Claude Outage History

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.

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 4:13 PM UTC when the status page moved to a warning state and lasted until 4:43 PM UTC 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 Feb 14, 2026 7:28 AM UTC and lasted until Feb 14, 2026 8:49 AM UTC, 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 Feb 13, 2026 5:18 PM UTC. 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 Feb 13, 2026 11:23 PM UTC as services returned to normal. Four components were affected during the event.

The Claude outage began at 4:46 PM UTC 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 7:33 PM UTC, 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 2:19 PM UTC and Claude's status page indicated an investigation into the issue.

The issue was resolved by 3:24 PM UTC, 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 1:23 PM UTC to 3:48 PM UTC, 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 Feb 11, 2026 1:23 PM UTC, Feb 11, 2026 2:58 PM UTC, and Feb 11, 2026 3:48 PM UTC, 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.

Claude experienced a brief degraded performance across its services due to elevated errors on Opus 4.6. The affected components were Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. The incident began at 8:24 AM UTC and was resolved by 8:39 AM UTC, lasting about 15 minutes. Claude's status page indicated elevated errors and an ongoing investigation, followed by restoration of service as the components returned to normal. The provider posted 2 status updates during the incident.

Claude's Opus 4.6 Fast Mode experienced elevated errors starting around 9:15 PM UTC, with users reporting authentication failures (e.g., Can’t OAuth) and messaging failures across regions. This caused degraded messaging capabilities for affected users.

The incident was acknowledged by Claude at Feb 10, 2026 10:13 PM UTC with a note that an investigation was underway. Claude issued 2 official status updates during the outage and confirmed recovery by Feb 11, 2026 5:43 AM UTC, after roughly 8 hours and 28 minutes. Reports originated from diverse regions, indicating broad impact rather than a single-region issue.

Claude's LLM and API endpoints experienced a global outage starting at Feb 10, 2026 7:33 PM UTC, with users reporting internal server errors and non-responsiveness across multiple regions. The impact included API errors (often 500), prompts failing to return results, and noticeable processing delays. User reports surged during the evening, peaking around 9:15 PM UTC to 9:30 PM UTC UTC as the issue affected a broad set of users.

There were no official status updates from Claude during the incident. StatusGator detected the outage at Feb 10, 2026 7:33 PM UTC based on user reports, with the early warning signal continuing until Feb 10, 2026 9:43 PM UTC. The outage lasted roughly 2 hours and 10 minutes and appeared to be global, impacting users across North America, Europe, and other regions.