Claude Outage History

Users worldwide experienced elevated errors and slow responses from Claude.ai, notably impacting the Claude Sonnet 4.6 model. The issue began at 2:49 PM UTC and affected multiple regions, with users in Ashburn, Singapore, Tokyo, and London reporting unavailable or delayed Claude.ai interactions. A fix was implemented and monitoring began around Mar 17, 2026 3:33 PM UTC, and the service returned to normal by 3:48 PM UTC, with ongoing monitoring through 4:07 PM UTC. StatusGator detected the issue at Mar 17, 2026 2:49 PM UTC, about 44 minutes before the official acknowledgment by Claude.

Claude Sonnet 4.6 experienced elevated errors that disrupted access to Claude.ai for free-tier users. Reports from around the world described login failures, degraded responsiveness, and trouble loading files or using Claude Code. The impact began around 2:08 PM UTC and lasted for about one hour and 40 minutes as affected users across North America, Europe, and Asia encountered inconsistent service before recovery began.

Users across regions experienced elevated errors and degraded performance across Claude Sonnet 4.6 and Claude Opus 4.6, with free Claude.ai users affected early in the incident. The issue began at Mar 17, 2026 8:08 AM UTC and a fix was identified by Mar 17, 2026 8:24 AM UTC, as investigators worked to pinpoint the cause. Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code were affected, producing slow responses, operations taking longer than usual, and maintenance-style messages or verification problems for some users.

Status updates over the morning showed progress: a fix was implemented and monitoring began around Mar 17, 2026 11:38 AM UTC, with Claude API, claude.ai, platform.claude.com, and Claude Code moving back toward normal operation. Some services began recovering to normal levels while others continued to experience degraded performance; by Mar 17, 2026 1:04 PM UTC the affected components had returned to up. The incident appeared global, evidenced by user reports from multiple regions across API and chat interfaces rather than a single regional outage.

An outage affecting Claude Sonnet 4.6 began at 1:58 PM UTC when Claude's status page first listed elevated errors. The disruption impacted multiple Claude services, including Claude.ai, the Claude API at api.anthropic.com, platform.claude.com, Claude for Government, and Claude Code. Users reported not receiving responses, long wait times, and maintenance messages, with conversations stalling or failing to generate results. The issue appeared to be global, with affected users across regions including Ashburn, Frankfurt, Singapore, and other locations.

Status updates showed ongoing remediation as engineers worked on a fix. The scope narrowed as some components began recovering, but others remained degraded for several hours. The incident was effectively resolved by 4:38 PM UTC, when claude.ai and related services returned to normal operation.

StatusGator detected the disruption at Mar 16, 2026 11:26 AM UTC, about 37 minutes before Claude's official acknowledgment. Claude.ai experienced elevated errors and a temporary service disruption, with users reporting that Claude could not be reached or chats would not load. The Claude status page shows the issue was acknowledged at 12:03 PM UTC and that a fix was implemented and monitoring began at 12:28 PM UTC, with service restored by 12:38 PM UTC.

A surge in user reports across multiple regions indicates widespread impact affecting Claude.ai users, with reports from Ashburn, London, Paris, Helsinki, Perth, and Sydney describing temporary disruptions. The status updates documented ongoing remediation and eventual restoration of service.

An outage began around Mar 13, 2026 6:38 PM UTC as Claude Opus 4.6 services showed elevated errors. The affected components included Claude API (api.anthropic.com), claude.ai, and Claude Code. Users reported prompts failing to generate results, timeouts, or non-responsive interfaces when interacting with Claude, and the web client sometimes displayed loading issues or incomplete responses. The disruption appeared broad, with reports spanning multiple regions and user experiences ranging from errors to stalled workflows.

Status updates indicated active investigation, and the issue persisted for several hours. By Mar 13, 2026 9:28 PM UTC the Claude API, claude.ai, and Claude Code components had returned to normal, marking the resolution of the incident. The outage noticeably disrupted workflows for users relying on Claude’s API and tooling during the window of impact.

Users experienced degraded performance across Claude Sonnet 4.6 tools as errors surfaced in the Claude API (api.anthropic.com), claude.ai, and Claude Code. The incident began at 4:27 PM UTC with elevated errors, and the Claude status page flagged a degraded state for these components at 4:38 PM UTC. Users reported chats failing to respond or taking longer than usual across many regions, indicating a global impact. The issues were resolved and services returned to normal by 7:48 PM UTC after the status changed to up.

Users of Claude Sonnet 4.6, Claude API, Claude Code, and Claude.ai saw elevated error rates during a brief incident on Claude Sonnet 4.6 from 3:30 PM UTC to 3:44 PM UTC. A separate Claude.ai-related hiccup occurred around 3:27 PM UTC and lasted about a minute, contributing to intermittent failures when calling Claude APIs, Code, or Claude.ai.

Status updates show the issue was categorized as a degraded service and then resolved. The affected components returned to normal by 4:28 PM UTC after being marked degraded at 4:09 PM UTC. User reports indicated a notable spike in activity around the incident window, with recovery occurring through the late afternoon.

Users across Claude services reported slow responses and timeouts, with some requests failing to load entirely. Early activity began around 3:05 PM UTC as browsers failed to load and a surge in reports followed around 3:30 PM UTC through 3:45 PM UTC. The issue appeared to impact multiple Claude components, including Claude API (api.anthropic.com), claude.ai, platform.claude.com, Claude for Government, and Claude Code.

Users worldwide faced login issues with Claude.ai and Claude Code beginning around 1:56 PM UTC. Many reports described login timeouts, authorization failures, and disrupted Claude Code sessions, affecting the ability to sign in, start tasks, or access chats. The Claude API itself was not affected, but the user experience was significantly degraded across Claude.ai and Claude Code components.