Claude Outage History

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 Jan 22, 2026 3:31 PM UTC, about 37 minutes before the first official acknowledgment at Jan 22, 2026 4:08 PM UTC. The outage affected two components, claude.ai and Claude Code, and lasted until Jan 22, 2026 4:53 PM UTC, for a duration of roughly 1 hour 22 minutes.

The Claude status page issued 3 updates during the incident (at Jan 22, 2026 4:08 PM UTC, Jan 22, 2026 4:13 PM UTC, and Jan 22, 2026 4:53 PM UTC UTC). This indicates the incident was actively managed, and services were restored to normal operation after the final update at Jan 22, 2026 4:53 PM UTC.

On Jan 21, 2026 2:44 PM UTC, 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 Jan 21, 2026 2:48 PM UTC.

The provider published two status updates during the incident, at Jan 21, 2026 2:48 PM UTC and Jan 21, 2026 3:38 PM UTC, with restoration reported by 3:38 PM UTC. The outage lasted about 50 minutes before services returned to normal.

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 Jan 20, 2026 4:43 PM UTC, lasting until Jan 20, 2026 5:38 PM UTC 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.

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 4:38 PM UTC and StatusGator detected the issue at Jan 20, 2026 4:38 PM UTC, 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 4:43 PM UTC with an Investigating message, and the service was restored by 5:38 PM UTC. The Early Warning Signal ended at 5:13 PM UTC. The provider issued 2 status updates during the incident.

Claude.ai experienced degraded performance due to compaction issues. The incident began at 7:28 AM UTC when Claude.ai moved into a degraded state as engineers identified the problem and began implementing a fix. Users reported issues related to the compaction feature and slower responses during this period.

Two status updates were issued during the incident, and Claude.ai returned to normal by 5:03 PM UTC. The outage lasted approximately 9 hours and 35 minutes, with the Claude.ai component returning to full functionality after the fix was deployed.

Claude experienced a global outage affecting Claude API (api.anthropic.com), claude.ai, and Claude Code. Users worldwide reported errors and degraded responses as requests failed. The outage began at 10:48 AM UTC and was resolved by 2:08 PM UTC, lasting about 3 hours and 20 minutes.

During the incident, the Claude status page issued three updates. The first acknowledged elevated error rates and said a fix was in progress; the second indicated continued work on a fix; the third confirmed restoration of services. The disruption affected three components and was reflected by a large volume of user reports from many regions, indicating widespread impact.

StatusGator detected issues at Jan 14, 2026 9:33 AM UTC, 45 minutes before Claude acknowledged the problem. The outage affected Claude API (api.anthropic.com), claude.ai, and Claude Code, causing errors and degraded access for users. The incident began with elevated error rates and widespread impact across Claude services, with users reporting global connectivity and responsiveness issues.

Claude experienced degraded performance beginning 8:34 AM UTC with elevated error rates across Claude API (api.anthropic.com), claude.ai, and Claude Code. Users worldwide reported authentication failures and errors when sending prompts. The incident prompted investigation and remained in a degraded state until it was resolved by 9:53 AM UTC. The outage spanned roughly 1 hour and 19 minutes and affected three components.

During the incident, Claude issued 2 official status updates. A large volume of user reports showed widespread impact across many regions, with issues described as unable to access or use Claude services. There was no clear regional concentration, indicating a global service degradation rather than a regional outage.

Claude experienced a brief degradation affecting multiple components after reports of increased errors tied to Opus 4.5. Users may have encountered errors when using the Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. The incident began with an investigation at Jan 13, 2026 7:27 AM UTC and a degraded state was observed starting at Jan 13, 2026 7:28 AM UTC.

Claude experienced a brief outage during a scheduled maintenance window affecting core chat and API functionality. The outage began at 7:04 AM UTC and was resolved by 7:27 AM UTC, lasting roughly 23 minutes. Users across multiple regions reported failures and degraded prompts or chat responses, indicating a global impact.

StatusGator detected the issue at Jan 13, 2026 7:04 AM UTC, ahead of any official acknowledgement from Claude on their status page. Claude did not publish an official status update during the incident, and the outage appears to have been contained by the end time with service restoring afterward.