Apollo GraphQL Outage History

Started Oct 06, 2026, 12:26 AM UTC· resolved Oct 06, 2026, 12:45 AM UTC

1. investigating Oct 06, 2026, 12:26 AM UTC

   We're seeing issues deploying new graph artifacts builds. We're currently investigating the root cause

2. monitoring Oct 06, 2026, 12:37 AM UTC

   We've identified an issue with our cloud configuration. We've corrected that and are now seeing recovery

3. resolved Oct 06, 2026, 12:45 AM UTC

   Issue with the graph artifacts pipeline has been resolved. No data has been lost during the incident only delayed while we resolved the issue. We apologize for this disruption

Read the full incident report →

Started Sep 01, 2026, 03:41 PM UTC· resolved Sep 01, 2026, 05:23 PM UTC

1. investigating Sep 01, 2026, 03:41 PM UTC

   Due to an ongoing outage on Google Cloud Platform (GCP), we're currently experiencing service disruptions across multiple Apollo services. We're actively investigating and will share updates as more information becomes available.

2. investigating Sep 01, 2026, 03:48 PM UTC

   The AWS Uplink endpoint remains available. GraphOS Routers and Gateways using the default multi-cloud configuration can continue to start up and fetch their configuration during this outage, but new schemas cannot be published.

3. identified Sep 01, 2026, 04:39 PM UTC

   Due to an ongoing outage on Google Cloud Platform (GCP), we're currently experiencing service disruptions across multiple Apollo services. We're actively investigating and will share updates as more information becomes available.

4. monitoring Sep 01, 2026, 05:21 PM UTC

   Our third party vendor has confirmed the issue was isolated to a portion of the us-central1-b zone; remaining zones in the region were unaffected. Most Apollo products have recovered, and our engineering team is validating the remaining impacted services. We'll continue monitoring closely before marking this incident resolved.

5. monitoring Sep 01, 2026, 05:23 PM UTC

   Our third party vendor has confirmed the issue was isolated to a portion of the us-central1-b zone; remaining zones in the region were unaffected. Most Apollo products have recovered, and our engineering team is validating the remaining impacted services. We'll continue monitoring closely before marking this incident resolved.

6. resolved Sep 01, 2026, 08:18 PM UTC

   Our third party vendor has confirmed the issue is now resolved, and all Apollo products have recovered.

Read the full incident report →

Started Aug 26, 2026, 10:12 PM UTC· resolved Aug 26, 2026, 10:18 PM UTC

1. identified Aug 26, 2026, 08:42 PM UTC

   Some organization and user modifications (user invites, user permission changes, OAuth changes) are failing intermittently. We are working on a fix.

2. monitoring Aug 26, 2026, 10:18 PM UTC

   We are no longer seeing any request failures, but we will continue to monitor until a root cause fix has been deployed.

3. resolved Aug 26, 2026, 11:36 PM UTC

   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.

Read the full incident report →

Started Aug 11, 2026, 07:11 PM UTC· resolved Aug 11, 2026, 08:23 PM UTC

1. investigating Aug 11, 2026, 07:11 PM UTC

   Registry service workflow latency has spiked, affecting mulitple internal services serving long-running workflows.

2. monitoring Aug 11, 2026, 08:23 PM UTC

   The issue has been resolved and we're continuing to monitor.

3. resolved Aug 11, 2026, 11:19 PM UTC

   The issue has been resolved.

Read the full incident report →

Started Aug 05, 2026, 09:43 AM UTC· resolved Aug 05, 2026, 10:08 AM UTC

1. identified Aug 05, 2026, 09:43 AM UTC

   Embedded Explorer and Embedded Sandbox are temporarily down. The issue has been identified and a fix is being deployed.

2. resolved Aug 05, 2026, 10:08 AM UTC

   The issue has been fixed.

Read the full incident report →

Started Jul 09, 2026, 03:41 PM UTC· resolved Jul 09, 2026, 06:09 PM UTC

1. investigating Jul 09, 2026, 03:41 PM UTC

   We’re currently investigating a rise in error rates for our Proposals service.

2. investigating Jul 09, 2026, 03:54 PM UTC

   We are still investigating elevated error rates for Proposals. We appreciate your patience.

3. identified Jul 09, 2026, 04:05 PM UTC

   We’ve identified the issue and are working on resolution.

4. monitoring Jul 09, 2026, 04:21 PM UTC

   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.

5. resolved Jul 09, 2026, 06:09 PM UTC

   The error rate for Proposals has returned to normal, no further impact expected.

Read the full incident report →

Started Jun 28, 2026, 03:13 AM UTC· resolved Jun 28, 2026, 08:16 PM UTC

1. investigating Jun 28, 2026, 03:13 AM UTC

   We are investigating suspected data loss for field and coordinate usage metrics for all customers.

2. monitoring Jun 28, 2026, 04:01 AM UTC

   Field and coordinate usage metric ingestion is functional and lag is trending downwards. We estimate 8-10 hours for full recovery.

3. monitoring Jun 28, 2026, 04:21 AM UTC

   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.

4. resolved Jun 28, 2026, 08:16 PM UTC

   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.

Read the full incident report →

Started Jun 15, 2026, 02:38 PM UTC· resolved Jun 15, 2026, 10:16 PM UTC

1. investigating Jun 15, 2026, 02:38 PM UTC

   We are investigating a case where metric ingestion is delayed for some customers. There is no loss of data.

2. investigating Jun 15, 2026, 04:18 PM UTC

   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.

3. identified Jun 15, 2026, 05:11 PM UTC

   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.

4. monitoring Jun 15, 2026, 05:42 PM UTC

   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.

5. resolved Jun 15, 2026, 10:16 PM UTC

   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.

Read the full incident report →

Started Jun 01, 2026, 08:35 AM UTC· resolved Jun 01, 2026, 11:39 AM UTC

1. investigating Jun 01, 2026, 08:35 AM UTC

   Some Router deployments are experiencing issues coming online due to a message around licensing. We are investigating.

2. investigating Jun 01, 2026, 09:12 AM UTC

   We are continuing to investigate.

3. monitoring Jun 01, 2026, 09:54 AM UTC

   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.

4. resolved Jun 01, 2026, 11:39 AM UTC

   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.

Read the full incident report →

Started May 25, 2026, 07:50 PM UTC· resolved May 26, 2026, 12:58 PM UTC

1. investigating May 25, 2026, 07:50 PM UTC

   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.

2. investigating May 26, 2026, 01:48 AM UTC

   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.

3. monitoring May 26, 2026, 12:41 PM UTC

   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.

4. resolved May 26, 2026, 12:58 PM UTC

   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.

Read the full incident report →

Started Apr 27, 2026, 08:34 AM UTC· resolved Apr 27, 2026, 10:29 AM UTC

1. investigating Apr 27, 2026, 08:34 AM UTC

   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.

2. monitoring Apr 27, 2026, 08:48 AM UTC

   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.

3. resolved Apr 27, 2026, 10:29 AM UTC

   We have observed sustained restored functionality in our Studio-initiated support ticket form and are marking this as fully resolved.

Read the full incident report →

Started Apr 24, 2026, 07:27 PM UTC· resolved Apr 24, 2026, 08:53 PM UTC

1. investigating Apr 24, 2026, 07:27 PM UTC

   We're seeing issues with StudioUI and are investigating to find the root cause

2. investigating Apr 24, 2026, 08:09 PM UTC

   We're continuing to investigate to find the root cause and resolve the issue

3. identified Apr 24, 2026, 08:33 PM UTC

   We have identified a possible root cause, and we are testing changes to confirm

4. monitoring Apr 24, 2026, 08:49 PM UTC

   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.

5. resolved Apr 24, 2026, 08:53 PM UTC

   We have resolved the issue. Customers should see full functionality.

Read the full incident report →

Started Apr 21, 2026, 05:05 PM UTC· resolved Apr 21, 2026, 05:20 PM UTC

1. investigating Apr 21, 2026, 05:05 PM UTC

   We’re investigating the availability of our platform after a recent deploy.

2. monitoring Apr 21, 2026, 05:20 PM UTC

   We have restored functionality to impacted users SSO access and are monitoring.

3. resolved Apr 21, 2026, 05:47 PM UTC

   SSO login is now fixed.

Read the full incident report →

Started Apr 16, 2026, 12:45 PM UTC· resolved Apr 16, 2026, 01:27 PM UTC

1. investigating Apr 16, 2026, 12:45 PM UTC

   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.

2. monitoring Apr 16, 2026, 01:27 PM UTC

   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.

3. resolved Apr 16, 2026, 03:43 PM UTC

   Proposals errors have been clear for ~2 hours since the rollback reached prod. Marking resolved.

Read the full incident report →

Started Mar 31, 2026, 06:59 AM UTC· resolved Mar 31, 2026, 07:39 AM UTC

1. investigating Mar 31, 2026, 06:59 AM UTC

   We’re monitoring an interruption in the transmission of transactional emails (e.g., email verification, welcome emails, proposals approvals). We are investigating.

2. monitoring Mar 31, 2026, 07:26 AM UTC

   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.

3. resolved Mar 31, 2026, 07:39 AM UTC

   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.

Read the full incident report →

Started Feb 10, 2026, 04:00 PM UTC· resolved Feb 10, 2026, 04:00 PM UTC

1. resolved Feb 10, 2026, 04:00 PM UTC

   We'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.

Read the full incident report →

Started Nov 21, 2025, 06:05 PM UTC· resolved Nov 21, 2025, 09:25 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 18, 2025, 05:30 PM UTC· resolved Nov 18, 2025, 05:30 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 18, 2025, 01:05 PM UTC· resolved Nov 18, 2025, 03:38 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 18, 2025, 12:30 PM UTC· resolved Nov 18, 2025, 12:30 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 05, 2025, 02:05 PM UTC· resolved Nov 05, 2025, 03:12 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 20, 2025, 09:06 PM UTC· resolved Oct 21, 2025, 05:26 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 20, 2025, 04:56 PM UTC· resolved Oct 21, 2025, 10:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 20, 2025, 08:14 AM UTC· resolved Oct 20, 2025, 10:39 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →