Claude Outage History

An outage affected Claude.ai and Claude Code, causing elevated errors and failed prompts across users worldwide. API calls returned errors and login/logout actions were impacted, making Claude Code less usable and causing prompts to not respond in many regions. StatusGator detected the issue at Mar 18, 2026 3:14 PM UTC and the Early Warning Signal ran until Mar 18, 2026 5:09 PM UTC, with the provider first acknowledging the disruption at 3:18 PM UTC. A fix was deployed by 3:28 PM UTC and recovery began, with Claude.ai and Claude Code returning to normal by 4:08 PM UTC. This disruption drew a surge of user reports around mid-afternoon, underscoring the widespread impact.

Users worldwide faced outages as Claude Opus 4.6 overloaded the platform, triggering widespread errors and timeouts across Claude API (api.anthropic.com), claude.ai, platform.claude.com, Claude for Government, and Claude Code. The incident began around 12:30 PM UTC and persisted into the afternoon, with a high volume of user reports from multiple regions indicating global disruption. StatusGator recorded an Early Warning Signal for overload starting at Mar 18, 2026 11:32 AM UTC and ending at Mar 18, 2026 1:49 PM UTC, including lead time of about Mar 18, 2026 12:33 PM UTC before the official acknowledgment.

An outage affecting Claude Opus 4.6 began around 6:43 AM UTC with elevated errors across Claude API (api.anthropic.com), claude.ai, platform.claude.com and Claude Code. Users across multiple regions reported slow responses, failed requests, and UI loading issues, indicating a broad impact on both programmatic access and the user interface. The disruption affected a global user base, with reports of degraded performance appearing for several hours.

The Claude Opus 4.6 outage began with widespread errors across Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. StatusGator users saw elevated failures in the Claude app and API starting around 7:37 PM UTC, with official acknowledgment around 7:48 PM UTC. The incident quickly escalated into a broader outage as users reported API errors, timeouts, and degraded performance. StatusGator’s Early Warning Signal indicated the issue ahead of the provider’s notice, showing a lead time of about 11 minutes between detection and official acknowledgment; the signal remained active from Mar 17, 2026 7:37 PM UTC until Mar 17, 2026 9:54 PM UTC. A large volume of user reports in the first hours underscored the global impact across multiple regions.

Mitigations were deployed and monitoring began around 10:43 PM UTC as engineers worked to restore services. A fix was implemented and results monitored, with all core components returning to normal by 12:28 AM UTC across Claude API, claude.ai, platform.claude.com, and Claude Code, marking the end of the incident. The outage disrupted workflows for developers and users relying on Claude across multiple fronts, including API access, UI interactions, and code tooling, during the evening and into the late night.

Users worldwide faced unresponsive Claude prompts as the chat service experienced a widespread outage. Reports spanned multiple regions including Ashburn, Frankfurt, Paris, Kuala Lumpur, Berlin, and Santiago, with chats taking longer than usual or failing to return any output. The outage began at 5:09 PM UTC and was resolved by 6:31 PM UTC. StatusGator detected the issue at Mar 17, 2026 5:09 PM UTC, ahead of any provider acknowledgement.

Claude's official status page did not show updates during the incident, leaving users to gauge impact from reports themselves. The surge in reports across continents confirms a global impact on Claude chat, with the core chat service degraded for about 1 hour and 22 minutes before gradual recovery.

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.