- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 38of 100
What to do
Check whether your product depends on Apollo GraphOS. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 20m it lasted.
Anything that failed between 2026-10-06 00:26 UTC and 2026-10-06 00:45 UTC may need a replay.Subscribe to Apollo GraphOS's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=apollo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
We're currently investigating the root causeRead the postmortem
Updates from Apollo GraphOS 3
- investigating
We're seeing issues deploying new graph artifacts builds. We're currently investigating the root cause
provider
- monitoring
We've identified an issue with our cloud configuration. We've corrected that and are now seeing recovery
provider
- resolved
Issue with the graph artifacts pipeline has been resolved. No data has been lost during the incident only delayed while we resolved the issue. We apologize for this disruption
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-dc05d554a2
Is Apollo GraphOS still down?
No, this incident was resolved 2026-10-06 00:45 UTC. For Apollo GraphOS's live state, see https://down.guide/apollo.
How long did it last?
20m, from 2026-10-06 00:26 UTC to 2026-10-06 00:45 UTC, by the times Apollo GraphOS posted.
What caused it?
Apollo GraphOS wrote: "We're currently investigating the root cause" The postmortem: https://status.apollographql.com/incidents/01M479MRVHMZNCT24DXB6FWVZS
Where does this come from?
Apollo GraphOS's official status page, https://status.apollographql.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.