Anthropic’s Claude AI platform experienced a significant service disruption on July 29, 2026, with elevated error rates and latency affecting all models across its entire product suite.
The incident affected claude.ai, the Claude API (api.anthropic.com), Claude Code, and Claude Cowork, disrupting workflows for developers, enterprises, and individual users who rely on Claude-powered applications.
The outage began at 19:49 UTC (12:49 PT) when Anthropic’s status page first flagged the issue as under investigation.
Claude Global Outage Caused Elevated Errors
Engineers had not yet pinpointed a root cause at this stage, though users across multiple platforms began reporting failed requests and sluggish response times almost immediately.
By 20:33 UTC, Anthropic’s engineering team identified the source of the elevated errors, confirming that the problem spanned multiple models rather than being isolated to a single deployment.
This distinguished the incident from typical model-specific hiccups, pointing instead to a broader infrastructure or backend issue affecting request processing across Claude’s entire model lineup.
At 21:38 UTC, Anthropic issued an update noting that recovery efforts were underway and that most models were beginning to show improvement.
This roughly one-hour gap between identification and initial recovery suggests the fix required coordinated backend changes rather than a simple configuration rollback, a pattern common in outages tied to load-balancing failures, capacity constraints, or upstream dependency issues.
The most critical window of impact occurred between 19:45 UTC and 21:26 UTC, roughly 12:45 PT to 1:26 PT, during which Claude models experienced their highest error rates.
This near two-hour disruption window would have caused noticeable service degradation for API-dependent applications, particularly those with limited retry logic or strict latency requirements.
At 22:20 UTC, Anthropic moved the incident to monitoring status, reporting recovery across all models and confirming that success rates had returned to normal levels.
The company continued observing system performance to rule out any recurrence before formally closing the incident at 22:36 UTC, marking a total incident duration of approximately two hours and 47 minutes from initial detection to resolution.
While Anthropic has not published a detailed post-incident report or root cause analysis, the pattern of the outage is evident: it affected all models simultaneously across every platform surface.
Suggests that a shared infrastructure component, such as an API gateway, authentication layer, or request-routing system, was responsible, rather than an issue with any individual model’s inference pipeline.
For organizations building on Claude’s API, this incident serves as a reminder of the importance of implementing robust fallback mechanisms, including retry logic with exponential backoff and multi-provider redundancy for latency-sensitive applications.
Enterprises running mission-critical workloads on Claude Code or Claude Cowork should also review their incident response playbooks to account for upstream provider outages of this scale.
Anthropic has not yet indicated whether a full incident postmortem will be published, though the company’s status page remains the primary channel for real-time updates on service health.
Cut SOC investigation blind spots and contain threats earlier to reduce response costs and business disruption with ANY.RUN.
