https://approjects-vendor-status-watch.static.hf.space/v/apollo.htmlIncidents from Apollo's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000http://status.apollographql.comapollo:2026-09-01T15:41:44ZTue, 01 Sep 2026 15:41:44 +0000Our third party vendor has confirmed the issue is now resolved, and all Apollo products have recovered.http://status.apollographql.comapollo:2026-08-26T22:12:39ZWed, 26 Aug 2026 22:12:39 +0000The fix has been deployed. These failed operations would have appeared as rate limit errors, but the rate limit was being incorrectly applied. We have made changes to ensure the rate limit works as expected.http://status.apollographql.comapollo:2026-08-11T19:11:37ZTue, 11 Aug 2026 19:11:37 +0000The issue has been resolved.http://status.apollographql.comapollo:2026-08-05T09:43:26ZWed, 05 Aug 2026 09:43:26 +0000The issue has been fixed.http://status.apollographql.comapollo:2026-07-09T15:41:29ZThu, 09 Jul 2026 15:41:29 +0000The error rate for Proposals has returned to normal, no further impact expected.http://status.apollographql.comapollo:2026-06-28T03:13:19ZSun, 28 Jun 2026 03:13:19 +0000The 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.http://status.apollographql.comapollo:2026-06-15T14:38:25ZMon, 15 Jun 2026 14:38:25 +0000The metric ingestion backlog has been fully processed and all metrics have resumed normal ingestion. We do not believe any data was lost as a result of this incident. All metric types should now be operating as expected. Thank you for your patience throughout this incident.http://status.apollographql.comapollo:2026-06-01T08:35:25ZMon, 01 Jun 2026 08:35:25 +0000After extended monitoring, we have confirmed that the issue is resolved. Post-incident action items will continue after the end of the incident. As with all incidents, we will be conducting an internal post-mortem. We appreciate your patience.http://status.apollographql.comapollo:2026-05-25T19:50:43ZMon, 25 May 2026 19:50:43 +0000The issue affecting the visibility of the “Submit a Request” and “My Requests” buttons in the Apollo Support Portal has been resolved. Portal functionality has been restored, and users should now be able to access these options normally. Thank you for your patience while we worked to resolve this issue.http://status.apollographql.comapollo:2026-04-27T08:34:51ZMon, 27 Apr 2026 08:34:51 +0000We have observed sustained restored functionality in our Studio-initiated support ticket form and are marking this as fully resolved.http://status.apollographql.comapollo:2026-04-24T19:27:20ZFri, 24 Apr 2026 19:27:20 +0000We have resolved the issue. Customers should see full functionality.http://status.apollographql.comapollo:2026-04-21T17:05:47ZTue, 21 Apr 2026 17:05:47 +0000SSO login is now fixed.http://status.apollographql.comapollo:2026-04-16T12:45:07ZThu, 16 Apr 2026 12:45:07 +0000Proposals errors have been clear for ~2 hours since the rollback reached prod. Marking resolved.http://status.apollographql.comapollo:2026-03-31T06:59:02ZTue, 31 Mar 2026 06:59:02 +0000Retries of delayed transaction emails have been successful. If you have not received an email you were expecting for account reasons, we suggest retrying the workflow which triggered the email.http://status.apollographql.comapollo:2026-02-12T06:06:22ZThu, 12 Feb 2026 06:06:22 +0000We've identified an issue where our metrics ingestion pipeline was falling behind for several hours. Systems have now fully recovered and no data was lost, however some customers may have experienced delays viewing insights data in Studio and / or slower page load times during this event. Apologies for the interruption.http://status.apollographql.comapollo:2025-11-21T18:05:32ZFri, 21 Nov 2025 18:05:32 +0000The issue has been resolved.http://status.apollographql.comapollo:2025-11-18T19:06:04ZTue, 18 Nov 2025 19:06:04 +0000There was a period of degraded performance on schema publishing. The root cause has been identified and service restored.http://status.apollographql.comapollo:2025-11-18T13:05:25ZTue, 18 Nov 2025 13:05:25 +0000We are marking this incident resolved on the Apollo side. For any continuing matters, please consult our support portal: https://support.apollographql.com/http://status.apollographql.comapollo:2025-11-18T13:05:25ZTue, 18 Nov 2025 13:05:25 +0000Cloud Routers are experiencing elevated errors due to an upstream external provider incident.http://status.apollographql.comapollo:2025-11-05T14:05:49ZWed, 05 Nov 2025 14:05:49 +0000We've confirmed that the issue with federation versions 2.9, 2.10, and 2.11 is resolved.http://status.apollographql.comapollo:2025-10-20T21:06:09ZMon, 20 Oct 2025 21:06:09 +0000No 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.http://status.apollographql.comapollo:2025-10-20T16:56:25ZMon, 20 Oct 2025 16:56:25 +0000We 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.http://status.apollographql.comapollo:2025-10-20T08:14:38ZMon, 20 Oct 2025 08:14:38 +0000As 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 thttp://status.apollographql.comapollo:2025-09-17T11:05:53ZWed, 17 Sep 2025 11:05:53 +0000This incident has been resolved.http://status.apollographql.comapollo:2025-08-21T22:06:05ZThu, 21 Aug 2025 22:06:05 +0000This incident has been resolved.