Apollo Graph, Inc.

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.

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.