- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us, us-east-1
- Down Index
- 50of 100
What to do
Check whether you use Apollo GraphOS in us, us-east-1. 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 2h 25m it lasted.
Anything that failed between 2025-10-20 08:14 UTC and 2025-10-20 10:39 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.
Updates from Apollo GraphOS 3
- investigating
Outage in AWS us-east-1 is impacting multiple Apollo products including Uplink (AWS), Cloud Routers and customer's ability to open supports tickets. By default Routers are configured to use GCP and AWS for Uplink, however if you have configured your router to use AWS exclusively there may be delays in schema updates, persisted queries manifests or the ability to bring new routers online, until the AWS outage is resolved. AWS Outage Link: https://health.aws.amazon.com/health/status
provider
- monitoring
AWS is reporting signs of recovery on their status page and we are seeing recovery in several of our triggered monitors for systems which rely on AWS, however, we continue to monitor the overall situation as AWS processes a backlog of events in us-east-1. As noted in the previous update, on-premise/self-hosted routers would only be impacted if their default configuration to roam between AWS and GCP has been changed to only rely on AWS. Anecdotally, we are seeing various non-Apollo systems regain previously unavailable functionality. AWS has suggested additional updates will occur within the next 30 minutes and we will update our own system statuses when we are confident they are fully recovered. Thanks for your patience during the matter and thank you for the AWS teams working toward full recovery.
provider
- resolved
As a result of the AWS us-east-1 system recovery, our own systems have also recovered, including AWS Uplink and AWS-hosted Cloud Routers. At this time we will mark this issue as Resolved, though we will continue to monitor for any possible reoccurrence. As noted in a previous update, the default configuration for Apollo Router and Apollo Gateway deployments is to roam between Google Cloud Platform (GCP) and Amazon Web Services (AWS) endpoints in the event that one or the other is available. If you have changed your configuration to rely on merely one provider, we recommend considering a configuration with fallback redundancy. Please contact support if you need assistance with this configuration. Additionally, our support systems have recovered and we believe any issues opened during the AWS incident have been received by our support teams. If you believe your issue has not been received, please feel free to reach out to our support team again.
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-83103fcd72
Is Apollo GraphOS still down?
No, this incident was resolved 2025-10-20 10:39 UTC. For Apollo GraphOS's live state, see https://down.guide/apollo.
How long did it last?
2h 25m, from 2025-10-20 08:14 UTC to 2025-10-20 10:39 UTC, by the times Apollo GraphOS posted.
What was affected?
Apollo GraphOS named in us, us-east-1.
What caused it?
Apollo GraphOS hasn't published a root cause. If it does, it shows here.
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.