ChatGPT, Claude and Grok all went down Thursday morning within minutes of each other. The precise trigger remains unclear, raising concerns about shared infrastructure in the AI sector.
- OpenAI, Anthropic and xAI models experienced downtime at the same time
- SpaceX cited a Memphis compute‑center outage as the cause for Grok
- No definitive third‑party provider was identified
Chronology of the Incident
From 6:23 AM PT to 10:05 AM PT on Thursday, three leading frontier AI models—OpenAI’s ChatGPT and Codex, Anthropic’s Claude series, and xAI’s Grok—experienced service interruptions. While the timing suggested a common link, each company reported distinct internal causes.
Company Statements
OpenAI spokesperson Kathleen Chaykowski said a routing error at 7:43 AM PT rendered ChatGPT and Codex unavailable for some users, a problem that was resolved by 8:17 AM PT. Anthropic announced a “partial outage” at 6:23 AM PT affecting Claude Mythos 5.1, Claude Fable 5.1 and Claude Opus 5, and confirmed a fix by 9:16 AM PT. xAI reported Grok issues starting at 6:30 AM PT and marked the incident resolved at 10:05 AM PT.
SpaceX’s Involvement
SpaceX, the parent of xAI, attributed the Grok disruption to an outage at its Memphis compute center and publicly apologized to “impacted compute partners.” The partnership between SpaceX, Anthropic and xAI was announced in May as a joint compute initiative.
Why This Matters
BozokMedia analysis shows that simultaneous outages across leading AI providers hint at a fragile dependency on shared infrastructure, potentially reshaping how firms negotiate compute contracts and diversify cloud strategies.
“The continuity of AI services now hinges as much on backend infrastructure stability as on the models themselves.”
Frequently Asked Questions
Q1: Was a cloud provider responsible for the outages?
A: Neither OpenAI nor Anthropic cited an external provider, and major cloud services reported no incidents.
Q2: What steps can firms take to avoid synchronized outages?
A: Adopting multi‑cloud architectures and strengthening routing redundancies can mitigate such systemic risks.