Live

Elevated errors for multiple models

This issue has been resolved. Impact occurred from 5:50pm PT / 00:50 UTC to 7:10pm PT / 02:10 UTC.

The latest update from Anthropic.

State

Resolved

Started

40 d ago

2026-09-22 00:57 UTC

Lasted

1 h 38 min

until 2026-09-22 02:35 UTC

Worst impact

Partial outage

Timeline

5 updates
00:5701:2101:4602:1002:35
Partial outageUpdate postedTimes in UTC

Investigating

20 min 21%

Identified

54 min 55%

Monitoring

24 min 24%

Updates

Times in UTC

As posted by Anthropic

Resolved2026-09-22 02:35 UTC

This issue has been resolved. Impact occurred from 5:50pm PT / 00:50 UTC to 7:10pm PT / 02:10 UTC.

Monitoring2026-09-22 02:11 UTC

We have seen success rates return to normal across affected models, and are monitoring closely to ensure no further issues.

Identified2026-09-22 01:35 UTC

We are continuing to work to resolve errors affecting some models. At this time, requests to Claude Fable 5 and 5.1 and Mythos 5 and 5.1 have returned to normal success rates. We are working to resolve remaining errors affecting Claude Opus 5, and will provide an additional update shortly.

Identified2026-09-22 01:17 UTC

We have identified the cause of elevated errors on requests to Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5 and are working on a fix. We will provide an update as soon as possible.

Investigating2026-09-22 00:57 UTC

We are investigating elevated errors on requests to Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5. We will provide an update as soon as possible.

Affected components

4
claude.aiClaude API (api.anthropic.com)Claude CodeClaude Cowork

Anthropic in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

50

Days with an incident

42

Median duration

1 h 8 min

This incident

1.5× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 days
median 1 h 8 min
90 days agoToday

Other Anthropic incidents

All incidents

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=anthropic
Slack
/feed subscribe https://outages.cc/feed.xml?providers=anthropic

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane