Claude Outage History

Claude experienced an outage with elevated errors across multiple components, impacting users trying to access Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. Users reported internal server errors and HTTP 500 responses during the event. The incident began around Feb 4, 2026 4:39 PM UTC and the status page moved to a degraded state at Feb 4, 2026 4:42 PM UTC as teams investigated. The outage lasted about 29 minutes and was resolved by Feb 4, 2026 5:08 PM UTC. It affected users across multiple regions globally. The Claude status page issued two updates during the incident, noting elevated errors and subsequent recovery.

Users attempting to establish new Claude.ai connections experienced elevated error rates, potentially impacting Claude.ai integrations. The first user reports appeared at 5:45 PM UTC, suggesting issues began before Claude acknowledged the incident. The Claude status page indicates an investigation started around Feb 3, 2026 6:42 PM UTC and the incident was upgraded to warn at Feb 3, 2026 6:43 PM UTC.\n\nThe incident affected the claude.ai component, with one official status update published. There was no Early Warning Signal detected. The outage duration spans from around 5:45 PM UTC to Feb 3, 2026 6:43 PM UTC (roughly 58 minutes) and the issue remained under investigation at the last update.

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.

The Claude service experienced a global outage affecting mobile and web access, with users reporting that the Claude app and related AI interfaces were unresponsive across multiple regions. Early reports described the iOS Apple app not working and prompts failing to return results, with maintenance messages appearing for some users. StatusGator detected activity starting at Jan 25, 2026 12:36 PM UTC based on user reports, and symptoms persisted through the afternoon, with signals around 6:42 PM UTC. There were no official status updates posted by Claude during the incident. The outage lasted roughly six hours, indicating a major disruption for users relying on Claude for chat and AI tasks. The impact appeared global rather than regionally isolated.

Claude API (api.anthropic.com) experienced elevated errors caused by an invalid signature in the thinking block, leading to intermittent API failures for callers. The issue began at Jan 23, 2026 5:13 AM UTC and was resolved by Jan 23, 2026 7:48 AM UTC, lasting about 2 hours and 35 minutes. The Claude status page issued two updates during the incident, noting ongoing remediation efforts and eventual restoration of normal service.

Claude.ai experienced a global outage that disrupted chat and degraded responses on claude.ai and Claude Code. Users reported that messages were not being accepted and conversations were unreliable, with a large volume of user reports (147 total) indicating widespread impact. StatusGator detected the issue at Jan 22, 2026 3:31 PM UTC, about 37 minutes before the first official acknowledgment at Jan 22, 2026 4:08 PM UTC. The outage affected two components, claude.ai and Claude Code, and lasted until Jan 22, 2026 4:53 PM UTC, for a duration of roughly 1 hour 22 minutes.

The Claude status page issued 3 updates during the incident (at Jan 22, 2026 4:08 PM UTC, Jan 22, 2026 4:13 PM UTC, and Jan 22, 2026 4:53 PM UTC UTC). This indicates the incident was actively managed, and services were restored to normal operation after the final update at Jan 22, 2026 4:53 PM UTC.

Claude experienced elevated errors on Claude Sonnet 4.5, causing a brief degradation across four Claude services: Claude API, claude.ai, platform.claude.com, and Claude Code. Users reported chat interruptions and slower responses. The outage began at Jan 21, 2026 2:48 PM UTC and was resolved by Jan 21, 2026 3:38 PM UTC, lasting about 50 minutes. The Claude status page posted two updates during the incident, noting ongoing investigation and eventual restoration of services.

The Claude service experienced elevated errors across multiple components, including Claude API, claude.ai, platform.claude.com, and Claude Code, resulting in degraded performance for users. Users reported timeouts, non-responses, and prompts not returning results during the incident. The outage began at 4:38 PM UTC and StatusGator detected the issue at Jan 20, 2026 4:38 PM UTC, about 5 minutes before Claude acknowledged the problem on their status page. The issue affected 4 components and led to degraded functionality for roughly an hour.

The Claude status page showed the first update at 4:43 PM UTC with an Investigating message, and the service was restored by 5:38 PM UTC. The Early Warning Signal ended at 5:13 PM UTC. The provider issued 2 status updates during the incident.

The Claude.ai component experienced compaction issues that degraded the chat experience. Users reported difficulties starting or continuing conversations, and some conversations did not compact as expected. The degraded state began at Jan 15, 2026 7:28 AM UTC and was resolved by Jan 15, 2026 5:03 PM UTC, lasting approximately 9 hours and 35 minutes.

StatusGator detected issues at Jan 14, 2026 9:33 AM UTC, 45 minutes before Claude acknowledged the problem. The outage affected Claude API (api.anthropic.com), claude.ai, and Claude Code, causing errors and degraded access for users. The incident began with elevated error rates and widespread impact across Claude services, with users reporting global connectivity and responsiveness issues.