Claude goes dark for two and a half hours as a sub-agent loop eats the serving fleet, three weeks after the IPO filing
Anthropic's status page logged elevated error rates at 14:19 UTC on June 23, identified the fix at 14:25 UTC and cleared the queue by 16:44 UTC. Downdetector peaked above 8,000 US reports while claude.ai, the Console, the API, Claude Code and Claude Cowork failed together. Claude for Government stayed up. The incident is the second multi-product outage of the month on a system that runs 99.12 to 99.41 percent ninety-day uptime three weeks after the company filed an S-1 at $965 billion.
TechRadar · The Next Web · status.claude.com · 2026-06-23 · Source ↗ ·
Anthropic's status page logged the first sign of trouble at 14:19 UTC on Tuesday, June 23, with elevated error rates across multiple Claude models. Six minutes later, at 14:25 UTC, the company moved the incident to "identified" and began rolling out a fix. By 16:44 UTC the queue was clear and the page flipped to monitoring. Within that window claude.ai, the Console, the public API, Claude Code and Claude Cowork were all returning errors simultaneously, while Claude for Government kept serving without disruption. Downdetector peaked at 7,119 US reports at 10:13 ET and crossed 8,000 in aggregate across the incident window, with smaller spikes recorded in the United Kingdom and Germany. It is the second multi-product Claude outage of June and the eleventh distinct Claude incident in twelve days according to the status timeline.
Anthropic did not publish a root cause in the public material around the incident. TechTimes, citing two engineers inside customer-side deployments who saw their Claude Code agentic pipelines fail in characteristic ways during the window, described "a critical bug that caused sub-agents to multiply exponentially rather than complete their assigned work," generating "an infinite loop that consumed platform resources at an unsustainable rate." That description fits the symptom set reported by customers on the Anthropic forum and on the r/ClaudeAI subreddit through the morning: parent agents launching child agents that launched grandchild agents that never completed, individual tool calls failing for lack of headroom while the overall request count from each affected tenant ballooned. Engineers on customer-side calls described autoscale tripping in the orchestration tier without bringing the queue down because every newly spun child task generated more work upstream.
"We've identified a fix for elevated errors across multiple Claude models."— Anthropic status page entry, 14:25 UTC, June 23
The reliability picture on a public-company timeline
Anthropic's own ninety-day uptime statistics, taken from the company's published status pages on the morning of the incident, show claude.ai running at 99.12 percent, Claude Code at 99.28 percent and the API at 99.41 percent. Translated into hours that is roughly nineteen to twenty-three hours of downtime per service per quarter. Enterprise software contracts in the markets Anthropic is selling into usually carry 99.9 percent or 99.95 percent uptime commitments with credits attached below threshold; Claude is currently running an order of magnitude below that envelope across the trio of products that anchor the agentic-development pitch. The June 23 incident lands three weeks after Anthropic confidentially filed an S-1 with the Securities and Exchange Commission at a $965 billion valuation on a $47 billion annualised run rate, the largest gap between revenue trajectory and reliability profile in recent enterprise-software history.
Claude Code is the part of the franchise most exposed to the failure mode. Anthropic in late May added a sub-agent orchestration layer that lets a parent Claude Code instance dispatch child agents for parallel work across a codebase. The feature has been one of the most heavily marketed capabilities of the post-Fable-5 product lineup, the architectural anchor of the company's pitch that Claude Code is the tier-one harness for autonomous engineering. The June 23 symptom set, with parent-child task multiplication consuming serving capacity, is the canonical failure mode for that architecture under load: a control plane that cannot back-pressure parents when children are queueing. Two of the past month's reliability incidents have traced to the same surface area.
"The product is shipping at the cost of operational maturity. The orchestration tier was the most aggressive bet in the Claude Code launch, and it's the part that keeps breaking."— Senior infrastructure engineer at an Anthropic enterprise customer, paraphrased to TechTimes
Customers, contracts and the Government carve-out
Claude for Government, which runs in a physically separate GovCloud environment with its own model-serving stack, was not affected by the June 23 incident. That separation is now the most reliable surface in Anthropic's product line and the only one that consistently meets the uptime requirements written into the company's federal contracts. It is also the surface farthest from the orchestration features that account for most of the recent downtime, because GovCloud customers run an older, slower-moving release train. The widening gap between government-tier reliability and commercial-tier reliability is becoming a story of its own inside the customer base; several enterprise buyers who spoke to reporters in the wake of the outage said they have started asking Anthropic whether they can be moved to a configuration closer to the GovCloud release cadence in exchange for accepting longer feature lag.
The competitive picture sharpens what comes next. OpenAI shipped GPT-5.5-Cyber to broad availability on June 22 with Daybreak and Patch the Planet as the orchestrated security tier, and is widely expected to graduate GPT-5.6 inside the week per Polymarket pricing. Google DeepMind's Gemini 3.5 Pro general-availability window opens June 23 to 30 with the 2-million-token context and Deep Think reasoning tier. Z.ai's GLM-5.2 sits one rung below Fable 5 on coding benchmarks and is currently the most capable model that an enterprise can actually invoke without uptime risk this week. The June 23 outage does not, on its own, change the customer-spend trajectory that took Anthropic past OpenAI in US business AI spending to 41 percent in May. It does pull the question of operational maturity forward into the S-1 review window, where it now sits alongside the export-control overhang and the 42-state attorney-general probe as a structural item to address before the September IPO window.
Claude goes dark for two and a half hours as a sub-agent loop eats the serving fleet, three weeks after the IPO filing
Anthropic's status page logged elevated error rates at 14:19 UTC on June 23, identified the fix at 14:25 UTC and cleared the queue by 16:44 UTC. Downdetector peaked above 8,000 US reports while claude.ai, the Console, the API, Claude Code and Claude Cowork failed together. Claude for Government stayed up. The incident is the second multi-product outage of the month on a system that runs 99.12 to 99.41 percent ninety-day uptime three weeks after the company filed an S-1 at $965 billion.
TechRadar · The Next Web · status.claude.com · 2026-06-23 · Source ↗ ·
Anthropic's status page logged the first sign of trouble at 14:19 UTC on Tuesday, June 23, with elevated error rates across multiple Claude models. Six minutes later, at 14:25 UTC, the company moved the incident to "identified" and began rolling out a fix. By 16:44 UTC the queue was clear and the page flipped to monitoring. Within that window claude.ai, the Console, the public API, Claude Code and Claude Cowork were all returning errors simultaneously, while Claude for Government kept serving without disruption. Downdetector peaked at 7,119 US reports at 10:13 ET and crossed 8,000 in aggregate across the incident window, with smaller spikes recorded in the United Kingdom and Germany. It is the second multi-product Claude outage of June and the eleventh distinct Claude incident in twelve days according to the status timeline.
Anthropic did not publish a root cause in the public material around the incident. TechTimes, citing two engineers inside customer-side deployments who saw their Claude Code agentic pipelines fail in characteristic ways during the window, described "a critical bug that caused sub-agents to multiply exponentially rather than complete their assigned work," generating "an infinite loop that consumed platform resources at an unsustainable rate." That description fits the symptom set reported by customers on the Anthropic forum and on the r/ClaudeAI subreddit through the morning: parent agents launching child agents that launched grandchild agents that never completed, individual tool calls failing for lack of headroom while the overall request count from each affected tenant ballooned. Engineers on customer-side calls described autoscale tripping in the orchestration tier without bringing the queue down because every newly spun child task generated more work upstream.
"We've identified a fix for elevated errors across multiple Claude models."— Anthropic status page entry, 14:25 UTC, June 23
The reliability picture on a public-company timeline
Anthropic's own ninety-day uptime statistics, taken from the company's published status pages on the morning of the incident, show claude.ai running at 99.12 percent, Claude Code at 99.28 percent and the API at 99.41 percent. Translated into hours that is roughly nineteen to twenty-three hours of downtime per service per quarter. Enterprise software contracts in the markets Anthropic is selling into usually carry 99.9 percent or 99.95 percent uptime commitments with credits attached below threshold; Claude is currently running an order of magnitude below that envelope across the trio of products that anchor the agentic-development pitch. The June 23 incident lands three weeks after Anthropic confidentially filed an S-1 with the Securities and Exchange Commission at a $965 billion valuation on a $47 billion annualised run rate, the largest gap between revenue trajectory and reliability profile in recent enterprise-software history.
Claude Code is the part of the franchise most exposed to the failure mode. Anthropic in late May added a sub-agent orchestration layer that lets a parent Claude Code instance dispatch child agents for parallel work across a codebase. The feature has been one of the most heavily marketed capabilities of the post-Fable-5 product lineup, the architectural anchor of the company's pitch that Claude Code is the tier-one harness for autonomous engineering. The June 23 symptom set, with parent-child task multiplication consuming serving capacity, is the canonical failure mode for that architecture under load: a control plane that cannot back-pressure parents when children are queueing. Two of the past month's reliability incidents have traced to the same surface area.
"The product is shipping at the cost of operational maturity. The orchestration tier was the most aggressive bet in the Claude Code launch, and it's the part that keeps breaking."— Senior infrastructure engineer at an Anthropic enterprise customer, paraphrased to TechTimes
Customers, contracts and the Government carve-out
Claude for Government, which runs in a physically separate GovCloud environment with its own model-serving stack, was not affected by the June 23 incident. That separation is now the most reliable surface in Anthropic's product line and the only one that consistently meets the uptime requirements written into the company's federal contracts. It is also the surface farthest from the orchestration features that account for most of the recent downtime, because GovCloud customers run an older, slower-moving release train. The widening gap between government-tier reliability and commercial-tier reliability is becoming a story of its own inside the customer base; several enterprise buyers who spoke to reporters in the wake of the outage said they have started asking Anthropic whether they can be moved to a configuration closer to the GovCloud release cadence in exchange for accepting longer feature lag.
The competitive picture sharpens what comes next. OpenAI shipped GPT-5.5-Cyber to broad availability on June 22 with Daybreak and Patch the Planet as the orchestrated security tier, and is widely expected to graduate GPT-5.6 inside the week per Polymarket pricing. Google DeepMind's Gemini 3.5 Pro general-availability window opens June 23 to 30 with the 2-million-token context and Deep Think reasoning tier. Z.ai's GLM-5.2 sits one rung below Fable 5 on coding benchmarks and is currently the most capable model that an enterprise can actually invoke without uptime risk this week. The June 23 outage does not, on its own, change the customer-spend trajectory that took Anthropic past OpenAI in US business AI spending to 41 percent in May. It does pull the question of operational maturity forward into the S-1 review window, where it now sits alongside the export-control overhang and the 42-state attorney-general probe as a structural item to address before the September IPO window.