Claude Outage History

Users worldwide experienced outages in Claude chat and desktop services beginning around 6:29 PM UTC with reports of chats not loading and slower responses. StatusGator detected the issue at Apr 25, 2026 6:29 PM UTC, about 14 minutes before Claude acknowledged the problem at Apr 25, 2026 6:43 PM UTC. Claude’s status page indicated an ongoing investigation and a degraded service as engineers triaged elevated errors, with impacts reported across multiple regions. The disruption was global, affecting users from North America, Europe, and Asia-Pacific, including both chat and desktop interfaces.

By around 7:03 PM UTC, Claude reported resolution and the service returned to normal, with the status moving back to up. The outage lasted roughly 35 minutes from the initial signal to restoration. Claude documented the investigation and corrective steps on its status page, noting elevated errors and slower responses during the incident. While access to chats and related features improved, some users may have continued to experience intermittent delays or incomplete chat history immediately after recovery.

Users worldwide faced outages across Claude's core services, including the Claude API (api.anthropic.com), platform.claude.com, Claude Code, and Claude Cowork. Sign-in failures, timeouts, and elevated errors disrupted workflows for many users. Status activity began around 12:47 PM UTC. StatusGator detected an Early Warning Signal at Mar 25, 2026 12:47 PM UTC, about 1 hour before Claude acknowledged the problem at Mar 25, 2026 1:48 PM UTC. The incident drew a large volume of user reports across regions, indicating global disruption. By 1:40 PM UTC the error rate had returned to baseline and monitoring continued to ensure stability.

Users around the world experienced elevated errors and degraded performance across Claude Opus 4.6. Access to Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code was affected, with reports of connection failures, busy server messages, and slow task execution. The impact began around 8:45 AM UTC and became more noticeable through the morning as users in multiple regions reported issues.

Claude's official status page recorded the first acknowledgement at Mar 25, 2026 9:39 AM UTC when the incident moved to a degraded state. A fix was implemented and monitoring continued by 10:08 AM UTC. By Mar 25, 2026 1:14 PM UTC the affected components were returned to an up state. User reports spanned the United States, India, The Netherlands, Japan, Canada, Germany, Indonesia, and other locations, indicating a broad, global impact on development workflows and AI-assisted tasks.

Users worldwide faced login and chat outages on Claude.ai as reports surged in the mid-afternoon UTC. Claude indicated elevated errors on Claude.ai between 4:10 PM UTC and 4:26 PM UTC, while the Claude API remained available. StatusGator detected the issue at Mar 23, 2026 4:14 PM UTC, roughly 49 minutes before Claude acknowledged the outage on its status page at 5:03 PM UTC. The disruption began to ease by around 4:50 PM UTC and full restoration followed by 5:14 PM UTC.

Across regions, users reported being unable to log in via app, link, or website; Claude.chat and other Claude web interfaces were not responding, with common error messages like "This isn't working right now" appearing in multiple locales. The issue appeared globally, with reports from North America, Europe, Asia, and beyond, while the Claude API remained accessible for automated usage.

Users worldwide could not sign in to Claude Console (platform.claude.com) or Claude.ai, with login loops and sign-in failures reported across multiple regions. StatusGator detected problems at Mar 22, 2026 6:16 PM UTC, roughly 17 minutes before Claude acknowledged the outage. The official status update showed Claude Console login down starting at Mar 22, 2026 6:34 PM UTC.

A mitigation was applied by Mar 22, 2026 6:48 PM UTC, and sign-ins began returning to normal; full recovery followed by Mar 22, 2026 6:54 PM UTC.

Users experienced delayed Claude.ai responses, with replies hanging for about 5 seconds after streaming before the message completes. The issue affected the Claude.ai component, while the Anthropic API was not affected. Impact began around 8:00 PM UTC.

Official updates documented the progression: at 11:19 AM UTC the Claude.ai component changed to a degraded state (warn) with the note 'Delayed response completion'; a follow-up at 12:39 PM UTC said a fix was being implemented; the service was restored by 1:13 PM UTC.

Overall, users experienced about 41 hours of degraded Claude.ai performance before restoration was completed by 1:13 PM UTC.

Impact began at 12:09 AM UTC when Claude Opus 4.6 started showing elevated error rates. The issue affected multiple Claude components, including Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code, leading to failed requests and degraded performance for users relying on Claude Opus 4.6. The StatusGator updates showed ongoing investigation and efforts to identify the root cause, with the issue persisting into the early hours across Opus and Sonnet 4.6 and causing degraded experiences for users.

The Claude service briefly experienced an outage impacting API access (api.anthropic.com), Claude AI, and Claude Code. Users attempting to run tasks against Claude API or interact with Claude AI or Claude Code encountered errors and timeouts as elevated issues were reported across all three components. The incident began at 4:04 PM UTC with initial error reports and an investigation, and the services were restored by 4:18 PM UTC.

Users around the world experienced degraded Claude chat performance as responses slowed and timeouts occurred. The disruption affected Claude API (api.anthropic.com), claude.ai, and Claude Code, with impact beginning around 3:23 PM UTC. Observations from users described messages like 'Taking longer than usual' and noticeable delays during conversations and code tasks.

StatusGator recorded an Early Warning Signal at Mar 19, 2026 2:43 PM UTC, noting slow or timing out chat responses, preceding Claude's official acknowledgement. The status page then indicated elevated errors around 3:38 PM UTC and the services returned to normal by 3:48 PM UTC. The early-warning window closed by 4:03 PM UTC. The incident suggests a brief degradation lasting roughly the span from the onset to rapid recovery, with a notable burst of user reports in the afternoon before stabilization.

StatusGator detected issues starting around Mar 19, 2026 12:00 AM UTC with a surge of user reports by 12:15 AM UTC, signaling a widespread impact on Claude surfaces. The Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code experienced authentication and chat failures, leaving users unable to sign in, access conversations, or send messages. Official updates show an escalation from a surface-wide warning to a full outage: the incident moved to a degraded/partial outage at Mar 19, 2026 12:28 AM UTC and then to a complete outage at Mar 19, 2026 12:33 AM UTC as engineers investigated. The disruption persisted for more than an hour, with recovery gradually progressing and services returning to normal by 1:43 AM UTC. StatusGator’s early signal highlighted the issue approximately 12:00 AM UTC with a lead time of about 33 minutes before the official acknowledgment.