Apollo Graph Status

Resolved: The issue has been resolved.

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

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

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

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

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

Resolved: We are marking this incident resolved on the Apollo side.

For any continuing matters, please consult our support portal: https://support.apollographql.com/

Monitoring: 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.

Monitoring: 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).

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

Monitoring: 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.

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

Resolved: The issue has been resolved.

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

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

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

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

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

Resolved: We are marking this incident resolved on the Apollo side.

For any continuing matters, please consult our support portal: https://support.apollographql.com/

Monitoring: 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.

Monitoring: 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).

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

Monitoring: 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.

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

Resolved: The issue has been resolved.

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

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

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

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

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