Claude Outage History

On Feb 28, 2026 6:13 PM UTC, Claude Opus 4.6 reported elevated errors affecting Claude API at api.anthropic.com, claude.ai, and Claude Code. Users interacting with Claude features may have experienced errors or degraded functionality during this period.

The issue prompted an investigation, and the affected components returned to normal by 6:38 PM UTC, approximately twenty-five minutes after the event began. The incident appeared localized to Claude Opus 4.6 components rather than indicating a broader service outage.

Users experienced degraded access to Claude.ai beginning around Feb 28, 2026 12:58 PM UTC as elevated errors affected claude.ai and some users could not load the Web/API endpoints or the settings page. Status updates showed a partial outage across the Claude.ai component, with reports of connection timeouts and upstream errors from multiple regions. StatusGator issued an Early Warning Signal at Feb 28, 2026 12:52 PM UTC tied to settings page connection problems (ending Feb 28, 2026 1:03 PM UTC), providing about six minutes of lead time before the first official acknowledgment at Feb 28, 2026 12:58 PM UTC.

Claude users across multiple services encountered an elevated error rate that caused failed requests and degraded performance for a short period. The Claude status page showed the issue beginning at 7:33 PM UTC when the affected components Claude for Government, Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code were flagged as experiencing elevated errors and the page indicated an ongoing investigation. The issue was resolved about ten minutes later, with status returning to normal by 7:43 PM UTC. User reports from multiple regions supported the window of impact, including messages around 7:34 PM UTC from Inhambupe, Bahia, Brazil and 7:42 PM UTC from Surat, Gujarat, India.

The Claude platform experienced a coordinated outage affecting usage reporting across Claude API (api.anthropic.com), Console (platform.claude.com), Claude AI (claude.ai), and Claude Code. Users encountered missing usage data and degraded interactions across dashboards and APIs. The incident began on 3:58 PM UTC and persisted until 5:18 PM UTC, spanning roughly 25 hours and 20 minutes. The provider issued 16 status updates during the incident as engineers investigated and rolled out fixes across the affected components.

A sequence of fixes gradually restored functionality, including a targeted fix for the /v1/organizations/usage_report/messages admin API endpoint and subsequent hotfixes for Claude Code on Windows. Elevated errors on claude.ai were addressed, and by 5:18 PM UTC all services returned to normal operation.

Claude experienced a prolonged outage affecting multiple components including claude.ai, platform.claude.com, Claude Code, Claude API (api.anthropic.com), Claude for Government, and the Claude Desktop app. Users faced widespread unavailability, crashes, and API errors across chat, coding, and government workflows. The outage began on 1:58 PM UTC and was resolved by 11:58 PM UTC.

The Claude service experienced a widespread outage affecting Claude API (api.anthropic.com), the Claude Platform, Claude Code, Claude for Government, and Claude Desktop. The incident began during a maintenance window with chat unavailable, and StatusGator detected the issue at Feb 25, 2026 12:57 PM UTC, about 1 hour before Claude officially acknowledged the problem at Feb 25, 2026 1:58 PM UTC. Users reported failures across web and desktop interfaces, with API endpoints returning errors and the Windows desktop experience disrupted.

The Claude service experienced an outage starting at 12:23 PM UTC 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 1:28 PM UTC. The outage lasted about 1 hour and 5 minutes.

From Feb 17, 2026 1:13 PM UTC, 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 1:13 PM UTC to 11:45 AM UTC. 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 Feb 16, 2026 4:08 PM UTC, causing degraded performance across Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. Users reported issues starting as early as 3:15 PM UTC, with messages describing unavailability and connection errors. The incident persisted for about 3 hours and 10 minutes, ending at Feb 16, 2026 7:18 PM UTC.

The provider issued four status updates during the incident: first at Feb 16, 2026 4:08 PM UTC noting an investigation, then at Feb 16, 2026 4:38 PM UTC that a fix was being implemented, followed by Feb 16, 2026 4:58 PM UTC reporting that a fix had been deployed and results were being monitored, and finally Feb 16, 2026 7:18 PM UTC confirming restoration of services.

Claude Opus 4.6 experienced elevated errors beginning at 2:33 PM UTC, 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 3:08 PM UTC. The Claude status page posted three updates during the event to communicate investigation, a fix, and recovery.