Historique des pannes de Apollo

1. 6 octobre 2026 à 00:26 UTCinvestigating

   Nous voyons des problèmes de déploiement de nouveaux artefacts graphiques. Nous enquêtons actuellement sur la cause profonde

2. 6 octobre 2026 à 00:37 UTCmonitoring

   Nous avons identifié un problème avec notre configuration cloud. Nous avons corrigé cela et nous voyons maintenant la récupération

3. 6 octobre 2026 à 00:45 UTCresolved

   La question du pipeline des artefacts graphiques a été résolue. Aucune donnée n'a été perdue pendant l'incident seulement retardé pendant que nous avons résolu le problème. Nous nous excusons pour cette perturbation

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 1 septembre 2026 à 15:41 UTCinvestigating

   En raison d'une panne continue sur Google Cloud Platform (GCP), nous sommes actuellement confrontés à des perturbations de services sur plusieurs services Apollo. Nous enquêtons activement et partagerons les mises à jour au fur et à mesure que davantage d'informations seront disponibles.

2. 1 septembre 2026 à 15:48 UTCinvestigating

   Le paramètre AWS Uplink reste disponible. Les routeurs et passerelles GraphOS utilisant la configuration multicloud par défaut peuvent continuer à démarrer et récupérer leur configuration pendant cette panne, mais de nouveaux schémas ne peuvent pas être publiés.

3. 1 septembre 2026 à 16:39 UTCidentified

   En raison d'une panne continue sur Google Cloud Platform (GCP), nous sommes actuellement confrontés à des perturbations de services sur plusieurs services Apollo. Nous enquêtons activement et partagerons les mises à jour au fur et à mesure que davantage d'informations seront disponibles.

4. 1 septembre 2026 à 17:23 UTCmonitoring

   Notre fournisseur tiers a confirmé que le problème était isolé dans une partie de la zone nous-central1-b; les zones restantes de la région n'étaient pas affectées. La plupart des produits Apollo ont récupéré, et notre équipe d'ingénieurs valide les autres services touchés. Nous continuerons à surveiller de près avant de marquer cet incident résolu.

