← Back to Anthropic's check readings
We started checking Anthropic on August 20, 2026, which is 62 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Anthropic reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Anthropic's own status page declared. Below it, any public chatter we saw about Anthropic and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Anthropic's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api
Our probes, auth (primary)
Unverified user reportsNo reports about Anthropic in the last 24 hours, which is not evidence that nothing is wrong.
Anthropic's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Anthropic's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Anthropic next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
- Bluesky posts3 in the last hour (prior day averaged 1.2/hour)
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
Anthropic's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Issue with spend limitsAll systems operational
Oct 7, 2026, 9:23 PM UTC to Oct 7, 2026, 9:23 PM UTC (0 min)resolved
their latest update (Oct 7, 2026, 9:23 PM UTC): We have identified an issue which resulted in some organizations to be incorrectly paused for having reached their spend limit, resulting in refused requests on the Claude API, Claude.ai, Claude Code, Claude Security, and Claude Cowork. This is now resolved.
Elevated errors on platform.claude.comPartial outage
Oct 7, 2026, 1:25 PM UTC to Oct 13, 2026, 6:00 PM UTC (6d 4h)resolved
their latest update (Oct 13, 2026, 6:00 PM UTC): This issue has been resolved.
Elevated errors loading usage data on platform.claude.comPartial outage
Oct 7, 2026, 1:20 AM UTC to Oct 7, 2026, 2:33 AM UTC (1h 13m)resolved
their latest update (Oct 7, 2026, 2:33 AM UTC): This incident has been resolved. From 17:00 PT on October 6 / 00:00 UTC on October 7 to 18:40 PT on October 6 / 01:40 UTC on October 7, many requests to load usage data on the platform.claude.com Usage page and the Admin API usage report returned errors.
Elevated errors for Claude Opus 5.5Partial outage
Oct 6, 2026, 12:24 PM UTC to Oct 6, 2026, 12:43 PM UTC (19 min)resolved
their latest update (Oct 6, 2026, 12:43 PM UTC): The issue affecting Claude Opus 5.5 has been resolved.
Elevated errors for Claude Mythos 5.1 and Claude Fable 5.1Partial outage
Oct 5, 2026, 1:05 PM UTC to Oct 5, 2026, 1:21 PM UTC (16 min)resolved
their latest update (Oct 5, 2026, 1:21 PM UTC): The issue affecting Claude Mythos 5.1 and Claude Fable 5.1 has been resolved. Impact occurred from 05:40 PT / 12:40 UTC to 06:10 PT / 13:10 UTC.
Delayed credits on the Claude PlatformMinor incident
Oct 1, 2026, 4:20 PM UTC to Oct 1, 2026, 10:36 PM UTC (6h 16m)resolved
their latest update (Oct 1, 2026, 10:36 PM UTC): This issue has been resolved.
Elevated errors on claude.ai, Claude Code, Claude Cowork and the Claude APIPartial outage
Sep 29, 2026, 2:21 PM UTC to Sep 29, 2026, 4:27 PM UTC (2h 6m)resolved
their latest update (Sep 29, 2026, 4:27 PM UTC): The issue affecting Claude.ai, the Claude desktop and mobile apps, Claude Code, Claude Cowork, and the Claude API has been resolved, and services have been operating normally since recovery. Impact occurred from 07:00 PT / 14:00 UTC to 07:59 PT / 14:59 UTC.
Elevated errors for multiple modelsPartial outage
Sep 22, 2026, 12:57 AM UTC to Sep 22, 2026, 2:35 AM UTC (1h 38m)resolved
their latest update (Sep 22, 2026, 2:35 AM UTC): This issue has been resolved. Impact occurred from 5:50pm PT / 00:50 UTC to 7:10pm PT / 02:10 UTC.
Issues with Google Play subscriptionsAll systems operational
Sep 16, 2026, 4:18 PM UTC to Sep 16, 2026, 4:51 PM UTC (33 min)resolved
their latest update (Sep 16, 2026, 4:51 PM UTC): This issue has been resolved.
Intermittent error spikes for Claude Mythos 5.1 and Claude Fable 5.1Partial outage
Sep 15, 2026, 9:48 AM UTC to Sep 15, 2026, 11:14 AM UTC (1h 26m)resolved
their latest update (Sep 15, 2026, 11:14 AM UTC): A fix has been deployed for Claude Mythos 5.1 and Claude Fable 5.1 and we are monitoring to ensure it has resolved the issue.
Showing the 10 most recent of 75 incidents Anthropic has declared in the history we hold.
These entries are Anthropic's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Anthropic's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.