所有系統正常

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

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

Identified: 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.

Identified: 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.

Resolved: This issue has been resolved.

Identified: We are aware of an issue affecting users interacting with subscriptions via Google Play, such as when creating a new subscription on Android devices. Google has confirmed an issue with Google Play, and we are awaiting their further updates.

Resolved: A fix has been deployed for Claude Mythos 5.1 and Claude Fable 5.1 and we are monitoring to ensure it has resolved the issue.

Monitoring: A fix has been deployed for Claude Mythos 5.1 and Claude Fable 5.1 and we are monitoring to ensure it has resolved the issue.

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

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

Resolved: This issue has been resolved. Microsoft has released a September 14 Windows update that fixes it: https://support.microsoft.com/en-us/servicing/os/windows-11/2026/09/kb5129195-windows-11-24h2-25h2-security-update

Identified: A Windows update released September 8 has left Claude Cowork on Windows unable to run local commands, because its workspace can no longer reach your computer's drive. For most users, chat and file reading and editing still work. There's no in-app workaround yet, and restarting or reinstalling won't help. Microsoft has developed a fix and is working to release it. We'll post an update when we have more to share.

Resolved: The issue affecting Claude services has been mitigated.

Identified: We are experiencing slower than normal response times on the Claude API for some customers whose traffic enters through the US Midwest. Users may experience elevated latency and some request timeouts.

Resolved: The issue affecting Claude services has been resolved. Impact occurred from 13:57 to 14:20 UTC

Monitoring: A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery.

Monitoring: A fix has been deployed for Claude Mythos 5.1 and Claude Fable 5.1 and we are monitoring for recovery.

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

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.

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.

Identified: The only affected models right now are Opus 4.8 and Opus 5. The rest of the models have recovered to baseline error rate.

Identified: We are continuing to work on a fix for this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are investigating elevated errors on requests to Claude Sonnet 5. We will provide an update as soon as possible.

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.

Investigating: We are investigating elevated errors on requests to Claude Sonnet 5. We will provide an update as soon as possible.

Resolved: This issue has been resolved.

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.

Resolved: This issue has been resolved.

Monitoring: We are seeing success rates recover across affected services. Core inference and the API are not impacted.

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.

Resolved: This issue has been resolved.

Investigating: We are investigating elevated errors affecting Claude for Microsoft Office 365. We will provide an update as soon as possible.

Resolved: The issue affecting Claude Code has been resolved. Impact occurred from 16∶55 to 19∶16 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.

Resolved: This issue has been resolved.

Monitoring: We have seen success rates return to normal for requests on Claude.ai and are monitoring closely.

Investigating: We are investigating reports of elevated errors affecting chats on claude.ai. We will provide an update as soon as possible.

Resolved: The issue affecting Claude Cowork and Claude Code on the web has been resolved.

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

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 will provide an update as soon as possible.

Resolved: This issue has been resolved.

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.

Resolved: This issue has been resolved.

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.

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.

Identified: 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.

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

Identified: 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.

Resolved: This issue has been resolved.

Investigating: We are investigating elevated errors on requests to some Claude models. We will provide additional updates as soon as possible.

Resolved: This issue has been resolved.

Investigating: We are investigating elevated errors affecting Google connectors (Sheets, Docs, Slides, and Chat) and custom Google integrations on Claude.ai. Core functionality is not affected. We will provide an update as soon as possible.