Apollo status history
Current state: operational — “All Systems Operational” per http://status.apollographql.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Apollo incidents last?
From 21 incidents with a vendor-posted start and resolve time. Longest on record: Issue Accessing “Submit a Request” and “My Requests” in Support Portal — 17.1 h (2026-05-25 19:50 UTC). Excluded, never estimated: 4 resolved before started (vendor data error). Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (25)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-01 15:41 UTC | Service Disruptions Due to Google Cloud Platform Issues | resolved | major | 4 h 37 min |
| 2026-08-26 22:12 UTC | Organization and user modifications are being incorrectly rate limited | resolved | major | 1 h 24 min |
| 2026-08-11 19:11 UTC | Registry workflow latency | resolved | minor | 4 h 07 min |
| 2026-08-05 09:43 UTC | Embedded Explorer and Embedded Sandbox temporarily down | resolved | major | 25 min |
| 2026-07-09 15:41 UTC | Proposals elevated error rate | resolved | minor | 2 h 28 min |
| 2026-06-28 03:13 UTC | Field and coordinate usage metric ingestion | resolved | major | 17 h 03 min |
| 2026-06-15 14:38 UTC | Delays in metric ingestion | resolved | minor | 7 h 37 min |
| 2026-06-01 08:35 UTC | Router Licensing impacting multiple customers | resolved | none | 3 h 04 min |
| 2026-05-25 19:50 UTC | Issue Accessing “Submit a Request” and “My Requests” in Support Portal | resolved | none | 17 h 08 min |
| 2026-04-27 08:34 UTC | Support ticket creation unavailable from Studio UI | resolved | none | 1 h 54 min |
| 2026-04-24 19:27 UTC | Studio Performance Deteriorated | resolved | none | 1 h 26 min |
| 2026-04-21 17:05 UTC | Platform availability for Studio SSO users | resolved | critical | 41 min |
| 2026-04-16 12:45 UTC | Schema proposal diff views returning errors | resolved | minor | 2 h 58 min |
| 2026-03-31 06:59 UTC | Transactional email delays | resolved | none | 40 min |
| 2026-02-12 06:06 UTC | Delays with GraphOS metrics availability and slow loading times for insights pages | resolved | none | — |
| 2025-11-21 18:05 UTC | Degredaded performance across several Apollo GraphOS services | resolved | minor | 3 h 20 min |
| 2025-11-18 19:06 UTC | Schema Publishing Encountering Issues | resolved | none | — |
| 2025-11-18 13:05 UTC | Elevated Error Rates for Cloud Routers and Studio UI | resolved | major | 2 h 32 min |
| 2025-11-18 13:05 UTC | Cloud Router elevated error rates | resolved | none | — |
| 2025-11-05 14:05 UTC | Federation version minor version build failures | resolved | major | 1 h 06 min |
| 2025-10-20 21:06 UTC | Schema Publishing Encountering Issues | resolved | minor | 8 h 20 min |
| 2025-10-20 16:56 UTC | AWS us-east-1 Outage Impacting Apollo Services | resolved | minor | 17 h 04 min |
| 2025-10-20 08:14 UTC | AWS us-east-1 Outage Impacting Multiple Apollo Services | resolved | major | 2 h 24 min |
| 2025-09-17 11:05 UTC | Schema proposal changes are unable to be saved | resolved | none | 46 min |
| 2025-08-21 22:06 UTC | Platform API SSL error | resolved | critical | — |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Apollo with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"apollo"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}