A quiet status page is not a promise that everything works. Labs open an incident once they've confirmed one, and that can be a while after your requests start failing. If you're seeing errors and this page says nothing, you're probably early rather than wrong.
What we can say is what Anthropic published and when, for Claude, Claude Code and the Anthropic API.
Sep 3 , 16:23 UTC
Resolved - The issue affecting Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5 has been resolved. Impact has ended as of 9:16 PT / 16:16 UTC.
Sep 3 , 16:06 UTC
Monitoring - A fix has been deployed for Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5 and we are monitoring for recovery.
Sep 3 , 15:25 UTC
Update - The only affected models right now are Opus 4.8 and Opus 5. The rest of the models have recovered to baseline error rate.
Sep 3 , 14:49 UTC
Update - We are continuing to work on a fix for this issue.
Sep 3 , 13:50 UTC
Update - An exhaustive list of…
Sep 3 , 12:56 UTC
Resolved - This incident has been resolved.
Sep 3 , 12:47 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Sep 3 , 12:37 UTC
Investigating - We are investigating elevated errors on requests to Claude Sonnet 5. We will provide an update as soon as possible.
Sep 2 , 21:44 UTC
Resolved - The issue affecting Claude Sonnet 5 has been resolved. Impact occurred from 2:05pm PT / 21:05 UTC to 2:19pm PT / 21:19 UTC.
Sep 2 , 21:17 UTC
Investigating - We are investigating elevated errors on requests to Claude Sonnet 5. We will provide an update as soon as possible.
Sep 2 , 01:24 UTC
Resolved - This issue has been resolved.
Sep 1 , 23:26 UTC
Monitoring - We have identified and resolved an issue where users who reached a balance of zero usage credits saw delays in the availability of newly purchased credits, resulting in some requests to the Claude API receiving 'credit balance is too low' errors erroneously. This affected credits purchased from 05:10am PT / 12:10 UTC to 2:35pm PT / 21:35 UTC. At this time, newly purchased credits should be available as expected and we are working to resolve any remaining impact.
Sep 1 , 18:07 UTC
Resolved - This issue has been resolved.
Sep 1 , 17:52 UTC
Monitoring - We are seeing success rates recover across affected services. Core inference and the API are not impacted.
Sep 1 , 17:05 UTC
Investigating - We are investigating reports of degraded performance affecting some Claude services, including docs.claude.com. We are working to resolve these issues and will provide an update as soon as possible.
Sep 1 , 16:22 UTC
Resolved - This issue has been resolved.
Sep 1 , 16:02 UTC
Investigating - We are investigating elevated errors affecting Claude for Microsoft Office 365. We will provide an update as soon as possible.
Aug 31 , 20:36 UTC
Resolved - The issue affecting Claude Code has been resolved. Impact occurred from 16∶55 to 19∶16 UTC.
Aug 31 , 19:21 UTC
Investigating - We are investigating reports of degraded performance affecting Claude in Slack, Claude Code on the web, and Code Review. We will provide an update as soon as possible.
Aug 31 , 17:52 UTC
Resolved - This issue has been resolved.
Aug 31 , 17:32 UTC
Monitoring - We have seen success rates return to normal for requests on Claude.ai and are monitoring closely.
Aug 31 , 17:23 UTC
Investigating - We are investigating reports of elevated errors affecting chats on claude.ai. We will provide an update as soon as possible.
Aug 28 , 20:21 UTC
Resolved - The issue affecting Claude Cowork and Claude Code on the web has been resolved.
Aug 28 , 18:21 UTC
Monitoring - A mitigation has been applied for the issue affecting Claude Cowork and Claude Code on the web, and we are monitoring for recovery. Sessions that disconnected earlier can be retried
Aug 28 , 17:22 UTC
Identified - We have identified an issue with an upstream cloud provider affecting Claude Cowork and Claude Code on the web. Some sessions may fail to start or disconnect mid-task; affected sessions can be retried. We are in contact with the provider and…
Aug 24 , 20:26 UTC
Resolved - This issue has been resolved.
Aug 24 , 20:11 UTC
Monitoring - We have identified and resolved an issue which resulted in errors when attempting to access Claude.ai, including logging in via subscriptions for Claude Code. Errors occurred between 1:00pm (20:00 UTC) through 1:08pm PT (20:08 UTC). We are monitoring closely to ensure no further issues.
Aug 24 , 17:16 UTC
Resolved - This issue has been resolved.
Aug 24 , 17:12 UTC
Investigating - From 9:02–9:08am PT / 16:02–16:08 UTC) users experienced issues when logging into Claude.ai, including for connecting Claude Code with subscription. At this time, this issue has been resolved, but we are continuing to investigate a potential issue impacting users of the Claude.ai desktop application.
Aug 24 , 08:30 UTC
Resolved - 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.
Aug 24 , 07:47 UTC
Update - 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.
Aug 24 , 06:42 UTC
Update - We are continuing to work to resolve issues causing elevated requests on multiple models. We will provide an update as soon as possible.
Aug 24…
If the status page is clear and it's still broken
Check what shipped. A client library or a coding tool that updated this morning explains a surprising number of sudden breakages, and the changelogs list those by the hour.
Then check whether the model you're calling is on its way out. The deprecation list has the retirement dates each lab has published.