Service Disruptions Due to Google Cloud Platform Issues
Affected: Studio UISchema ChecksUplinkMetrics IngestionSchema PublishingGraphQL APINotificationsInsights DashboardSchema Proposals
Apollo GraphQL Outage History
Apollo GraphQL is up right nowApollo GraphQL had 22 outages in the last 2 years totaling 26h 28m of downtime — averaging 0.9 incidents per month.
There were 22 Apollo GraphQL outages since October 20, 2025 totaling 26h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.
Organization and user modifications are being incorrectly rate limited
Affected: Studio UI
Timeline · 3 updates
- identified Aug 26, 2026, 08:42 PM UTC
Status: Identified Some organization and user modifications (user invites, user permission changes, OAuth changes) are failing intermittently. We are working on a fix. Affected components Studio UI (Partial outage)
- monitoring Aug 26, 2026, 10:18 PM UTC
Status: Monitoring We are no longer seeing any request failures, but we will continue to monitor until a root cause fix has been deployed. Affected components Studio UI (Operational)
- resolved Aug 26, 2026, 11:36 PM UTC
Status: Resolved The 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. Affected components Studio UI (Operational)
Registry workflow latency
Affected: Schema ChecksSchema PublishingSchema Proposals
Timeline · 3 updates
- investigating Aug 11, 2026, 07:11 PM UTC
Status: Investigating Registry service workflow latency has spiked, affecting mulitple internal services serving long-running workflows. Affected components Schema Checks (Degraded performance) Schema Publishing (Degraded performance) Schema Proposals (Degraded performance)
- monitoring Aug 11, 2026, 08:23 PM UTC
Status: Monitoring The issue has been resolved and we're continuing to monitor. Affected components Schema Proposals (Operational) Schema Checks (Operational) Schema Publishing (Operational)
- resolved Aug 11, 2026, 11:19 PM UTC
Status: Resolved The issue has been resolved. Affected components Schema Checks (Operational) Schema Publishing (Operational) Schema Proposals (Operational)
Embedded Explorer and Embedded Sandbox temporarily down
Affected: Studio UI
Timeline · 2 updates
- identified Aug 05, 2026, 09:43 AM UTC
Status: Identified Embedded Explorer and Embedded Sandbox are temporarily down. The issue has been identified and a fix is being deployed. Affected components Studio UI (Partial outage)
- resolved Aug 05, 2026, 10:08 AM UTC
Status: Resolved The issue has been fixed. Affected components Studio UI (Operational)
Proposals elevated error rate
Affected: Studio UISchema ChecksSchema Proposals
Timeline · 5 updates
- investigating Jul 09, 2026, 03:41 PM UTC
Status: Investigating We’re currently investigating a rise in error rates for our Proposals service. Affected components Schema Checks (Degraded performance) Studio UI (Degraded performance)
- investigating Jul 09, 2026, 03:54 PM UTC
Status: Investigating We are still investigating elevated error rates for Proposals. We appreciate your patience. Affected components Studio UI (Degraded performance) Schema Proposals (Degraded performance) Schema Checks (Operational)
- identified Jul 09, 2026, 04:05 PM UTC
Status: Identified We’ve identified the issue and are working on resolution. Affected components Schema Checks (Operational) Studio UI (Degraded performance) Schema Proposals (Degraded performance)
- monitoring Jul 09, 2026, 04:21 PM UTC
Status: Monitoring We have applied a fix and have begun to see recovery in our metrics. We will continue to monitor and update the status page once it’s resolved. Affected components Schema Checks (Operational) Studio UI (Degraded performance) Schema Proposals (Degraded performance)
- resolved Jul 09, 2026, 06:09 PM UTC
Status: Resolved The error rate for Proposals has returned to normal, no further impact expected. Affected components Schema Checks (Operational) Studio UI (Operational) Schema Proposals (Operational)
Field and coordinate usage metric ingestion
Affected: Metrics Ingestion
Timeline · 4 updates
- investigating Jun 28, 2026, 03:13 AM UTC
Status: Investigating We are investigating suspected data loss for field and coordinate usage metrics for all customers. Affected components Metrics Ingestion (Partial outage)
- monitoring Jun 28, 2026, 04:01 AM UTC
Status: Monitoring Field and coordinate usage metric ingestion is functional and lag is trending downwards. We estimate 8-10 hours for full recovery. Affected components Metrics Ingestion (Partial outage)
- monitoring Jun 28, 2026, 04:21 AM UTC
Status: Monitoring The backlog of object field, input object field, and enum value metrics are now being processed but we expect the backlog to take 8-10 hours to be fully processed. For a period of time between 4 am and 9pm on June 27 UTC we expect there to be data loss for input object field and enum value metrics, as well as the client and operation breakdown of object field metrics. No other metrics (operation, trace, etc.) are impacted. Affected components Metrics Ingestion (Degraded performance)
- resolved Jun 28, 2026, 08:16 PM UTC
Status: Resolved The 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. Affected components Metrics Ingestion (Operational)
Delays in metric ingestion
Affected: Metrics Ingestion
Timeline · 5 updates
- investigating Jun 15, 2026, 02:38 PM UTC
Status: Investigating We are investigating a case where metric ingestion is delayed for some customers. There is no loss of data. Affected components Metrics Ingestion (Degraded performance)
- investigating Jun 15, 2026, 04:18 PM UTC
Status: Investigating We have identified the cause though customers continue to experience metric ingestion delays while we identify the appropriate mitigation. Data backfill after remediation is still expected after mitigation is applied. We appreciate your patience. Affected components Metrics Ingestion (Degraded performance)
- identified Jun 15, 2026, 05:11 PM UTC
Status: Identified We are incrementally applying mitigations which are showing positive results. We feel we are confidently iterating toward recovery. At this time, no data is believed to be lost and metric backfill will continue with the oldest metrics being populated first, though we currently have a substantial backlog which we will scale to process quickly. We will update this status page as things continue and we appreciate your patience. Affected components Metrics Ingestion (Degraded performance)
- monitoring Jun 15, 2026, 05:42 PM UTC
Status: Monitoring We are confidently seeing recovery. Some metric delay will continue for the next couple hours, though many metric types have already recovered. We will keep this status page open in Monitoring state and update it when we have eliminated our metric lag. Thank you again for your patience. Affected components Metrics Ingestion (Degraded performance)
- resolved Jun 15, 2026, 10:16 PM UTC
Status: Resolved The 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. Affected components Metrics Ingestion (Operational)
Router Licensing impacting multiple customers
Timeline · 4 updates
- investigating Jun 01, 2026, 08:35 AM UTC
Status: Investigating Some Router deployments are experiencing issues coming online due to a message around licensing. We are investigating.
- investigating Jun 01, 2026, 09:12 AM UTC
Status: Investigating We are continuing to investigate.
- monitoring Jun 01, 2026, 09:54 AM UTC
Status: Monitoring We have seen recovery for about 50 minutes now and we are continuing to monitor the recovery. If you find that you are impacted by a licensing message on Router startup, please open a ticket with our support team.
- resolved Jun 01, 2026, 11:39 AM UTC
Status: Resolved After 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.
Issue Accessing “Submit a Request” and “My Requests” in Support Portal
Timeline · 4 updates
- investigating May 25, 2026, 07:50 PM UTC
Status: Investigating We’re currently investigating an issue where the “Submit a Request” and “My Requests” buttons are not appearing properly in the Apollo Support Portal. As a temporary workaround, tickets can still be created and accessed through the “Submit a Request” button available in the header of the portal.
- investigating May 26, 2026, 01:48 AM UTC
Status: Investigating We’re continuing to investigate the issue affecting the visibility of the “Submit a Request” and “My Requests” buttons in the Apollo Support Portal. At this time, we are working with our external provider to identify the root cause and restore normal functionality.
- monitoring May 26, 2026, 12:41 PM UTC
Status: Monitoring We’ve implemented changes to address the issue affecting the visibility of the “Submit a Request” and “My Requests” buttons in the Apollo Support Portal. At this time, the portal appears to be functioning normally, and we are actively monitoring the situation to ensure stability. If you continue experiencing issues, please try refreshing the page or signing out and back into the portal. We’ll continue to monitor closely and provide additional updates if needed.
- resolved May 26, 2026, 12:58 PM UTC
Status: Resolved The 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.
Support ticket creation unavailable from Studio UI
Timeline · 3 updates
- investigating Apr 27, 2026, 08:34 AM UTC
Status: Investigating Opening a ticket using the Contact Support button on the studio.apollographql.com "studio.apollographql.com": http://studio.apollographql.com site itself is currently failing. Support tickets can still be created through our support.apollographql.com "support.apollographql.com": http://support.apollographql.com portal, or via our support@ email address on the apollographql.com domain.
- monitoring Apr 27, 2026, 08:48 AM UTC
Status: Monitoring Support ticket opening functionality has been restored to Studio’s “Contact Support” functionality in the UI. We have mitigated the failures and will monitor before marking as resolved.
- resolved Apr 27, 2026, 10:29 AM UTC
Status: Resolved We have observed sustained restored functionality in our Studio-initiated support ticket form and are marking this as fully resolved.
Studio Performance Deteriorated
Timeline · 5 updates
- investigating Apr 24, 2026, 07:27 PM UTC
Status: Investigating We're seeing issues with StudioUI and are investigating to find the root cause
- investigating Apr 24, 2026, 08:09 PM UTC
Status: Investigating We're continuing to investigate to find the root cause and resolve the issue
- identified Apr 24, 2026, 08:33 PM UTC
Status: Identified We have identified a possible root cause, and we are testing changes to confirm
- monitoring Apr 24, 2026, 08:49 PM UTC
Status: Monitoring We confirmed with internal testing that our fix is working as expected, and customers should be seeing recovery. We're continuing to monitor to confirm.
- resolved Apr 24, 2026, 08:53 PM UTC
Status: Resolved We have resolved the issue. Customers should see full functionality.
Platform availability for Studio SSO users
Affected: Studio UI
Timeline · 3 updates
- investigating Apr 21, 2026, 05:05 PM UTC
Status: Investigating We’re investigating the availability of our platform after a recent deploy. Affected components Studio UI (Full outage)
- monitoring Apr 21, 2026, 05:20 PM UTC
Status: Monitoring We have restored functionality to impacted users SSO access and are monitoring. Affected components Studio UI (Operational)
- resolved Apr 21, 2026, 05:47 PM UTC
Status: Resolved SSO login is now fixed. Affected components Studio UI (Operational)
Schema proposal diff views returning errors
Affected: Schema ChecksSchema Publishing
Timeline · 3 updates
- investigating Apr 16, 2026, 12:45 PM UTC
Status: Investigating We are aware of an issue affecting GraphOS Studio where users may encounter errors when attempting to view the Changes or Schema Reference tabs within graph proposal. We are investigating and will give an update soon. Affected components Schema Checks (Degraded performance) Schema Publishing (Degraded performance)
- monitoring Apr 16, 2026, 01:27 PM UTC
Status: Monitoring We have identified the root cause of the failures affecting the Changes and References tabs in Schema Proposals. A fix has been deployed and we continue to monitor and investigate. Affected components Schema Checks (Operational) Schema Publishing (Operational)
- resolved Apr 16, 2026, 03:43 PM UTC
Status: Resolved Proposals errors have been clear for ~2 hours since the rollback reached prod. Marking resolved. Affected components Schema Checks (Operational) Schema Publishing (Operational)
Transactional email delays
Timeline · 3 updates
- investigating Mar 31, 2026, 06:59 AM UTC
Status: Investigating We’re monitoring an interruption in the transmission of transactional emails (e.g., email verification, welcome emails, proposals approvals). We are investigating.
- monitoring Mar 31, 2026, 07:26 AM UTC
Status: Monitoring We’ve identified the root cause of the delays, applied mitigations and recent delivery attempts are succeeding. Some previously attempted deliveries may take time to be retried.
- resolved Mar 31, 2026, 07:39 AM UTC
Status: Resolved Retries 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.