Anthropic
AI safety company founded by ex-OpenAI researchers Dario and Daniela Amodei. Builds the Claude family of large language models with a focus on steerability, interpretability, and reducing harmful outputs.
Products
Claude (Opus · Sonnet · Haiku) · Claude.ai · Claude Code · Anthropic API
Reliability — last 7d
Composite score
Uptime
Incidents
Median MTTR
What's breaking (last 7d)
Components ranked by incident count. Click a row for the incident list. Down-time is attributed proportionally for multi-component incidents.
| Component | Incidents | Down (attr.) | Median MTTR | Last |
|---|---|---|---|---|
platform.claude.com (formerly console.anthropic.com) | 6 | 2h 26m | 56m | 1d ago |
claude.ai | 5 | 2h 11m | 57m | 1d ago |
Claude API (api.anthropic.com) | 5 | 2h 11m | 57m | 1d ago |
Claude Code | 5 | 2h 11m | 57m | 1d ago |
Claude Cowork | 5 | 3h 33m | 57m | 1d ago |
Claude for Government | 3 | 1h 18m | 57m | 1d ago |
Type of failure
Categorised from the public incident headlines (outage / latency / auth / etc.). Click a category to drill in.
When it breaks
Incident starts by weekday × hour, UTC. Hover a cell for incident detail.
Hour of day · UTC
Anthropic — incidents by day (last 7d)
Worst incidents
Ranked by severity-weighted duration (impact × wall-clock). Click any incident for the full update timeline.
Score breakdown
SLA compliance
How often does this provider clear their stated availability target?
Incident history
showing 6 of 200 · 4 of 105 days
Most likely outage time
Hottest hour
Worst day
Worst time of day
How fast they fix things
Distribution of incident resolution times.
Typical fix
57m
half of incidents resolve faster
On a bad day
5h 56m
9 in 10 resolve faster than this
Distribution
Method: a rolling quarter (13 weeks ≈ 91 days). Each cell is one 7-day slice of severity- and component-weighted uptime (same calc as the score's uptime card); red when the slice dips below the stated SLA.