Claude Outage History
This archive contains manually reviewed outage notes for meaningful Claude crowd-report spikes. It is intentionally selective and is not auto-generated from every burst of button clicks.
Each note records the crowd-report timing, what users appeared to experience, what surface looked affected, and how the official provider messaging lined up with the live signal.
Reviewed incidents
24
Manual archive notes published so far
Major incidents
6
Broad or severe disruptions in this archive
Auth + access notes
3
Login and direct access incidents
Tracked downtime
28.8h
Across model, auth, upload, and broad-outage notes
Loading archive browser…
So far, this archive has skewed toward 11 model/API notes and 6 narrower upload, connector, or desktop notes. That split is part of the point: not every “Claude down” report is the same kind of failure.
If you want the higher-level pattern instead of note-by-note reading, open the Claude outage history by surface breakdown.
The template below is what every reviewed incident note should cover. That consistency matters if this archive is going to become genuinely useful instead of becoming another thin “Claude down” page cluster.
- When the crowd signal first moved
- What users appeared to report
- What surface looked affected
- When the spike peaked and eased
- How the official provider status compared
- What uncertainty remained
A crowd spike alone is not enough to justify an incident note. The page should add real value beyond the homepage chart and help someone understand what happened after the fact.
Until then, use the homepage for the live signal, the methodology page for the counting rules, and this explainer for how crowd reports differ from official status updates.