Elevated errors for Claude Sonnet 5
This incident has been resolved.
The latest update from Anthropic.
State
Resolved
Started
59 d ago
2026-09-03 12:37 UTC
Lasted
19 min
until 2026-09-03 12:56 UTC
Worst impact
Partial outage
Timeline
3 updatesInvestigating
10 min 51%
Monitoring
9 min 49%
Updates
Times in UTCAs posted by Anthropic
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are investigating elevated errors on requests to Claude Sonnet 5. We will provide an update as soon as possible.
Affected components
4Anthropic in the last 90 days
Full historyIncidents in 90 days
50
Days with an incident
42
Median duration
1 h 8 min
This incident
72% shorter than the median
Other Anthropic incidents
All incidentsAnthropic·Elevated errors affecting the Google Calendar connector
The issue affecting the Google Calendar connector on claude.ai, Claude Code, and Claude Cowork has been resolved. Impact occurred from 04:07 PT / 11:07 UTC on October 26 to 11:52 PT / 18:52 UTC on October 28.
Anthropic·Elevated errors affecting the Gmail connector
The issue affecting the Gmail connector on claude.ai, Claude Code, and Claude Cowork has been resolved. Impact occurred from 16:00 PT / 23:00 UTC on October 27 to 22:29 PT on October 27 / 05:29 UTC on October 28.
Anthropic·Elevated errors for Claude Sonnet 5.5
The issue affecting claude.ai, the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 07:42 PT / 14:42 UTC to 08:17 PT / 15:17 UTC.
Anthropic·Elevated errors for Claude Sonnet 5.5
The issue affecting Claude services has been resolved.
Anthropic·Elevated errors for Claude Fable 5.1
The issue affecting Claude services has been resolved. Impact occurred from 01:08 PT / 08:08 UTC to 01:29 PT / 08:29 UTC.
Follow Anthropic
Your coding agent knows when Anthropic is down, and tells you when a failure is theirs, not yours. You can also get Anthropic incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "anthropic" and tell me if Anthropic has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=anthropic/feed subscribe https://outages.cc/feed.xml?providers=anthropicFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane