Simultaneous ChatGPT, Claude, and Grok Outage

OpenAI, Anthropic, and xAI each gave a different official explanation for the September 3 outage: a routing error for ChatGPT and Codex, an unspecified infrastructure issue for Claude, and a hardware failure at xAI's own Memphis compute center for Grok ^[1]. But the surface-level story of three unrelated companies having a bad morning together misses a structural detail that surfaced in follow-up reporting: Anthropic and xAI have a compute partnership tied to that same Memphis site, meaning Claude's frontier capacity and Grok's home data center are not as independent as the separate brand names suggest. That link helps explain why a hardware problem at one company's facility could ripple into another's status page, and why redundancy that looks robust on an org chart can still trace back to the same physical building. Frontier-scale models also run across GPU racks wired together to act as a single giant compute unit with shared memory, which is why there was no idle spare capacity sitting around to fail over into without simply doubling the infrastructure bill.

OpenAI said the ChatGPT and Codex disruption traced to a routing error beginning around 7:43 am PT ^[1], while xAI's parent SpaceXAI apologized for an outage at its Memphis compute center that also hit outside compute partners ^[2], making Grok's the longest outage of the three at roughly three and a half hours ^[1]. Anthropic, meanwhile, described only a general infrastructure issue behind Claude's roughly three-hour outage across Claude.ai, Claude Code, Claude Cowork, and its API ^[1]. Multiple outlets floated a common thread in Microsoft Azure's East US region, since ChatGPT, Claude, and Grok all route meaningful compute or networking through Azure while Google's Gemini, running on its own cloud stack, was comparatively unaffected ^[3][4]. That theory was never officially confirmed, and Cloudflare explicitly denied any disruption on its network during the incident window ^[1]. An OpenAI engineer went further, indicating the ChatGPT failure was a separate routing error unrelated to xAI's Memphis incident ^[5], leaving three distinct company explanations rather than one confirmed shared root cause ^[6].

Because ChatGPT, Claude, and Grok all failed inside the same roughly 90-minute window, treating one AI vendor as a live fallback for another offered far less real-world protection than most enterprise resilience plans assumed ^[7]. Analysts framed the event as proof that organizations have not built business continuity plans for AI outages and are exposed to a new class of operational risk tied to how deeply automated workflows now depend on a handful of providers ^[8][9]. Even Microsoft's own Copilot reportedly suffered stability and downtime issues in the same window despite running on Microsoft's cloud, suggesting whatever went wrong sat in infrastructure layers common across multiple products rather than in any single vendor's code ^[3].

The September 2026 incident extends a pattern rather than starting one. In June 2024, ChatGPT, Claude, and Perplexity went down at the same time in an episode dubbed an 'AI apocalypse' ^[10]. ChatGPT suffered its own extended outage of more than 15 hours in June 2025, also taking down Sora and API access ^[11]. A global Cloudflare failure in November 2025 knocked out major AI platforms that depend on its network alongside tens of thousands of other sites ^[12]. By April 2026, ChatGPT, Claude, and Gemini had already gone down at roughly the same time once before, undermining the common practice of treating the three as interchangeable backups for each other ^[13]. In the three weeks before the September 3 event, Anthropic alone logged 21 separate incidents, part of 25 outages in the trailing 30 days across five components ^[14].

The outage generated more than 37,000 Downdetector reports for OpenAI alone, climbing past 66,000 once combined with Codex, making it one of the most heavily reported AI outages tracked in 2026 ^[3]. Grok's outage ran roughly three hours and thirty-seven minutes, the longest of the three, while Claude's lasted about three hours and six minutes ^[15][16]. Both consumer chatbot apps and workplace tools, including coding assistants like Codex and Claude Code, went down at the same time, disrupting everyday users and developer workflows in the same stroke ^[7][15].