30 Apollo incidents · junio de 2025 — official updates, affected components, duration and resolution details.
Latencia del flujo de trabajo del servicio del registro ha aumentado, lo que ha afectado a los servicios internos multple que prestan servicios de larga duración.
The issue has been resolved and we're continuing to monitor.
The issue has been resolved.
Traducido automáticamente desde la actualización oficial del incidente.
Embedded Explorer and Embedded Sandbox are temporarily down. The issue has been identified and a fix is being deployed.
The issue has been fixed.
We’re currently investigating a rise in error rates for our Proposals service.
We are still investigating elevated error rates for Proposals. We appreciate your patience.
We’ve identified the issue and are working on resolution.
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.
The error rate for Proposals has returned to normal, no further impact expected.
We are investigating suspected data loss for field and coordinate usage metrics for all customers.
Field and coordinate usage metric ingestion is functional and lag is trending downwards. We estimate 8-10 hours for full recovery.
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.
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.
We are investigating a case where metric ingestion is delayed for some customers. There is no loss of data.
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.
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.
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.
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.
Some Router deployments are experiencing issues coming online due to a message around licensing. We are investigating.
We are continuing to investigate.
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.
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.
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.
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.
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.
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.
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.
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.
We have observed sustained restored functionality in our Studio-initiated support ticket form and are marking this as fully resolved.
We're seeing issues with StudioUI and are investigating to find the root cause
We're continuing to investigate to find the root cause and resolve the issue
We have identified a possible root cause, and we are testing changes to confirm
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.
We have resolved the issue. Customers should see full functionality.
We’re investigating the availability of our platform after a recent deploy.
We have restored functionality to impacted users SSO access and are monitoring.
SSO login is now fixed.
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.
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.
Proposals errors have been clear for ~2 hours since the rollback reached prod. Marking resolved.
We’re monitoring an interruption in the transmission of transactional emails (e.g., email verification, welcome emails, proposals approvals). We are investigating.
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.
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.
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.
Platform API is also seeing degraded performance, which we are investigating
We're seeing increases in latency across a few different Apollo services. You may be seeing latency issues with proposals, checks, and studio.
We're still investigating the root cause. We're seeing some recovery, but not to full recovery
We're continuing to investigate the root cause of the issue. Some customers are reporting significant improvements in performance.
We've implemented a fix and are monitoring the system.
The issue has been resolved.
There was a period of degraded performance on schema publishing. The root cause has been identified and service restored.
We're experiencing elevates error rates due to an upstream DNS provider major incident.
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.
We're continuing the monitor the affected services while the upstream provider remediates the issue.
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).
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.
We are marking this incident resolved on the Apollo side. For any continuing matters, please consult our support portal: https://support.apollographql.com/
Cloud Routers are experiencing elevated errors due to an upstream external provider incident.
We’re investigating a potential issue with at minimum Federation versions 2.9, 2.10 and 2.11 that causes builds to fail.
We've rolled back federation versions 2.10 and 2.11 to the previous minor version, which should resolve the issue for those federation versions. We're continuing to investigate potential issues with federation version 2.9.
We've rolled back federation version 2.9 to its previous minor version, which should resolve the issue for that federation version. We're still working on confirming that the issue is completely resolved.
We've confirmed that the issue with federation versions 2.9, 2.10, and 2.11 is resolved.
We're investigating issues in the schema publishing pipeline. There is degraded performance right now. We are investigating the root cause.
We've identified the root cause of the issue as a third party dependency of Apollo attempting to recover from the AWS outage that has impacted many. The third party is working on remediating the issue and we are continuing to monitor.
No 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.
AWS has reported continued degradation after initial signs of recovery. We are seeing some minor impacts to the AWS Uplink service, which we are continuing to monitor. As we've previously stated we recommend customers to allowlist AWS and GCP Uplink endpoints which Apollo provides. Allowlisting both endpoints will allow seamless fallback if one is having issues. We have not seen any impact to GCP Uplink. Thanks for your patience during the matter and thank you for the AWS teams working toward full recovery.
Apollo Products hosted in AWS may be running into performance issues as problems at the Cloud Hosting Provider are remediated. Please use the "contact support" button in Studio if you require further bespoke assistance from Apollo.
We are continuing to monitor for any further issues.
All systems appear operational but some of our 3rd party dependencies have not fully recovered. Will continue to monitor.
Systems remain stable and operational on our side, though we are still monitoring dependent software closely before we mark this resolved. We will post another update within 60 minutes.
We 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.