Anthropic's status page published an incident report on July 29, 2026, titled "Elevated errors across all models," documenting a service degradation affecting the company's Claude model lineup. The incident page, hosted at the dedicated URL on status.claude.com, confirmed the disruption spanned the full range of models rather than a single endpoint or deployment tier. Anthropic Status Page

The July 29 event follows a separate, earlier July incident recorded in Anthropic's status history. That earlier disruption, identified as "Elevated errors on Claude Opus 5 and Haiku 4.5," was resolved as of 14:34 UTC (7:34 PST). The scope was narrower, limited to two specific models rather than the full fleet. The status history page does not provide a root-cause analysis for the earlier incident. Anthropic Status History

These incidents arrive against a backdrop of recurring availability issues for Anthropic's services. On June 23, 2026, TechRadar reported a Claude outage that Anthropic confirmed as resolved. No official explanation for the increased errors was provided at that time. TechRadar

Anthropic's status page, powered by Atlassian Statuspage, recorded 99.40% uptime for claude.ai during July 2026. The page also shows no incidents reported on July 28, 2026, the day before the most recent "elevated errors" event. For a service increasingly embedded in production workflows, API pipelines, and agentic systems, a 99.40% monthly figure translates to roughly 26 minutes of aggregate downtime across the month, though the actual user impact depends on when those errors cluster. Anthropic Uptime

The distinction between "elevated errors" and a full outage matters operationally. Elevated errors typically manifest as increased HTTP 5xx responses, elevated latency, or degraded inference quality rather than a hard service unavailability. For teams running Claude behind retry logic, circuit breakers, or multi-provider fallback configurations, the impact may be limited to increased tail latency or higher retry volumes. For teams with tighter coupling, a sustained elevation in error rates can propagate into application-level failures, particularly in agentic pipelines where a single failed step can abort a multi-turn workflow.

The progression from a two-model incident in early-to-mid July to an all-model incident on July 29 is worth noting, though the verified facts do not establish whether the events share a common root cause. Anthropic has not, based on the available status page records, published a post-incident analysis tying the July events together. The June 23 outage similarly lacked an official explanation.

What this means in practice is that organizations building on Claude should treat status page incident reports as one signal among several. The "all models" scope of the July 29 incident is a reminder that a failure mode affecting shared infrastructure (serving layer, routing, or model hosting) can negate the redundancy assumptions teams make when they spread workloads across different Claude model variants. A fallback from Opus to Haiku provides no resilience if both are served through the same degraded layer.

For context, the major API-based model providers have all experienced incidents of this nature. The operational pattern is familiar: a degradation is detected, a status page entry is posted, service is restored, and in some cases a post-mortem follows. Whether Anthropic publishes a detailed post-incident review for the July 29 event will be telling. The absence of an explanation for the June 23 outage set a precedent that leaves downstream consumers without the root-cause information needed to adjust their own resilience strategies.

The 99.40% July uptime figure, while not catastrophic, sits below the 99.9% or higher thresholds that many enterprise service-level agreements target. Teams that have committed to upstream SLAs based on assumed provider availability may find that figure uncomfortable. The practical takeaway is that multi-provider redundancy, already a common pattern among sophisticated API consumers, continues to earn its architectural cost.

For now, the July 29 incident page is the authoritative record. Whether it is followed by a detailed post-mortem or, as with the June event, closed without public explanation, will determine how much downstream teams can learn from it.