# Field and coordinate usage metric ingestion

- Provider: [Apollo GraphOS](https://down.guide/apollo)
- Level: confirmed
- Impact: Partial outage
- lasted 17h 3m
- started 2026-06-28 03:13 UTC
- id: DWN-24d767bd7b
- Official page: https://status.apollographql.com/incidents/01KW63F7XTV5JY2NVAG9TARMEG

## Updates from Apollo GraphOS
### 2026-06-28 03:13 UTC: investigating
We are investigating suspected data loss for field and coordinate usage metrics for all customers.

### 2026-06-28 04:01 UTC: monitoring
Field and coordinate usage metric ingestion is functional and lag is trending downwards. We estimate 8-10 hours for full recovery.

### 2026-06-28 04:21 UTC: monitoring
The backlog of object field, input object field, and enum value metrics are now being processed but we expect the backlog to take 8-10 hours to be fully processed. For a period of time between 4 am and 9pm on June 27 UTC we expect there to be data loss for input object field and enum value metrics, as well as the client and operation breakdown of object field metrics. No other metrics (operation, trace, etc.) are impacted.

### 2026-06-28 20:16 UTC: resolved
The backlock of schema coordinate (object field, input object field, and enum value) metrics has now cleared and there is no more metric ingestion delay. The metrics for input object fields, enum values, and the operation and client breakdown of object fields is inaccurate for June 27 4-5am and 8-9pm, and missing between 5am to 8pm (all times in UTC). All other metrics were not impacted.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).
