Simultaneous outages affecting Claude, ChatGPT and Grok on 3 September 2026 – a common cause remains unconfirmed
.gif)
The Grok outage on Android on 3 September 2026 was part of simultaneous morning outages affecting Claude, ChatGPT/Codex and Grok. SpaceX cited an outage at a data center in Memphis as the cause of the Grok outage, but Anthropic and OpenAI did not confirm a common cause.
The latest reports show that the outage affecting Grok models in the Android app on 3 September 2026 was not an isolated event, but part of simultaneous morning outages at three major AI model providers. According to SpaceX (the parent company of xAI), the problems with Grok were caused by “an outage at their compute center in Memphis” that morning; the company also apologized to “affected compute partners” – Anthropic and xAI had announced compute partnerships with SpaceX in May 2026. However, neither OpenAI nor Anthropic confirmed to Wired any shared cause with their own outages, and Anthropic declined to comment on the entire episode. According to Wired, simultaneous outages across the industry usually point to a problem at a shared cloud or CDN provider, but none of the major infrastructure providers (Cloudflare, AWS, Microsoft Azure) reported an outage that day.
The Grok outage on Android itself was recorded on the xAI status page from 13:30 GMT (6:30 PT), marked as active with a severity of “outage” at 13:43 GMT, and resolved at 17:04 GMT (10:05 PT) – meaning it lasted approximately 3.5 hours and, according to Wired, affected all Grok platforms and services, not just the Android app.
At the same time, Anthropic reported a partial outage from 6:23 to 9:16 PT, with elevated error rates for the Claude Mythos 5.1, Claude Fable 5.1 and Claude Opus 5 models; shortly after 9 PT, the Claude Sonnet 5 model also experienced similar problems. OpenAI recorded a routing error (“routing error”) that made ChatGPT and Codex unavailable to some users between 7:43 and 8:17 PT. There were also isolated reports of problems with the Gemini model, unconfirmed by Google; the incident was not recorded on the Google status dashboard.
Why it matters
This shows that even major AI model providers can fail simultaneously without a clear shared cause – for companies and individuals alike, this is an argument for planning a backup between providers for tasks where an outage lasting hours is a problem.
What was added since the original report
Verified updates
-
The Grok outage was part of a simultaneous all-day incident involving Claude (6:23–9:16 PT) and ChatGPT (7:43–8:17 PT); The cause was an identified outage at the xAI/SpaceX compute center in Memphis; xAI and Anthropic had compute partnerships with SpaceX from May 2026; Google Gemini also reported problems, but the vendor did not confirm them; No shared third-party provider (cloud, CDN) was identified as the cause
- The Grok outage was part of a simultaneous all-day incident involving Claude (6:23–9:16 PT) and ChatGPT (7:43–8:17 PT)
- The cause was an identified outage at the xAI/SpaceX compute center in Memphis
- xAI and Anthropic had compute partnerships with SpaceX from May 2026
- Google Gemini also reported problems, but the vendor did not confirm them
- No shared third-party provider (cloud, CDN) was identified as the cause
Two audiences, two different impacts
What this means
For individuals
Users relying on Claude, ChatGPT, Codex or Grok on the morning of 3 September 2026 (between approximately 6:23 and 10:05 PT) may have encountered errors or service unavailability lasting tens of minutes to several hours.
For a business
Companies relying on APIs for Claude, ChatGPT/Codex or Grok models experienced errors or unavailability for one to three hours on the morning of 3 September 2026, without a clearly confirmed common cause, highlighting the risk of simultaneous outages at multiple providers even without a confirmed shared supplier.
Risks and complianceCheck the original
Event sources
independently confirmed · 2 publishers, 1 independent. We count feeds from the same owner only once.