Live

Elevated errors for multiple models

This issue has been resolved. From 9:50pm PT / 04:50 UTC through 00:36am PT / 07:36 UTC, users saw elevated errors on requests to Claude models, including Claude Opus 5 and Fable 5.

The latest update from Anthropic.

State

Resolved

Started

69 d ago

2026-08-24 05:06 UTC

Lasted

3 h 24 min

until 2026-08-24 08:30 UTC

Worst impact

Partial outage

Timeline

5 updates
05:0605:5706:4807:3908:30
Partial outageUpdate postedTimes in UTC

Investigating

21 min 10%

Identified

3 h 3 min 90%

Updates

Times in UTC

As posted by Anthropic

Resolved2026-08-24 08:30 UTC

This issue has been resolved. From 9:50pm PT / 04:50 UTC through 00:36am PT / 07:36 UTC, users saw elevated errors on requests to Claude models, including Claude Opus 5 and Fable 5.

Identified2026-08-24 07:47 UTC

At this time, we have seen errors stabilize on Opus 5 and Fable 5, and are working to fully resolve success rates on all affected models. We will provide an update as soon as possible.

Identified2026-08-24 06:42 UTC

We are continuing to work to resolve issues causing elevated requests on multiple models. We will provide an update as soon as possible.

Identified2026-08-24 05:27 UTC

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

Investigating2026-08-24 05:06 UTC

We are investigating elevated errors on requests to Claude Mythos 5, Claude Fable 5, Claude Opus 5, and Claude Opus 4.8. 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

3.0× 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