Apollo Graph Status

Resolved: We will mark this as resolved as issues impacting our service have been resolved either through mitigation or upstream provider resolution. While some of our dependent services have indicated there is on-going stabilization of their own systems (following on the AWS us-east-1 disruptions yesterday) any unresolved items have NO impact to our offerings. In the event that we have new findings or degradations, we will open a new incident.

Thank you for your patience while we adapted toward changing circumstances following on yesterday's events, and thank you to teams across the industry who worked (or may still be working) tirelessly toward recovery.

Monitoring: Systems remain stable and operational on our side, though we are still monitoring dependent software closely before we mark this resolved. We will post another update within 60 minutes.

Monitoring: All systems appear operational but some of our 3rd party dependencies have not fully recovered. Will continue to monitor.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Apollo Products hosted in AWS may be running into performance issues as problems at the Cloud Hosting Provider are remediated.

Please use the "contact support" button in Studio if you require further bespoke assistance from Apollo.

Monitoring: AWS has reported continued degradation after initial signs of recovery. We are seeing some minor impacts to the AWS Uplink service, which we are continuing to monitor.

As we've previously stated we recommend customers to allowlist AWS and GCP Uplink endpoints which Apollo provides. Allowlisting both endpoints will allow seamless fallback if one is having issues. We have not seen any impact to GCP Uplink.

Thanks for your patience during the matter and thank you for the AWS teams working toward full recovery.

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.

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.

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

Resolved: We will mark this as resolved as issues impacting our service have been resolved either through mitigation or upstream provider resolution. While some of our dependent services have indicated there is on-going stabilization of their own systems (following on the AWS us-east-1 disruptions yesterday) any unresolved items have NO impact to our offerings. In the event that we have new findings or degradations, we will open a new incident.

Thank you for your patience while we adapted toward changing circumstances following on yesterday's events, and thank you to teams across the industry who worked (or may still be working) tirelessly toward recovery.

Monitoring: Systems remain stable and operational on our side, though we are still monitoring dependent software closely before we mark this resolved. We will post another update within 60 minutes.

Monitoring: All systems appear operational but some of our 3rd party dependencies have not fully recovered. Will continue to monitor.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Apollo Products hosted in AWS may be running into performance issues as problems at the Cloud Hosting Provider are remediated.

Please use the "contact support" button in Studio if you require further bespoke assistance from Apollo.

Monitoring: AWS has reported continued degradation after initial signs of recovery. We are seeing some minor impacts to the AWS Uplink service, which we are continuing to monitor.

As we've previously stated we recommend customers to allowlist AWS and GCP Uplink endpoints which Apollo provides. Allowlisting both endpoints will allow seamless fallback if one is having issues. We have not seen any impact to GCP Uplink.

Thanks for your patience during the matter and thank you for the AWS teams working toward full recovery.

Resolved: No schema publishing or checks issues have been observed for couple of hours now. We are continuing to monitor our services in relation to the AWS outage today on the other open incident.

Monitoring: We've identified the root cause of the issue as a third party dependency of Apollo attempting to recover from the AWS outage that has impacted many. The third party is working on remediating the issue and we are continuing to monitor.

Investigating: We're investigating issues in the schema publishing pipeline. There is degraded performance right now. We are investigating the root cause.

Resolved: We will mark this as resolved as issues impacting our service have been resolved either through mitigation or upstream provider resolution. While some of our dependent services have indicated there is on-going stabilization of their own systems (following on the AWS us-east-1 disruptions yesterday) any unresolved items have NO impact to our offerings. In the event that we have new findings or degradations, we will open a new incident.

Thank you for your patience while we adapted toward changing circumstances following on yesterday's events, and thank you to teams across the industry who worked (or may still be working) tirelessly toward recovery.

Monitoring: Systems remain stable and operational on our side, though we are still monitoring dependent software closely before we mark this resolved. We will post another update within 60 minutes.

Monitoring: All systems appear operational but some of our 3rd party dependencies have not fully recovered. Will continue to monitor.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Apollo Products hosted in AWS may be running into performance issues as problems at the Cloud Hosting Provider are remediated.

Please use the "contact support" button in Studio if you require further bespoke assistance from Apollo.

Monitoring: AWS has reported continued degradation after initial signs of recovery. We are seeing some minor impacts to the AWS Uplink service, which we are continuing to monitor.

As we've previously stated we recommend customers to allowlist AWS and GCP Uplink endpoints which Apollo provides. Allowlisting both endpoints will allow seamless fallback if one is having issues. We have not seen any impact to GCP Uplink.

Thanks for your patience during the matter and thank you for the AWS teams working toward full recovery.

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.

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.

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