The Three AI Outages Overlapped for 85 Minutes
Official status records logged the Claude, Grok, and ChatGPT incidents of 3 September 2026 starting 2 hours 21 minutes apart, but all three had unresolved incidents running at once for 85 minutes. Anthropic's and OpenAI's own incident histories show six stretches of concurrent unresolved incidents, beginning on four dates in the 31 days to 4 September, including 3 September.
This piece has a Chinese companion on aire: 三家 AI 紅燈重疊的 85 分鐘 (in Chinese)
Four incidents, logged in official status records, starting 2 hours and 21 minutes apart: Claude’s Sonnet 5 alert at 20:37 Taipei time, Claude’s broader multi-model incident at 21:26, Grok’s outage four minutes later at 21:30, and ChatGPT/Codex at 22:58, all on 3 September 2026.
Line them up on one clock and the idea that all three went down at once turns out to be compressed. The window where Claude, Grok, and ChatGPT all had an unresolved incident running at the same time was 85 minutes. Widen the clock to the past 31 days, and two of those vendors, Anthropic and OpenAI, logged unresolved incidents at the same time in six stretches beginning on four dates, including 3 September.
Opening accounts at three AI vendors is not the same as holding three insurance policies.
The Four Incidents Started 2 Hours and 21 Minutes Apart
| Service | Incident name (official) | Start | End | Official duration |
|---|---|---|---|---|
| Claude | Elevated errors for Claude Sonnet 5 | Sep 3, 20:37 | Sep 3, 20:56 | ~19 min |
| Claude | Elevated errors for multiple models | Sep 3, 21:26 | Sep 4, 00:23 | ~2h 57m |
| Grok in X | Models outage | Sep 3, 21:30 | Sep 4, 01:05 | 3h 35m |
| ChatGPT/Codex | Elevated errors across ChatGPT and Codex | Sep 3, 22:58 | Sep 4, 00:55 | ~1h 57m |
All times are Taipei (UTC+8). Claude’s and OpenAI’s rows come from each vendor’s own statuspage incident data. The Grok in X row comes from its status.x.ai incident page. Four rows cover four incidents.
The start times run 20:37, 21:26, 21:30, 22:58, 2 hours and 21 minutes apart, not simultaneous. The overlap window starts at the latest of the three start times, 22:58, and ends at the earliest of the three end times, 00:23. That is 85 minutes in which Claude, Grok, and ChatGPT all had an unresolved incident running. Anthropic’s own update gives an earlier impact-ended time, 00:16 rather than the incident’s formal close at 00:23. Measured to 00:16, the same overlap is 78 minutes.
Claude logged two incidents that night. The first affected only Claude Sonnet 5 and lasted 19 minutes. The second was broader: a 21:50 update listed Mythos/Fable 5.1, Mythos/Fable 5, Opus 5, Opus 4.8 and Opus 4.6 as affected, across claude.ai, the Claude API, Claude Code, and Claude Cowork, with impact marked major.
By 23:25, Anthropic wrote: “The only affected models right now are Opus 4.8 and Opus 5. The rest of the models have recovered to baseline error rate.” The closing update said: “Impact has ended as of 9:16 PT / 16:16 UTC,” which is 00:16 Taipei time on 4 September. The other models were back to baseline before 23:25; Opus 4.8 and Opus 5 took at least 51 minutes longer.
The Grok in X incident ran for roughly 3 hours 35 minutes. Its page marked the issue resolved and traffic healthy again.
Six Overlap Stretches Began on Four Dates in the 31-Day Window
Pull Anthropic’s and OpenAI’s own incident histories, their public statuspage incident data, with each vendor’s full set of start and resolved times. Take the union within each vendor, then the intersection across the two, and a second pattern shows up.
The two feeds’ shared coverage window runs from 20:43 on 4 August to 17:22 on 4 September, about 30.9 days. Claude logged 27 incidents in that window; OpenAI logged 25. The share of time with any unresolved incident running was 5.7% for Claude and 11.0% for OpenAI.
The intersection comes out as six stretches, each a period when Claude and OpenAI both had an unresolved incident running, adding up to 6.0 hours, with the stretches beginning on four dates:
- 13 August, 22:33–00:08 (95 min)
- 1 September, 01:23–01:52 (29 min)
- 1 September, 03:21–04:28 (67 min)
- 2 September, 00:02–00:22 (20 min)
- 2 September, 01:05–02:07 (62 min)
- 3 September, 22:58–00:23 (85 min)
The 85 minutes on 3 September is the second-longest of the six; the longest is the 95 minutes on 13 August. Two vendors overlapping is not new in this window. What 3 September adds is a third vendor, Grok, inside the same stretch.
Two limits belong next to those numbers. First, each statuspage feed only returns the most recent 50 or 25 incidents, so the window is capped at 31 days by how the data was pulled here. The ratio cannot be extrapolated to a full year.
Second, an unresolved incident is not the same as an outage. Most of the incidents above affected only some models or some regions, and a red status page does not mean every request failed.
Three Accounts Do Not Solve Two Problems
Opening three accounts takes minutes. Two problems after that don’t.
The first is whether the work can actually move. A companion piece on aire, How long does it take to switch from Claude to Codex? (in Chinese), breaks the friction into three layers: credentials, memory, and tooling. That piece’s own reading is that credentials are usually the easiest of the three, and that memory and tooling are where a switch actually gets stuck. A second account is not a usable backup unless the work can move across all three layers. Otherwise it is a spare login page.
The second is knowing when to switch. A status page records what the provider has marked as an incident; it does not say whether the request in front of you will succeed. In Claude’s own updates, some models were back to baseline while Opus 4.8 and Opus 5 stayed affected.
The 31-day numbers, 5.7% for Claude, 11.0% for OpenAI, and six overlap stretches beginning on four dates, can’t answer how many accounts is enough, because that isn’t what they measure.
The question worth calculating is a different one: which pieces of work cannot tolerate a window like the 85 minutes in which all three vendors had unresolved incidents at once? That is where the backup belongs.
Frequently asked questions
What happened to Claude, Grok, and ChatGPT on 3 September 2026?
Official status pages logged four incidents that evening, Taipei time: elevated errors on Claude Sonnet 5 from 20:37 to 20:56; a broader Claude incident affecting multiple models from 21:26 to 00:23 the next day; a Grok in X outage from 21:30 to about 01:05 the next day; and elevated errors across ChatGPT and Codex from 22:58 to 00:55.
Were Claude, Grok, and ChatGPT actually down at the same time?
Not exactly at once. The four incidents started 2 hours 21 minutes apart, from 20:37 to 22:58. The window where Claude, Grok, and ChatGPT all had an unresolved incident running at the same time was 85 minutes, from 22:58 to 00:23 the next day (or 78 minutes using the impact-ended time Anthropic wrote into its own update). An unresolved incident on a status page is also not the same as a service being fully unavailable.
Can subscribing to multiple AI vendors prevent this kind of overlap?
Multiple accounts can help when an affected workflow can move to a vendor without a concurrent unresolved incident. During the shared 85-minute window on 3 September, all three vendors had unresolved incidents, but that does not mean every service or request was unavailable. The two things multiple accounts don’t solve on their own are whether work can actually move to a different vendor, since credentials, memory, and tooling all have to carry over, and how to know, in the moment, that it’s time to switch. Status pages aren’t built to answer that second question.