Claude Outage History

A brief outage impacted Claude’s core tooling around Opus 4.8, with users facing elevated error rates and temporary service disruption messages. The affected components included Claude Console (platform.claude.com), Claude Cowork, Claude for Government, Claude API (api.anthropic.com), claude.ai, and Claude Code. The incident began around 2:33 PM UTC as the team investigated the elevated error rates, leading to degraded experiences for users trying to upload documents or images.

Users experienced errors when calling the Claude API for Opus 4.5 beginning at 1:39 PM UTC. The service reported elevated errors and a degraded state while engineers investigated, impacting applications that rely on api.anthropic.com for programmatic access.

At 1:53 PM UTC the issue was identified and a fix was being implemented. The service recovered about 38 minutes later, with 2:18 PM UTC marking the API returning to normal operation. A small number of user reports documented sporadic issues during the outage.

Claude reported elevated errors on Opus 4.8 Fast, affecting users attempting to use that feature during a short incident. The status page moved to a warning at 6:23 PM UTC with an update that an investigation was underway. The issue was resolved about 15 minutes later, with the page returning to normal operation at 6:38 PM UTC. A small number of user reports surfaced before the official acknowledgment, indicating some users encountered errors ahead of Claude's notice. Throughout the event, Claude provided updates describing the investigation and the eventual restoration of Opus 4.8 Fast.

Users worldwide experienced errors and slower responses from Claude's AI service, with reports spanning Europe, North America, Africa and the Middle East. Symptoms included error messages and noticeably longer processing times. StatusGator detected degraded performance starting at Jun 24, 2026 2:01 PM UTC and the issue persisted until Jun 24, 2026 2:34 PM UTC; user reports were posted from 1:15 PM UTC through 2:30 PM UTC.

A coordinated outage hit Claude Opus 4.8, causing an elevated error rate and degraded availability across Claude Console, Claude Cowork, Claude API, claude.ai, and Claude Code. Users globally reported errors and longer processing times, with issues affecting login, responses, and feature usage. The impact appeared across regions including Europe, North America, and parts of the Middle East and Asia, indicating widespread disruption to multiple Claude services.

Users on Claude.ai began reporting issues around 6:15 PM UTC as elevated error rates appeared for the service. The Claude.ai component then moved from up to a degraded state at 6:28 PM UTC, with the engineering team quickly initiating investigation. The disruption affected typical Claude.ai usage, causing errors for requests and responses for about five minutes until the service was restored by 6:33 PM UTC.

An outage hit Claude services across multiple components, with prompts failing and models not loading for the Claude Console, Claude Cowork, Claude API, claude.ai, and Claude Code. Impact started around 2:24 PM UTC and persisted for nearly two hours, as users reported not receiving responses or experiencing long wait times. StatusGator had detected issues earlier, with an Early Warning Signal logged at 2:06 PM UTC indicating prompts and models were not responding, roughly 17 minutes before the official acknowledgement. The episode spanned global usage, affecting developers, teams, and researchers relying on Claude for chat, coding, and API integrations.

An outage affected Claude Opus 4.8, disrupting the Claude Cowork, Claude Console, Claude API, claude.ai, and Claude Code services. Users reported elevated errors, slow responses, and timeouts across these areas. The incident began at 6:33 AM UTC as the Claude status page indicated an active investigation, signaling a broad disruption to core Claude functionality. The impact was felt by users relying on the suite for development, collaboration, and automated tasks.

A brief disruption affected Claude services, with elevated errors reported across Claude Cowork, Claude API (api.anthropic.com), claude.ai, and Claude Code. The incident began at 7:18 PM UTC as the Claude status page noted an outage and that the team was investigating. A few minutes later, the issue appeared to stabilize and the components returned to normal by 7:23 PM UTC—roughly five minutes of degraded access for users. The status page indicated ongoing investigation during the outage and later signaled recovery. User reports during the window were limited, consistent with a short-lived disruption impacting multiple models in parallel. The incident did not show regional concentration and was resolved across all affected components.

Claude users were hit by an outage beginning at 8:13 AM UTC as elevated errors affected Claude Opus 4.8 components. The disruption touched Claude Cowork, Claude API (api.anthropic.com), claude.ai, and Claude Code, with reports of sign-in failures, timeouts, and API overload errors such as 529 across regions including Europe, North America, and Asia-Pacific.

Status page updates from Claude indicated ongoing investigation and a move toward restoration. By 10:03 AM UTC, the affected components had returned to an operational state, marking the end of the outage and return to normal service.

User observations show a global pattern, with reports from Melbourne, Milan, Bengaluru, Dubai and other locations, suggesting broad reach rather than a single regional problem. The disruption lasted roughly two hours and primarily affected API access and developer tooling rather than all Claude services.