Claude went down twice in 14 hours — and Anthropic's uptime numbers tell the full story
Two Claude outages in 14 hours on June 22–23 pushed 90-day uptime below enterprise SLA thresholds, with 8,000+ Downdetector reports at peak.
Two separate Claude outages hit within 14 hours of each other on June 22 and 23, and the numbers sitting on Anthropic’s own status page make the situation harder to ignore. Across claude.ai, the Claude API, and Claude Code, 90-day uptime figures are currently 99.12%, 99.41%, and 99.28% respectively. That sounds fine until you compare it to the 99.9% threshold that most enterprise software contracts require. At 99.9%, you’re allowed roughly two hours of downtime per service per quarter. Anthropic’s current figures translate to somewhere between 19 and 23 hours per service. That gap matters if your team is building production workflows on top of Claude.
What actually happened
The first incident began just after midnight UTC on June 22. Anthropic’s engineering team opened an investigation at 00:37 UTC into elevated error rates hitting five models simultaneously: Opus 4.8, Opus 4.7, Opus 4.6, Sonnet 4.6, and Haiku 4.5. Recovery didn’t happen all at once. The team brought models back one by one, with monitoring confirming a fix by 02:06 UTC. A roughly 90-minute window of disruption, resolved before most US-based users started their day.
Then a second wave emerged the same afternoon. Elevated error rates across the same model set were logged from 08:11 UTC, with a fix confirmed at 14:44 UTC on June 22.
Less than 14 hours after that, the June 23 incident began. Reports started coming in around 10:02 am Eastern Time, and Downdetector peaked at over 8,000 reports in the United States alone. Anthropic’s status page logged the investigation opening at 14:19 UTC and marked the issue as identified by 14:25 UTC, six minutes later. Error rates broadly returned to normal by 16:44 UTC. Affected services spanned the full platform: Claude.ai, the Claude API, Claude Console, Claude Code, and Claude Cowork.
Anthropic has not published a root-cause analysis for either incident.
The demand problem Anthropic acknowledged publicly
When asked about the pattern of disruptions, Anthropic told Fortune: “Demand for Claude has grown at an unprecedented rate, and our infrastructure has been stretched to meet it, particularly at peak hours.” The company pointed to compute capacity deals with Amazon and Google as sources of relief, though most of that capacity isn’t expected to be operational until late 2026 or into 2027.
The scale of the mismatch is striking. Anthropic’s annualised revenue run rate moved from roughly $9 billion at the end of 2025 to $47 billion by May 2026. The company has separately disclosed that demand is running approximately 80 times higher than it planned for at the start of 2026. Infrastructure cannot scale that fast, regardless of how many supply contracts you sign.
These two incidents on June 22 and 23 are not isolated. TechTimes documented what was at the time the tenth significant disruption since June 5, averaging roughly one per day. The June 22 overnight outage was the third disruption that month alone, following a major multi-hour event on June 2 and a networking degradation incident on June 5.
What the error types tell you
Anthropic’s API documentation distinguishes between two error types developers encounter during outages. An HTTP 500 error means something has failed inside Anthropic’s infrastructure and requires a server-side fix. An HTTP 529 error means the system is technically healthy but is rejecting requests because it has hit capacity limits. Crucially, 529 errors do not count against your usage quota and resolve when capacity frees up. During peak-demand outages, knowing which error you’re seeing tells you whether to wait it out or escalate.
What this means if you’re building on Claude
If your team uses Claude primarily through the chat interface for research or drafting, a 90-minute outage is annoying. If you have production pipelines calling the Claude API, or CI/CD workflows integrated with Claude Code, the calculus is different. Development cycles stall, automated content pipelines miss scheduled runs, and any customer-facing feature that depends on Claude goes silent.
The June 2 incident is worth understanding as a specific warning. That outage was traced to a bug in Claude Code’s sub-agent architecture, where sub-agents designed to parallelise complex coding tasks entered an infinite loop and multiplied exponentially. Anthropic issued an automated quota reset for affected Pro and Max accounts after the fact. But if your pipelines are deeply integrated with Claude Code’s agentic features, you are inheriting whatever failure modes exist in that architecture, and Anthropic has not yet published detailed post-mortems explaining what changed to prevent recurrence.
Practical steps worth taking now, if you haven’t already: implement multi-model failover routing so a single provider outage doesn’t halt your entire pipeline, treat AWS Bedrock’s Claude access as a separate failure domain from Anthropic’s direct API, and add circuit breakers to any workflow that calls Claude Code as part of an automated process.
The broader timing
All of this is happening roughly three weeks after Anthropic confidentially filed for an IPO that could value the company above $1 trillion. Operational reliability is not a minor footnote for a company at that stage. Investors and enterprise procurement teams making multi-year commitments will be looking at the same uptime figures that are publicly visible on status.claude.com, and those numbers currently sit below the threshold that enterprise SLAs typically require.
Anthropic’s compute partnerships with Amazon, Google, Microsoft, and others represent genuine capacity on the way. But the gap between contracted capacity and operational capacity is measured in months, and the current demand curve is not waiting.
For now, the practical reality is that Claude is a powerful platform running under significant strain. Plan your integrations accordingly.
Updates to this story
30 July 2026: Claude suffers two network outages in 24 hours on July 29–30; Claude for Government stays online
The reliability pattern documented in this article has continued. Two separate network failures on July 29 and July 30 caused elevated errors and reduced availability across claude.ai, the API, Claude Code, and Claude Cowork. Services were fully restored by late July 30, with StatusGator confirming recovery by July 31 at 4:23 AM UTC.
The first incident ran from approximately 12:45 PT to 1:26 PT on July 29, producing widespread 529 Overloaded errors. A second, longer incident began at 6:03 AM UTC on July 30 and lasted roughly four hours. Anthropic confirmed in its official acknowledgment that multiple separate network failures cut into serving capacity, requiring traffic rerouting before full recovery.
Two details sharpen the picture from the June outages covered here. First, Claude for Government remained unaffected throughout, consistent with its isolated infrastructure holding up during earlier incidents. Second, StatusGator records now show 155 Claude outages since January 2026, which reframes any single event as part of a sustained frequency problem rather than an isolated bad day.
No root-cause postmortem had been published at the time of this update. Teams with uptime SLA requirements should note that the Government tier has consistently been the only surface to stay insulated across this year’s incident log.
26 July 2026: Claude Opus 5 elevated errors on July 26 — incident resolved, but reliability timeline worth tracking
The incident is resolved. Anthropic logged elevated errors for Opus 5 on July 26 at 9:17 UTC, with resolution confirmed by 10:44 UTC, and status.claude.com shows no incidents on July 27.
The timing matters. Claude Opus 5 launched on July 24, meaning this availability event hit within roughly 48 hours of the model going public. It also did not arrive in isolation. A related incident on July 25 at 19:44 UTC had already flagged elevated errors across Claude Mythos 5, Fable 5, and Haiku 4.5, making this a multi-model disruption window spanning two days. Opus 5 immediately became the default model on Claude Max at launch, which amplifies the blast radius of any outage affecting it.
This adds another data point to the pattern covered in the original article. The 90-day uptime figures from status.anthropic.com now stand at 99.53% for the API and 99.45% for Claude Code, both still short of the 99.9% threshold common in enterprise SLAs. The June 22 to 23 double outage is already baked into those trailing numbers, and the July 25 to 26 window will apply further pressure as the rolling window advances.
For teams evaluating Opus 5 as a production default, the core question from the original article holds: the reliability track record needs to close the gap before the uptime figures justify enterprise SLA commitments.
22 July 2026: Claude suffers another user-reported outage on July 22, raising reliability questions
The June 22-23 double outage covered in this article is no longer an isolated low point. On July 22, Claude experienced a multi-wave disruption that stretched across most of the UTC working day, adding fresh pressure to Anthropic’s reliability record.
Anthropic’s status page logged five separate incidents on July 22, beginning with elevated errors on Claude Opus 4.1 at 8:34 AM UTC and continuing through a broader service disruption resolved at 5:45 PM UTC. Affected services included document creation on claude.ai, Claude Code, Cowork Remote, Claude Design, and the Microsoft 365 add-ins for Word, PowerPoint, and Excel. Third-party tracker StatusGator recorded a warning state lasting 8 hours and 42 minutes on July 22, with a further 6 hours and 44 minutes carrying into July 23.
This is not a one-off. Confirmed disruptions have now hit on July 9, 14, 16, 17, 21, and 22. Hundreds of users filed reports on Downdetector around 1:15 PM Eastern Time on July 22, echoing the spike pattern seen in June.
For enterprise buyers already watching 90-day uptime figures after the June incidents, the cumulative July picture makes the trend harder to dismiss as noise. The June 22-23 analysis below remains accurate as a baseline; July has extended and reinforced it.
17 July 2026: Claude reportedly suffers another outage on July 17 — Anthropic’s second in a month
What looked like a single July 17 outage is actually a cluster of four separate incidents across July 16 and 17, making the situation worse than initial reports suggested.
The most significant episode was on July 16, when a major outage affected multiple models for roughly 3 hours 26 minutes (11:30 AM to 3:15 PM PT). July 17 then brought three further incidents: an early morning degradation affecting Sonnet 5 and Haiku 4.5 (resolved in around 20 minutes), an afternoon server overload lasting approximately 1 hour 32 minutes that generated the DownDetector UK spike around 2:56 PM BST, and a brief evening partial outage for Sonnet 5 users lasting roughly 10 minutes. All incidents are now resolved.
This pattern extends the reliability concern raised in the original June 22 to 23 article. The current 90-day uptime figures from status.claude.com show Claude Code at 99.47% and the core API at 99.53%, both still below the 99.9% threshold common in enterprise SLAs. The afternoon DownDetector reports, while notable, were considerably smaller in scale than the 8,000 plus reports logged during the June double-outage. Anthropic has previously attributed capacity issues to surging enterprise adoption of Claude Code alongside rising consumer signups.