Claude outage history

An outage began around 1:30 PM UTC after elevated errors affected Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5. Users attempting to use Claude API (api.anthropic.com), Claude Code, Claude Cowork, or claude.ai encountered failed requests and timeouts as the models degraded. StatusGator logged an Early Warning Signal at Sep 3, 2026 1:25 PM UTC, about five minutes before Claude acknowledged the problem, indicating early user-facing signs of the outage. The disruption persisted for most of the afternoon, affecting multiple models and services across the Claude suite.

Users attempting to use Claude Sonnet 5 encountered elevated errors across Claude API (api.anthropic.com), Claude Code, Claude Cowork, and claude.ai. The incident began at Sep 3, 2026 12:43 PM UTC with elevated errors on requests to Claude Sonnet 5 and a notification that engineers were investigating. The disruption lasted about five minutes and was resolved by Sep 3, 2026 12:48 PM UTC as all affected components returned to normal and service health was restored.

An outage briefly disrupted Claude Sonnet 5, causing elevated errors on requests and degraded responses across Claude Cowork, claude.ai, Claude API (api.anthropic.com), and Claude Code. The disturbance began at 9:23 PM UTC and was resolved by 9:48 PM UTC, lasting about 25 minutes.

Claude's status page documented an investigation into the elevated errors and updates as the team worked to restore normal service. By the time services returned to normal, all affected components were listed as up.

Claude experienced degraded credit-purchase flow on 12:10 PM UTC to 9:35 PM UTC, with newly purchased credits not becoming available as expected and some Claude API requests returning 'credit balance is too low' errors for purchases made in that window. The Claude Console indicated a degraded condition starting around 11:28 PM UTC as the issue unfolded.

The problem was mitigated, and normal operations resumed by 1:28 AM UTC, with newly purchased credits available again and API usage returning to typical levels after roughly 13 hours of degraded service.

Users experienced degraded performance on Claude Console (platform.claude.com) and Claude for Microsoft Office 365, including docs.claude.com. The incident began at 5:08 PM UTC as Claude acknowledged degraded performance and opened an investigation across affected services.

By 5:53 PM UTC, status updates noted recovery in success rates and confirmed that core inference and the API were not impacted. The issue was resolved by 6:08 PM UTC when components returned to normal, restoring full operation across Claude Console and Claude for Office 365.

Users relying on Claude.ai within Microsoft Office 365 encountered degraded performance and elevated errors. The degradation started at Sep 1, 2026 4:03 PM UTC and progressed through the early part of the incident, with the service returning to normal around Sep 1, 2026 4:23 PM UTC. A single user reported issues at 3:30 PM UTC before the status page acknowledged the problem, indicating limited early visibility from user feedback.

During the event, Claude.ai for Office 365 showed ongoing issues as updates rolled in, before the system recovered to normal operation. The key impacted component was claude.ai, with users experiencing degraded performance and errors while attempting Office 365 integrations.

Users began experiencing degraded performance on claude.ai in Slack, Claude Code on the web, and Code Review around Aug 31, 2026 7:23 PM UTC. The Claude status page listed a degraded performance for claude.ai and Claude Code and indicated the team was investigating. The impact appeared as slower responses and intermittent issues rather than a full outage.

Claude.ai users experienced a brief degradation in chat performance. The incident began at Aug 31, 2026 5:38 PM UTC when the Claude status page reported degraded performance and investigations into elevated errors affecting chats were opened. The service returned to normal by Aug 31, 2026 5:43 PM UTC, with users able to resume normal usage shortly thereafter. A user reported issues around 5:15 PM UTC, indicating some awareness of the problem before the official acknowledgment. The episode lasted about five minutes and did not indicate a broad regional impact.

Users attempting to chat with Claude.ai experienced degraded performance and elevated errors in Claude.ai chats. A small volume of user reports began around 5:15 PM UTC. The Claude.ai component was listed as degraded on the status page at Aug 31, 2026 5:23 PM UTC as engineers investigated the issue. The problem was resolved by Aug 31, 2026 5:33 PM UTC, with Claude.ai returning to normal operation, after about ten minutes of degraded performance. During the incident, status updates described an ongoing investigation into elevated chat errors and a commitment to provide updates as soon as possible; the impact was limited to Claude.ai chats and did not affect all Claude services.

Users of Claude Code and Claude Cowork on the web encountered elevated errors starting at 5:23 PM UTC due to an upstream cloud provider issue. Some sessions may fail to start or disconnect mid-task, though retrials were possible. The incident affected Claude Code and Claude Cowork, with those components listed as degraded during the disruption as teams coordinated with the upstream provider and prepared updates. A mitigation was applied at 6:23 PM UTC and monitoring for recovery began.

By 8:23 PM UTC, the issue had been resolved and Claude Code and Claude Cowork returned to normal operation as the provider mitigated the problem and observed recovery.