There were 112 Claude outages since January 2026 which are summarized below, including incident details, duration, and resolution information.
Claude not working for you?
Claude not working for you?
Minor
: Claude Haiku 3.5 services briefly degraded across API and UI
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(35 minutes)
Claude Haiku 3.5 experienced elevated errors and degraded performance across multiple access points, including Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. Users reported slow page loads and upgrade-related issues during the incident.
Major
: Claude AI app outage affects users globally
Detected by StatusGator:
Officially acknowledged:
No
Outage ended:
(6 hours and 6 minutes)
Claude AI app and the web interface experienced a global disruption, with users worldwide reporting the service not loading, prompts failing, or chat interactions timing out. The incident began with an Early Warning Signal at indicating issues with the Apple app, and the signal remained in place until {{time:18:42:00Z}}. Activity from user reports surged through the afternoon, indicating widespread impact across many regions.
Minor
: Claude Opus 4.5 errors trigger brief degraded performance
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 50 minutes)
Claude experienced a brief degradation in Opus 4.5 with increased error rates impacting four components: Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. Users interacting with the API and related tools may have experienced intermittent failures and slower responses. The outage began with an investigation around and the status changed to degraded at .
The issue was resolved by , with the outage lasting approximately 1 hour 53 minutes. The Claude service issued 2 status updates during the incident, describing the ongoing investigation and the subsequent recovery.
Minor
: Claude API degraded due to invalid signature in thinking block
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 35 minutes)
Claude API (api.anthropic.com) experienced elevated errors starting at due to an invalid signature in the thinking block, causing API calls to fail or return errors. The incident lasted until , a total duration of 2 hours and 35 minutes. The issue affected users attempting to use Claude's API endpoints, with responses that were not as expected.
The provider posted two status updates during the incident: the initial notice of elevated errors and ongoing work to fix the issue, and a follow-up stating that the service had returned to normal. Engineers implemented a fix and the Claude API returned to standard operation by the end of the window.
Minor
: Claude API and claude.ai brief outage with elevated errors
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 minutes)
An outage affected Claude API (api.anthropic.com), claude.ai, and Claude Code, causing elevated error rates and degraded performance for a brief period. The incident began at when the Status page indicated a degraded state and was resolved by . The service posted two status updates during the event—one noting elevated error rates and ongoing monitoring, and a follow-up confirming restoration. With user reports indicating widespread impact across multiple regions, the outage lasted about 5 minutes.
Minor
: Claude AI and Claude Code brief degraded performance
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(45 minutes)
Claude.ai began experiencing elevated errors at , with Claude Code joining the disturbance shortly after. Users reported errors when sending prompts, getting responses, or accessing chats, including non-responsive chats, error messages, blank screens, and login or prompt failures. The issue affected both claude.ai and Claude Code and persisted for about 45 minutes before services returned to normal, with restoration indicated by .
The provider issued 3 status updates during the incident, communicating ongoing investigation and eventual restoration: at , , and . A broad set of users across multiple regions reported trouble with chat and coding workflows, reflecting a brief, global impact on Claude AI services.
Minor
: Claude.ai outage disrupts chat across Claude.ai and Claude Code
Detected by StatusGator:
(37 minutes earlier)
Officially acknowledged:
Outage ended:
(1 hour and 22 minutes)
Claude.ai experienced a global outage that disrupted chat and degraded responses on claude.ai and Claude Code. Users reported that messages were not being accepted and conversations were unreliable, with a large volume of user reports (147 total) indicating widespread impact. StatusGator detected the issue at , about 37 minutes before the first official acknowledgment at . The outage affected two components, claude.ai and Claude Code, and lasted until , for a duration of roughly 1 hour 22 minutes.
The Claude status page issued 3 updates during the incident (at , , and UTC). This indicates the incident was actively managed, and services were restored to normal operation after the final update at .
Minor
: Claude outage impacts API, Claude AI, and platform services
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(50 minutes)
On , Claude began investigating elevated errors across four components: Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. Users attempting chat, API calls, or console access experienced degraded functionality across multiple regions during the incident. The status moved to a degraded state at .
The provider published two status updates during the incident, at and , with restoration reported by . The outage lasted about 50 minutes before services returned to normal.
Minor
: Claude API and UI elevated errors; brief partial outage
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(55 minutes)
Claude Opus 4.5 and Sonnet 4.5 experienced elevated errors affecting four components: Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. The Claude status page shows the issue began with an investigation and a transition to a warning at , lasting until when services were restored. The incident involved multiple status updates from the provider and a notable global user impact.
Status updates were posted twice during the event, detailing ongoing investigation and eventual restoration. User reports indicated widespread impact across regions, with API calls failing, UI interactions not responding, and features like prompts and edits not functioning as expected.
Minor
: Claude outage: elevated errors across API, UI, and Code
Detected by StatusGator:
(5 minutes earlier)
Officially acknowledged:
Outage ended:
(1 hour and 1 minute)
The Claude service experienced elevated errors across multiple components, including Claude API, claude.ai, platform.claude.com, and Claude Code, resulting in degraded performance for users. Users reported timeouts, non-responses, and prompts not returning results during the incident. The outage began at and StatusGator detected the issue at , about 5 minutes before Claude acknowledged the problem on their status page. The issue affected 4 components and led to degraded functionality for roughly an hour.
The Claude status page showed the first update at with an Investigating message, and the service was restored by . The Early Warning Signal ended at . The provider issued 2 status updates during the incident.