5. 1 septembre 2026 à 20:18 UTCresolved

   Notre fournisseur tiers a confirmé que le problème est maintenant résolu, et tous les produits Apollo ont récupéré.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 26 août 2026 à 22:12 UTCidentified

   Certaines modifications de l'organisation et de l'utilisateur (invitations de l'utilisateur, modifications de la permission de l'utilisateur, modifications d'OAuth) échouent de façon intermittente. Nous travaillons sur une solution.

2. 26 août 2026 à 22:18 UTCmonitoring

   Nous ne voyons plus d'échecs de requête, mais nous continuerons à surveiller jusqu'à ce qu'une correction de cause racine ait été déployée.

3. 26 août 2026 à 23:36 UTCresolved

   La solution a été déployée. Ces opérations en échec auraient semblé être des erreurs de limite de taux, mais la limite de taux était mal appliquée. Nous avons apporté des modifications pour nous assurer que la limite de tarif fonctionne comme prévu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 11 août 2026 à 19:11 UTCinvestigating

   La latence du service d'enregistrement a augmenté, affectant les services internes multiples servant les workflows à long terme.

2. 11 août 2026 à 20:23 UTCmonitoring

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

3. 11 août 2026 à 23:19 UTCresolved

   The issue has been resolved.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 5 août 2026 à 09:43 UTCidentified

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

2. 5 août 2026 à 10:08 UTCresolved

   The issue has been fixed.

1. 9 juillet 2026 à 15:41 UTCinvestigating

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

2. 9 juillet 2026 à 15:54 UTCinvestigating

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

3. 9 juillet 2026 à 16:05 UTCidentified

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

4. 9 juillet 2026 à 16:21 UTCmonitoring

   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. 9 juillet 2026 à 18:09 UTCresolved

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

1. 28 juin 2026 à 03:13 UTCinvestigating

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

2. 28 juin 2026 à 04:01 UTCmonitoring

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

3. 28 juin 2026 à 04:21 UTCmonitoring

   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. 28 juin 2026 à 20:16 UTCresolved

   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.

1. 15 juin 2026 à 14:38 UTCinvestigating

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

2. 15 juin 2026 à 16:18 UTCinvestigating

   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. 15 juin 2026 à 17:11 UTCidentified

   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. 15 juin 2026 à 17:42 UTCmonitoring

   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. 15 juin 2026 à 22:16 UTCresolved

   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.

1. 1 juin 2026 à 08:35 UTCinvestigating

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

2. 1 juin 2026 à 09:12 UTCinvestigating

   We are continuing to investigate.

3. 1 juin 2026 à 09:54 UTCmonitoring

   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. 1 juin 2026 à 11:39 UTCresolved

   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.

1. 25 mai 2026 à 19:50 UTCinvestigating

   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. 26 mai 2026 à 01:48 UTCinvestigating

   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. 26 mai 2026 à 12:41 UTCmonitoring

   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. 26 mai 2026 à 12:58 UTCresolved

   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.

1. 27 avril 2026 à 08:34 UTCinvestigating

   Opening a ticket using the Contact Support button on the [studio.apollographql.com](http://studio.apollographql.com "studio.apollographql.com") site itself is currently failing. Support tickets can still be created through our [support.apollographql.com](http://support.apollographql.com "support.apollographql.com") portal, or via our `support@` email address on the `apollographql.com` domain.

2. 27 avril 2026 à 09:23 UTCmonitoring

   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. 27 avril 2026 à 10:29 UTCresolved

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

1. 24 avril 2026 à 19:27 UTCinvestigating

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

2. 24 avril 2026 à 20:09 UTCinvestigating

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

3. 24 avril 2026 à 20:33 UTCidentified

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

4. 24 avril 2026 à 20:49 UTCmonitoring

   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. 24 avril 2026 à 20:53 UTCresolved

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

1. 21 avril 2026 à 17:05 UTCinvestigating

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

2. 21 avril 2026 à 17:20 UTCmonitoring

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

3. 21 avril 2026 à 17:47 UTCresolved

   SSO login is now fixed.

1. 16 avril 2026 à 12:45 UTCinvestigating

   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. 16 avril 2026 à 13:27 UTCmonitoring

   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. 16 avril 2026 à 15:43 UTCresolved

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

1. 31 mars 2026 à 06:59 UTCinvestigating

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

2. 31 mars 2026 à 07:26 UTCmonitoring

   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. 31 mars 2026 à 07:39 UTCresolved

   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.

1. 12 février 2026 à 06:06 UTCresolved

   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.

1. 21 novembre 2025 à 18:05 UTCinvestigating

   Platform API is also seeing degraded performance, which we are investigating

2. 21 novembre 2025 à 18:05 UTCinvestigating

   We're seeing increases in latency across a few different Apollo services. You may be seeing latency issues with proposals, checks, and studio.

3. 21 novembre 2025 à 19:06 UTCinvestigating

   We're still investigating the root cause. We're seeing some recovery, but not to full recovery

4. 21 novembre 2025 à 20:06 UTCinvestigating

   We're continuing to investigate the root cause of the issue. Some customers are reporting significant improvements in performance.

5. 21 novembre 2025 à 21:05 UTCmonitoring

   We've implemented a fix and are monitoring the system.

6. 21 novembre 2025 à 22:05 UTCresolved

   The issue has been resolved.

1. 18 novembre 2025 à 19:06 UTCresolved

   There was a period of degraded performance on schema publishing. The root cause has been identified and service restored.

1. 18 novembre 2025 à 13:05 UTCinvestigating

   We're experiencing elevates error rates due to an upstream DNS provider major incident.

2. 18 novembre 2025 à 14:06 UTCmonitoring

   We're continuing the monitor the affected services while the upstream provider remediates the issue.

3. 18 novembre 2025 à 14:06 UTCmonitoring

   Our DNS provider has provided an update: "The issue has been identified and a fix is being implemented." We will be monitoring for recovery of our systems.

4. 18 novembre 2025 à 14:44 UTCmonitoring

   At this time, our monitors indicate that only Cloud Routers hosted on Apollo infrastructure are impacted as a result of an upstream service provider incident. Studio UI has already recovered. Beyond these two impacted services, there has been no impact to APIs (including Uplink).

5. 18 novembre 2025 à 15:02 UTCmonitoring

   The upstream provider has indicated recovery on their status page (https://www.cloudflarestatus.com/incidents/8gmgl950y3h7). At the same time, we have seen our own monitors return to non-triggered states. We will continue to monitor for the next 15 minutes and then declare this Resolved. While Cloud Routers were impacted throughout the incident, the Studio UI impact was during two distinct periods: Nov 18 11:52 am – Nov 18, 12:10 pm UTC (18 minutes) and again from Nov 18, 12:51 pm – Nov 18, 1:09 pm UTC (another 18 minutes). Studio UI was otherwise available in times outside of that range.

6. 18 novembre 2025 à 15:38 UTCresolved

   We are marking this incident resolved on the Apollo side. For any continuing matters, please consult our support portal: https://support.apollographql.com/

1. 18 novembre 2025 à 13:05 UTCresolved

   Cloud Routers are experiencing elevated errors due to an upstream external provider incident.