Apollo GraphQL Outage History

Apollo GraphQL is up right now

Apollo GraphQL had 22 outages in the last 2 years totaling 27h 57m of downtime — averaging 0.9 incidents per month.

There were 22 Apollo GraphQL outages since July 3, 2025 totaling 27h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.apollographql.com

Minor June 15, 2026

Delays in metric ingestion

Detected by Pingoru
Jun 15, 2026, 10:16 PM UTC
Resolved
Jun 15, 2026, 10:16 PM UTC
Duration
Affected: Metrics Ingestion
Timeline · 5 updates
  1. 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)

  2. 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)

  3. 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)

  4. 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)

  5. 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)

Read the full incident report →

Minor June 1, 2026

Router Licensing impacting multiple customers

Detected by Pingoru
Jun 01, 2026, 11:39 AM UTC
Resolved
Jun 01, 2026, 11:39 AM UTC
Duration
Timeline · 4 updates
  1. 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.

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

    Status: Investigating We are continuing to investigate.

  3. 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.

  4. 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.

Read the full incident report →

Minor May 26, 2026

Issue Accessing “Submit a Request” and “My Requests” in Support Portal

Detected by Pingoru
May 26, 2026, 12:58 PM UTC
Resolved
May 26, 2026, 12:58 PM UTC
Duration
Timeline · 4 updates
  1. 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.

  2. 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.

  3. 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.

  4. 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.

Read the full incident report →

Minor April 27, 2026

Support ticket creation unavailable from Studio UI

Detected by Pingoru
Apr 27, 2026, 10:29 AM UTC
Resolved
Apr 27, 2026, 10:29 AM UTC
Duration
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Minor April 24, 2026

Studio Performance Deteriorated

Detected by Pingoru
Apr 24, 2026, 08:53 PM UTC
Resolved
Apr 24, 2026, 08:53 PM UTC
Duration
Timeline · 5 updates
  1. investigating Apr 24, 2026, 07:27 PM UTC

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

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

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

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

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

  4. 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.

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

    Status: Resolved We have resolved the issue. Customers should see full functionality.

Read the full incident report →

Minor April 21, 2026

Platform availability for Studio SSO users

Detected by Pingoru
Apr 21, 2026, 05:47 PM UTC
Resolved
Apr 21, 2026, 05:47 PM UTC
Duration
Affected: Studio UI
Timeline · 3 updates
  1. 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)

  2. 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)

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

    Status: Resolved SSO login is now fixed. Affected components Studio UI (Operational)

Read the full incident report →

Minor April 16, 2026

Schema proposal diff views returning errors

Detected by Pingoru
Apr 16, 2026, 03:43 PM UTC
Resolved
Apr 16, 2026, 03:43 PM UTC
Duration
Affected: Schema ChecksSchema Publishing
Timeline · 3 updates
  1. 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)

  2. 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)

  3. 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)

Read the full incident report →

Minor March 31, 2026

Transactional email delays

Detected by Pingoru
Mar 31, 2026, 07:39 AM UTC
Resolved
Mar 31, 2026, 07:39 AM UTC
Duration
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →