Claude Outage History

Claude.ai connectors experienced degraded performance due to an elevated error rate when establishing new connections. The issue affected users relying on Claude.ai connectors, causing connection failures and slower workflows. The incident began at Feb 3, 2026 6:43 PM UTC and lasted about 2 hours and 5 minutes, ending at Feb 3, 2026 8:48 PM UTC when the service returned to normal. The Claude.ai component issued 2 status updates during the incident, describing an ongoing investigation and eventual restoration. User reports indicated connection issues in some locations, reflecting a limited but noticeable impact before resolution.

The Claude API and related services across API, UI, and coding interfaces experienced a brief outage lasting about 21 minutes. Users attempting to use Claude capabilities encountered errors or degraded responses across api.anthropic.com, claude.ai, platform.claude.com, and Claude Code. The outage began on 3:48 PM UTC and was resolved by 4:09 PM UTC, with a global pattern of reports indicating widespread disruption.

Claude’s status page showed early actions: an update at 3:46 PM UTC stating the issue had been identified and a fix was being implemented, followed by recovery updates as services came back online. In total, four components were affected, and the incident was resolved after about 21 minutes.

Claude experienced an API outage affecting all models, including Claude API, claude.ai, platform.claude.com, and Claude Code. Users reported internal server errors and HTTP 500 responses, hindering access to Claude services. The outage began at 3:48 PM UTC and was resolved by 4:09 PM UTC, lasting about 21 minutes. StatusGator detected the issue earlier, with reports starting at Feb 3, 2026 3:37 PM UTC, roughly 11 minutes before Claude acknowledged the incident. Early Warning Signal observed: StatusGator detected issues at Feb 3, 2026 3:37 PM UTC.

The Claude Opus 4.5 stack briefly experienced elevated errors affecting Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. The incident began at 11:15 PM UTC with engineers investigating, and the status page showed a degraded state at 11:18 PM UTC. The issue was resolved and services returned to normal by 11:23 PM UTC. The Claude status page posted two updates during the incident. A limited number of user reports suggested sporadic impact during the window, but the outage was short and contained.

Claude.ai and platform.claude.com experienced a degraded purchase flow beginning around Feb 1, 2026 9:59 PM UTC due to credit purchase issues and delays. Some API or Extra Usage purchases were charged but credits were not immediately reflected, impacting access to services that rely on up-to-date credit balances. The incident affected two components (claude.ai and platform.claude.com) and lasted until around Feb 1, 2026 11:48 PM UTC when status returned to normal.

Status communications included two updates on the Claude status page: the issue was first listed as a warning at Feb 1, 2026 10:03 PM UTC and later resolved back to normal at Feb 1, 2026 11:48 PM UTC. User reports came from multiple regions, including New Zealand, the United States, and the United Kingdom, indicating a broad impact on purchasing and credit balance updates. The outage duration was approximately 1 hour and 49 minutes.

Claude API, claude.ai, platform.claude.com, and Claude Code experienced a brief degraded performance due to elevated errors. The issues began at Feb 1, 2026 11:36 AM UTC and were resolved by Feb 1, 2026 12:38 PM UTC, affecting API access, chat interactions, and coding features during that window.

The Claude status page documented the incident with two updates, first indicating a degraded state at 11:48 AM UTC and later confirming restoration at 12:38 PM UTC. The outage lasted roughly 1 hour and 2 minutes as systems returned to normal after the final update.

Claude Opus 4.5 briefly experienced degraded performance across multiple components, including Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. The incident began at 10:58 AM UTC and was resolved by 11:43 AM UTC, lasting about 45 minutes. The Claude status page reported elevated errors and published two updates during the incident, indicating ongoing investigation before the services returned to normal.

Claude Code experienced memory leaks in Claude Code 2.0.27, causing degraded performance for some users. The Claude status page moved to a degraded state at 8:18 PM UTC and noted that the problem had been identified with a fix in progress; more details were linked to Github issue #22042. The issue affected the Claude Code component and prompted two official status updates during the incident.

Two updates were issued as the team worked on a fix, and the problem was resolved when Claude Code returned to normal at 9:08 PM UTC, with the incident lasting roughly 50 minutes.

The Claude platform experienced a brief partial outage affecting the ability to purchase API credits on platform.claude.com (formerly console.anthropic.com). Some users could not complete API credit purchases during the incident. The issue began at Jan 29, 2026 7:13 PM UTC and was resolved by Jan 29, 2026 8:43 PM UTC, lasting about 1 hour 30 minutes. The Claude status page listed the event as a degraded purchase flow and issued 2 updates before full restoration.

Claude Opus 4.5 experienced elevated errors affecting several Claude services, including Claude API (api.anthropic.com), claude.ai, platform.claude.com, and Claude Code. Users attempting to use Claude endpoints may have encountered errors or degraded responses during the incident window.

This was a repeat of an incident earlier in the day. The Claude status page shows errors restarting from 1:41 PM UTC, with the degraded condition beginning at Jan 28, 2026 1:53 PM UTC and the incident resolving by Jan 28, 2026 2:18 PM UTC, lasting about 25 minutes from Jan 28, 2026 1:53 PM UTC to Jan 28, 2026 2:18 PM UTC. The provider issued two status updates during the incident, and services returned to normal afterward.