Claude Outage History

Users worldwide faced an outage across Claude's core services beginning around 12:39 AM UTC, with elevated error rates across Claude Cowork, Claude API (api.anthropic.com), claude.ai, and Claude Code. An Early Warning Signal from StatusGator appeared at 12:28 AM UTC, indicating Claude Code and Chat were not responding, about 11 minutes before the provider acknowledged the issue. The incident sparked a surge in user reports across multiple regions, with many customers unable to send messages, experiencing long loading times, or seeing capacity-related errors.

An outage affected Claude's Opus 4.8 stack, taking down the Claude API (api.anthropic.com), Claude Console (platform.claude.com), Claude Cowork, Claude AI (claude.ai), and Claude Code. Users reported API errors, timeouts, and incomplete responses across multiple regions, with activity peaking in the 17:00 to 17:30Z window. The disruption began at 5:13 PM UTC and persisted for about 50 minutes before recovery.

Claude services tied to Opus 4.8 encountered a significant outage that affected API responses and user-facing tools. Beginning around 5:13 PM UTC, users reported API errors, incomplete responses, and timeouts across Claude API (api.anthropic.com), Claude Console (platform.claude.com), Claude Cowork, Claude Code, and claude.ai. The disruption appeared globally, with reports spanning multiple regions and impacting developers and end users relying on Claude-powered prompts, generation, and integrations.

Users experienced elevated error rates affecting the Claude API, with related components showing degraded performance. The impact touched Claude Console (platform.claude.com), Claude Cowork, Claude API (api.anthropic.com), claude.ai, and Claude Code, causing API errors and disrupted workflows for a brief period.

The incident began at 8:18 AM UTC when Claude indicated elevated errors and launched an investigation. The issue was resolved by 8:38 AM UTC, with all affected components returning to normal. The disruption lasted roughly twenty minutes.

An outage hit Claude Opus 4.8, causing elevated errors across Claude Console, Claude Cowork, Claude API, claude.ai, and Claude Code. Users attempting to interact with Claude services encountered failures loading the Console, making API requests, or using Claude-enabled apps, with the disruption lasting about 55 minutes. The incident began at 6:08 AM UTC and was resolved by 7:03 AM UTC. Early user reports appeared in the first minutes, signaling impact across multiple interfaces.

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.