21,228 outages in February - Here are the biggest:
There were 95 Claude outages since January 2026 which are summarized below, including incident details, duration, and resolution information.
Claude not working for you?
Claude not working for you?
The Claude service experienced an outage starting at with elevated errors on Claude Sonnet 4.5 that affected claude.ai, platform.claude.com, and Claude Code. A later update clarified that the affected model was Sonnet 4.6, and all three components returned to normal by . The outage lasted about 1 hour and 5 minutes.
From , Claude Opus 4.6 began showing elevated errors across Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. Users reported failures and slower responses, with a surge in reports in the days that followed indicating broad disruption across Opus 4.6 and related models such as Sonnet 4.5 and Haiku 4.5/4.6. The Claude status page published multiple updates as engineers investigated, rolled out fixes, and monitored results.
The outage lasted roughly 6 days and 22 hours, spanning from to . The service saw a high volume of user reports, and status updates described ongoing investigations and corrective actions across several models and components. With issues reported globally, users experienced intermittent responses, missing results, and delays across Claude API, claude.ai, platform.claude.com, and Claude Code as teams worked to restore full functionality. As of the latest updates, some resilience remained degraded and the incident continued to be actively investigated.
Claude Opus 4.6 began showing elevated errors at , causing degraded performance across Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. Users reported issues starting as early as , with messages describing unavailability and connection errors. The incident persisted for about 3 hours and 10 minutes, ending at .
The provider issued four status updates during the incident: first at noting an investigation, then at that a fix was being implemented, followed by reporting that a fix had been deployed and results were being monitored, and finally confirming restoration of services.
Claude Opus 4.6 experienced elevated errors beginning at , impacting Claude API (api.anthropic.com), claude.ai, and Claude Code. Users reported outages and degraded experiences, including apps and websites not loading or taking longer to respond. The issue appeared to be global, with reports from Bengaluru (India), South Fulton (Georgia, USA), and Portimão (Portugal), indicating broad reach. The incident lasted about 35 minutes and resolved by . The Claude status page posted three updates during the event to communicate investigation, a fix, and recovery.
Users attempting to use Claude's Code Execution Tool encountered API request errors, preventing execution workflows via that feature. The issue appeared limited to the Code Execution Tool API and did not indicate wider Claude service problems.
The outage began at when the status page moved to a warning state and lasted until when it returned to nominal. The provider posted two status updates during the incident, acknowledging the issue and outlining ongoing remediation, before restoring full functionality.
The incident was brief, lasting about 30 minutes, with no other Claude services affected and no user reports recorded during the period.
The Claude outage affected Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code, causing elevated errors and user-reported failures. The incident began at and lasted until , a duration of about 1 hour and 21 minutes. User reports clustered between 07:30 and 07:45 UTC, indicating broad impact across regions as services failed to respond or returned errors.
The Claude API (api.anthropc.com) and related services including claude.ai, platform.claude.com, and Claude Code experienced degraded performance beginning at . Users reported API connectivity failures, login problems, and usage-limit prompts across multiple regions. The incident lasted approximately 6 hours and 5 minutes and was resolved by as services returned to normal. Four components were affected during the event.
The Claude outage began at with users reporting the service not responding or loading, and it affected users across multiple regions. The issue persisted for nearly three hours, with reports describing prompts failing to process, endless loading loops, and maintenance messages. StatusGator tracked an Early Warning Signal through , indicating continued disruption before the situation abated. A large volume of user reports throughout the event reflected widespread impact on chat and prompt generation.
Claude did not publish any official status updates during the incident, and there were no acknowledged changes on the Claude status page. The incident appears to have been global in scope, with users in diverse locations experiencing similar symptoms and degraded productivity while attempting to use Claude for prompts and code assistance during the outage.
Claude reported elevated errors tied to Opus 4.6, impacting multiple components: Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. The incident began at and Claude's status page indicated an investigation into the issue.
The issue was resolved by , with all components returning to normal after roughly 1 hour and 5 minutes of disruption. The incident involved two official status updates during its duration.
From to , Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code experienced elevated errors, causing slower responses and failures for writing tasks for users globally. The outage lasted approximately 2 hours and 25 minutes.
Three official status updates were issued during the incident at , , and , describing an active investigation and later restoration as Claude Sonnet 4.5 and Claude Haiku 4.5 were affected, with affected services returning to normal by the end of the incident.
Looking for more Claude outage stats?
Get real-time insights and historical data on Claude outages.
