Claude Outage History

The Claude suite experienced degraded performance beginning around 10:05 AM UTC due to Opus 4.6 Fast Mode generating a small amount of errors. This affected Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code, causing errors and slower responses for users. The Claude status page documented the incident escalating to degraded at Feb 10, 2026 11:28 AM UTC and returning to normal by Feb 10, 2026 4:29 PM UTC. The incident lasted from 10:05 AM UTC to 4:29 PM UTC and included 2 official status updates. User reports spanned multiple locations, indicating a broad impact across Claude services.

Claude experienced a brief degraded service affecting its API and platform components, including Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. The issue began at Feb 7, 2026 4:03 PM UTC with elevated errors on Claude models and an ongoing investigation. The outage lasted about 30 minutes and was resolved by Feb 7, 2026 4:33 PM UTC as all components returned to normal. The Claude status page issued two updates during the incident. There was no clear regional pattern observed.

Claude's web chat interface and related services faced a worldwide outage, with users across multiple regions reporting that prompts did not load, responses timed out, or the chat UI became unresponsive. The incident began at Feb 6, 2026 8:04 PM UTC and was resolved by Feb 6, 2026 8:30 PM UTC. The outage affected multiple components including the web chat, the chat API, and workspace connectivity, leading to diminished ability to generate and deliver responses.

Claude did not publish public status updates during the event. StatusGator logged an Early Warning Signal beginning at Feb 6, 2026 8:04 PM UTC, based on user reports, ahead of any official acknowledgement. The reports continued through the end of the window, indicating a broad impact rather than a localized incident.

Impact appeared global, with reports from North America, Europe, and other regions describing non-responsiveness, timeouts, and stalls in the chatbot. The outage affected several components including web chat, API responses, and workspace connectivity, reducing users' ability to interact with Claude during the window.

Claude.ai experienced a degraded condition beginning at Feb 5, 2026 3:58 PM UTC due to a conversation compaction degradation. Users reported symptoms including difficulty reaching the API, timeouts, retries, and errors such as 'exceed max compactions per block,' impacting chat workflows for several users during the incident. The issue affected the claude.ai component and was observed through user reports across different regions.

The Claude.ai status page indicated the issue was identified and a fix was being implemented at the start. The service returned to normal by Feb 5, 2026 8:33 PM UTC after about 4 hours and 35 minutes. The provider issued 2 status updates during the incident, reflecting the progression from degradation to full recovery.

Claude experienced elevated errors across Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code, causing intermittent API failures and internal server errors for users. The incident began at Feb 4, 2026 4:42 PM UTC when Claude's status page changed from up to warn with the message 'Elevated errors on Claude models' and an investigation was started. Users across several regions reported 500 errors and internal server errors when invoking models or tooling. The issue affected multiple components and persisted for about 26 minutes before service returned to normal.

The Claude status page issued two updates during the incident, including the initial investigation and the subsequent resolution notice. The problem was resolved by Feb 4, 2026 5:08 PM UTC and all components returned to an operational state. The impact appeared global rather than regionally isolated, with reports coming from various locations around the world.

The Claude Opus 4.5 and Sonnet 4.5 platforms experienced elevated errors starting at 10:18 AM UTC, affecting four Claude components: Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. Users reported prompts failing to respond, slow performance, and timeouts across these products.

The incident lasted about 55 minutes, with services returning to normal by 11:13 AM UTC. The Claude status page documented degraded behavior and issued two official updates during the incident to communicate scope and resolution.

Reports came from many regions, indicating broad geographic impact. Activity peaked between 10:15 AM UTC and 10:45 AM UTC as users across different time zones described prompts not responding, slowdowns, and intermittent timeouts.

Claude Opus 4.5 experienced a multi-component outage beginning at Feb 3, 2026 9:08 PM UTC, affecting Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. Users reported being unable to complete tasks, non-functional features, and delayed responses across these services. The outage lasted about two hours and was observed across multiple regions. The incident was resolved by Feb 3, 2026 11:08 PM UTC. User reports started around 9:15 PM UTC.

Claude.ai connectors experienced degraded performance due to an elevated error rate when establishing new connections. The issue affected users relying on Claude.ai connectors, causing connection failures and slower workflows. The incident began at Feb 3, 2026 6:43 PM UTC and lasted about 2 hours and 5 minutes, ending at Feb 3, 2026 8:48 PM UTC when the service returned to normal. The Claude.ai component issued 2 status updates during the incident, describing an ongoing investigation and eventual restoration. User reports indicated connection issues in some locations, reflecting a limited but noticeable impact before resolution.

The Claude API and related services across API, UI, and coding interfaces experienced a brief outage lasting about 21 minutes. Users attempting to use Claude capabilities encountered errors or degraded responses across api.anthropic.com, claude.ai, platform.claude.com, and Claude Code. The outage began on 3:48 PM UTC and was resolved by 4:09 PM UTC, with a global pattern of reports indicating widespread disruption.

Claude’s status page showed early actions: an update at 3:46 PM UTC stating the issue had been identified and a fix was being implemented, followed by recovery updates as services came back online. In total, four components were affected, and the incident was resolved after about 21 minutes.

Claude experienced an API outage affecting all models, including Claude API, claude.ai, platform.claude.com, and Claude Code. Users reported internal server errors and HTTP 500 responses, hindering access to Claude services. The outage began at 3:48 PM UTC and was resolved by 4:09 PM UTC, lasting about 21 minutes. StatusGator detected the issue earlier, with reports starting at Feb 3, 2026 3:37 PM UTC, roughly 11 minutes before Claude acknowledged the incident. Early Warning Signal observed: StatusGator detected issues at Feb 3, 2026 3:37 PM UTC.