Elevated errors on claude.ai, the Claude API, and Claude Code
Anthropic reports elevated errors on claude.ai, the Claude API, Claude Code, and Claude Cowork. Anthropic is investigating the problem.
State
Investigating
Started
Ongoing for
42 min
Worst impact
Partial outage
Timeline
1 updateInvestigating
42 min 100%
Updates
Times in UTCAs posted by Anthropic
We are investigating reports of degraded performance affecting claude.ai, the Claude API, and Claude Code. We will provide an update as soon as possible.
Affected components
4Anthropic in the last 90 days
Full historyIncidents in 90 days
47
Days with an incident
41
Median duration
42 min
This incident
About the median
Other Anthropic incidents
All incidentsAnthropic·Elevated errors on claude.ai, Claude Code, and platform.claude.com
Anthropic reported elevated errors on claude.ai, Claude Code, platform.claude.com, and Claude Cowork. Anthropic later confirmed the issue is resolved. The outage lasted about 120 minutes.
Anthropic·Elevated errors affecting the Microsoft 365 connector
Anthropic reports elevated errors in the Microsoft 365 connector on claude.ai and Claude Cowork. Mail, calendar and search tools fail for most requests, and Claude for Outlook is also affected. Anthropic identified the cause as a Microsoft 365 service incident and continues to work with the upstream provider.
Anthropic·Elevated errors on Fable 52 and Mythos 52
Overloaded errors on Fable 5.2 and Mythos 5.2 for four minutes. Incident has been mitigated.
Anthropic·Degraded performance for Claude Fable 5.1
Claude Fable 5.1 had degraded performance. The issue affected claude.ai, the Claude API, Claude Code, and Claude Cowork. Anthropic reports that the incident is resolved.
Anthropic·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.
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.live/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.live/feed.xml?providers=anthropic/feed subscribe https://outages.live/feed.xml?providers=anthropicFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane