Claude Outage History

Claude's chat service experienced a widespread outage, leaving users around the world unable to get responses or encountering errors when chatting. StatusGator detected the issue at Mar 10, 2026 5:04 PM UTC, ahead of any official acknowledgement, as reports began to surge around 5:30 PM UTC and continued through 6:15 PM UTC. Users described slow replies, timeouts, and prompts that would not load, with some noting maintenance notices as the incident progressed.

No official Claude status updates were posted during the event. The issue appeared to have global reach, with reports spanning North America, Europe, and Asia, indicating a broad impact on typical chat tasks. The outage was observed to end by 6:53 PM UTC as activity subsided and users resumed normal usage.

The Claude Desktop app became unresponsive, preventing startup and normal use for users around the world. The incident began at Mar 8, 2026 5:58 PM UTC and persisted for more than a day as engineers investigated. Users reported issues ranging from login problems to stalled workflows, with many describing difficulty in completing tasks in Claude Cowork or Claude Code.

Root cause: a daylight saving time transition created an infinite loop when the app tried to locate tasks scheduled during the skipped hour in certain time zones. The team released a fix as an update (version 1.1.5749) and provided a workaround to switch to a non-DST timezone if updating immediately. By gradually deploying the fix, Claude aimed to restore normal functionality for affected users and prevent recurrence across regions.

The service was restored by Mar 10, 2026 4:53 PM UTC, and status updates indicated the desktop client returning to normal operation. A large volume of user reports across multiple regions reflected the broad impact, underscoring how widespread the outage was for desktop users.

Users of Claude Desktop and the Claude API experienced widespread issues starting 5:18 PM UTC, with desktop apps hanging, blank screens, and slow or failed responses across Claude API (api.anthropic.com), claude.ai, and Claude Code. A notable volume of user reports across regions indicated a broad impact on core workflows that rely on Claude.

Official status updates identified the cause as a missing Filesystem connector on Claude Desktop, with a fix implemented and guidance to re-add the connector to organization allowlists to reactivate it. On 1:58 PM UTC, Claude Haiku 4.5 also showed elevated errors, and a follow-up at 4:58 PM UTC noted the Filesystem connector issue persisted but that a fix had been applied. The issue was gradually resolved, and the system returned to normal by 3:53 PM UTC.

The Claude API (api.anthropic.com) experienced a partial outage as some API requests timed out due to elevated TCP three-way handshake failures caused by network degradation at an upstream peering point. Requests that could connect were unaffected, but overall the experience degraded for developers relying on Claude's API. The incident began at Mar 6, 2026 3:38 PM UTC and was categorized as a degraded service during the event. A fix was implemented at Mar 6, 2026 4:04 PM UTC and monitoring continued; connectivity returned to normal by Mar 6, 2026 4:23 PM UTC, with the outage lasting roughly 45 minutes.

The Claude platform experienced elevated errors starting around 2:18 PM UTC, affecting Opus 4.6 and Haiku 4.5 workloads. Users reported authentication failures, non-loading models, and various errors when trying to use Claude features. The issues hit core components Claude API (api.anthropic.com), claude.ai, and Claude Code, resulting in degraded performance and intermittent access for those trying to interact with Opus 4.6 and Haiku 4.5.

Recovery unfolded in stages: a brief stabilization appeared around 2:58 PM UTC as Claude API components moved back toward up, but Haiku 4.5 problems re-emerged around 3:58 PM UTC. A fix was implemented by 4:18 PM UTC and monitoring continued. By 5:03 PM UTC all Claude components were reported up again, marking the end of the incident after roughly 2:18 PM UTC to 5:03 PM UTC (about 2 hours and 45 minutes) of degraded service. The footprint appeared global, with reports from multiple regions.

An outage disrupted Claude's Admin API and the Console, with usage reporting and cost reporting affected. Users attempting to manage accounts, access reporting screens, or run queries against the Sonnet 4.6 model reported errors and slow responses. StatusGator logged an Early Warning Signal starting at Mar 3, 2026 3:44 PM UTC, roughly 1 hour and 9 minutes before the first official acknowledgement at 4:53 PM UTC.

Engineering teams pushed fixes over the next hours. The admin API was operational again by 12:58 AM UTC and the Console (platform.claude.com) followed by 1:34 AM UTC. A separate update addressed usage reporting, and by 8:33 AM UTC the service had fully recovered. The outage affected Claude API (api.anthropic.com) and platform.claude.com, with cost reporting also impacted during the incident.

The Claude service experienced an outage starting around 2:53 PM UTC with elevated errors on Claude Haiku 4.5. By 3:43 PM UTC the issue expanded to Claude Sonnet 4.6 and related components, including Claude API (api.anthropic.com), claude.ai, and Claude Code, with users seeing failures and degraded performance. The incident affected users globally, who reported a range of symptoms from timeouts, failed uploads, and unresponsiveness across regions such as the United States, United Kingdom, India, United Arab Emirates, and the Philippines. The status updates described elevated errors and degraded service during this period, and recovery began by 4:43 PM UTC as components returned to normal.

User reports surged in the late afternoon UTC, with activity peaking around 4:00 PM UTC to 4:15 PM UTC, spanning regions from Dubai to the United States, United Kingdom, India, and the Philippines. Many users described errors such as inability to run scripts, network timeouts, and unresponsive AI responses, indicating widespread impact before stabilization.

Users across multiple regions encountered degraded Claude services as elevated errors affected Claude Opus 4.6 components, including claude.ai, platform.claude.com, Claude Code, and the Claude API (api.anthropic.com). The impact manifested as tools not loading, chats failing to load or generate content, and authentication or task-generation issues. Beginning around 3:18 AM UTC, reports flowed in and spread through the morning, indicating a broad, global disruption.

Status updates from Claude showed an ongoing investigation with fixes being implemented and monitored. A series of remediation steps began to restore functionality, and by 2:33 PM UTC most affected components were returning to normal operation (claude.ai, platform.claude.com, Claude Code, and Claude API). The incident represented a partial outage across Claude Opus 4.6 services rather than a full service shutdown.

Users experienced degraded Claude performance across the Opus 4.6 stack, including the Claude API, claude.ai, platform.claude.com, and Claude Code. The outage led to incomplete or failing response generation, with reports of chats not loading, uploads failing, and older chats disappearing in some cases. The impact appeared globally across multiple user locations and activities, illustrating the breadth of the disruption.

An outage began around 11:37 AM UTC with Claude reporting service unavailability due to server errors. Users worldwide could not access Claude.ai, and login/logout flows along with the chat experience were affected. The disruption extended to Claude Console and Claude Code, while the Claude API was noted as functioning for some operations, indicating the issue was concentrated on user-facing paths rather than the API itself. Status updates emphasized elevated errors across multiple Claude components.