A rare four-way outage

On the morning of September 3, 2026 U.S. Eastern time, four major AI services — ChatGPT, Claude, Grok, and Gemini — experienced significant disruptions within a span of under three hours. Ars Technica, drawing on each vendor's status pages and DownDetector data, summed up the window bluntly: having all four frontier models concentrate failures in the same stretch is "practically unheard of."

Anthropic spoke up first, reporting a partial outage at 9:23 ET

Anthropic was the first to acknowledge the problem publicly. Per status.claude.com incident 461yvfrzpwtt, the company flagged "elevated errors" affecting Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5 at 9:23 ET, identified the cause roughly 15 minutes later, and marked the issue resolved at 12:16 ET — a roughly three-hour incident. Just after noon, a separate event (288w7p4hk1l1) hit Claude Sonnet 5, showing that multiple Claude model families were sequentially stressed within a single workday.

OpenAI followed at 10:43 ET, wrapped at 12:55

OpenAI published incident 01M1KWEDH417T2CF44YYHZDFCR on status.openai.com at 10:43, reporting "elevated errors" and degraded performance for ChatGPT and Codex. A mitigation was deployed within roughly half an hour, and the incident was marked resolved at 12:55. Ars notes that OpenAI's published 90-day availability stood at 99.63% for ChatGPT and 100% for ChatGPT Codex, putting this squarely in "two-decimals-after-the-point" territory.

Grok and Gemini stayed silent, but the data did not

xAI's Grok surfaced a user-facing "is experiencing issues" error message, while DownDetector reports on Grok jumped from fewer than 10 before 9:00 ET to 1,365 by 9:45, then settled to 273. Google never publicly acknowledged any Gemini trouble, but DownDetector counts on Gemini leapt from about 23 around 10:30 to 412 just after 11:00, and StatusGator labelled the Gemini API status as "likely outage" between 10:45 and 11:15. Both companies stuck to the same playbook: leave no trace on the official status page, and let third-party monitoring take the public-relations hit.

Hyperscalers were clean, but community data wobbled

Notably, the three hyperscalers most often blamed for upstream failure — AWS, Azure, and Cloudflare — posted no major incidents on their own status pages. Yet DownDetector still showed visible spikes for all three that morning, hinting that an upper-layer model failure briefly pushed traffic sideways through other SaaS surfaces before looping back to the cloud itself. Ars framed it as a "model layer broke, public cloud stayed up" split — itself a signal worth keeping.

Commentary: this is a model-layer single point, not a cloud-layer one

The most important takeaway is where the failure was sliced. Four models from four different companies, running on different clouds, with different inference stacks and GPU clusters — yet all failed at nearly the same moment. That argues against the failure originating in physical infrastructure. More plausible explanations include: enterprise traffic sitting behind multi-model failover that turned one outage into cascading pressure on the next provider; an upstream vendor (CDN, identity, DNS, load-balancing SaaS) acting as an implicit shared dependency at that instant; or a synchronized training/inference framework release that introduced a time-windowed regression.

Regardless of the cause, this episode is a reminder that the much-cited "99.x% frontier-model availability" number is measured by status pages, not by real user experience. When four flagship products go silent in the same morning of the same workday, the figure that actually matters for both enterprises and individuals is "global AI service availability" — and that number sits well below any single vendor's self-report.

Next time someone tells you "multi-model failover is stable enough," pull this one back up.

References