Anthropic’s Claude AI platform suffered its tenth significant service disruption since June 5 on Tuesday afternoon, when errors began hitting Claude Opus 4.8 and Haiku 4.5 at 1:29 PM ET — a pattern that has emerged as a direct consequence of the company’s own admission: demand for Claude has grown faster than its infrastructure can handle. The incident remains unresolved as of the most recent status update, affecting users of claude.ai, the Claude API, Claude Code, and Claude Cowork, and arrives the day after a proposed class-action lawsuit accused Anthropic of delivering far less AI service than its premium subscribers paid for.

Anthropic’s official status page confirmed the incident began at 5:29 PM UTC (1:29 PM ET) on Tuesday. A fix was declared at 6:00 PM UTC, but a follow-up update at 6:15 PM UTC reported that errors on Opus 4.8 and Haiku 4.5 persisted. As of 7:00 PM UTC (3:00 PM ET), the company said it was “continuing to work to resolve an elevated rate of errors on requests to Claude Opus 4.8” and would provide another update “as soon as possible.” Searches for “is Claude down” surged on Google Trends as users scrambled to confirm the issue. Claude Console and Claude for Government appear to be unaffected by the current incident.

What Anthropic Has Said

Anthropic has not issued a standalone public statement on the June 16 incident beyond its rolling status page updates. That absence continues a pattern: the company has not published post-incident root cause analyses or detailed engineering post-mortems for any of its recent June disruptions, according to a review of public reporting.

The company’s most candid public acknowledgment of its infrastructure problems came in a statement to Fortune in April 2026, after a separate wave of outages and user backlash over Claude Code performance. “Demand for Claude has grown at an unprecedented rate, and our infrastructure has been stretched to meet it, particularly at peak hours,” Anthropic said. The statement added: “Compute is a constraint across the entire industry, and we are scaling our compute rapidly and responsibly — including through a recently announced expansion of our partnership with Amazon and Google, which will bring significant new capacity online in the coming months.”

That capacity has not yet arrived. The disruptions have continued.

June 2026: A Reliability Pattern That Should Concern Enterprise Buyers

Tuesday’s outage is the latest in a documented run of service failures that began June 5. Independent monitoring by StatusGator confirms the following incidents for claude.ai since that date:

June 5 — Significant outage affecting claude.ai, the API, Claude Code, and Claude Cowork. Anthropic investigated user reports of potential data leakage and found no evidence of customer data exposure, attributing the disruption to an infrastructure failure.June 7 — Warning-level incident lasting 1 hour and 19 minutes.June 8 — Warning-level incident lasting 2 hours and 4 minutes.June 9 — Two separate incidents: a 25-minute warning and a 1-hour-40-minute degradation.June 10 — Warning-level incident lasting 3 hours and 14 minutes.June 11 — Two separate incidents: a 24-minute warning and a 29-minute outage.June 13 — Warning-level incident lasting 39 minutes.June 15 — Warning-level incident lasting 1 hour and 54 minutes.

That sequence puts the mean time between significant failures at roughly one day — a figure that would breach standard commercial service-level agreements that enterprise cloud providers typically guarantee at 99.9% uptime or higher.

Why Agentic Claude Code Users Face Amplified Risk

For individual users, a Claude outage is an inconvenience. For the growing number of engineering teams that have embedded Claude Code into automated workflows, the risk is categorically different.

According to a February 2026 SemiAnalysis report, Claude Code now accounts for roughly 4% of all public GitHub commits, processing more than 135,000 commits per day. Unlike a flat chatbot session — where a user can simply wait and retry — Claude Code is increasingly deployed as a component inside CI/CD pipelines that execute multi-step tasks autonomously. When an outage interrupts one of those tasks mid-run, the pipeline does not pause and resume; it fails, often requiring manual intervention to clean up partially executed operations.

Thoughtworks noted after the June 2 outage that the core problem is single-vendor dependency: “hardcoding a specific provider’s API endpoint into your application was an acceptable availability strategy” in the early days of AI adoption, but “in 2026, it’s a single point of failure that’s a very real threat to business continuity.”

Anthropic itself distinguishes between two error types that developers see during outages: HTTP 500 errors, which indicate an internal server failure inside Anthropic’s infrastructure, and HTTP 529 errors, which signal capacity overload — the system is technically healthy but rejecting requests because it has reached its limit. Per Anthropic’s own API documentation, a 529 error “does not count against your quota” and resolves when capacity frees up, while a 500 error requires a server-side fix. Both have appeared during June’s disruptions.

What Is Driving the Failures

The infrastructure strain is traceable to a convergence of factors. Runtime.news reported in March 2026 that Anthropic’s infrastructure is struggling to keep pace with the surge in demand for its Opus and Sonnet models following Claude Code’s rapid growth, compounded by a 55% jump in Claude mobile app downloads after Anthropic’s public dispute with the Pentagon over AI safety restrictions. That dispute — in which Anthropic refused to allow Claude’s use for fully autonomous weapons or mass domestic surveillance — led the Trump administration to designate the company a supply-chain risk, which in turn drove users away from competitors and toward Claude.

The customer growth numbers are striking. Anthropic’s annualized revenue climbed from $9 billion at end-2025 to more than $30 billion in early April 2026, with the number of enterprise clients spending more than $1 million annually doubling from 500 to 1,000 in under two months. The infrastructure was not built for that pace.

How to Check Claude’s Real-Time Status

Users and developers experiencing issues can monitor live updates at status.claude.com. The page breaks down the health of individual services — claude.ai, the API, Claude Code, and Claude Cowork — and supports email, SMS, Slack, and Microsoft Teams notifications for incident alerts. For developers, Anthropic’s API documentation recommends switching to a different model tier during model-specific capacity events: the error message from Claude Code during overloads prompts users to run /model and select a less-constrained model.

As of Tuesday at 3:00 PM ET, the incident remained active. TechTimes will update this article as the situation develops.

Frequently Asked Questions

Is Claude down right now on June 16, 2026?

As of 3:00 PM ET on June 16, 2026, yes — Anthropic’s status page confirms an active incident affecting Claude Opus 4.8 and Haiku 4.5, with elevated error rates reported across claude.ai, the Claude API, Claude Code, and Claude Cowork. A fix attempt at 2:00 PM ET failed to hold. The company says it is continuing to work on a resolution.

Why does Claude keep going down in June 2026?

Anthropic acknowledged in a statement to Fortune that demand for Claude has grown faster than its infrastructure can support, particularly at peak hours. The company attributed the problem to unprecedented user growth — driven partly by enterprise adoption of Claude Code and partly by a surge in downloads after Anthropic’s public dispute with the Pentagon — while noting it is expanding compute capacity through partnerships with Amazon and Google. That new capacity is not yet available.

What should I do if Claude is unavailable?

Check status.claude.com for real-time updates and subscribe to email, SMS, or Slack alerts. If you are a developer using the Claude API, note that the direct Anthropic API and AWS Bedrock run on separate infrastructure pools — during some outages, Bedrock remains available when the direct API does not. Claude Code users can run the /model command to switch to a different model tier when one model is experiencing capacity constraints.

What does the Kahn v. Anthropic lawsuit have to do with today’s outage?

Filed June 14, 2026, in the Northern District of California, the proposed class-action lawsuit by plaintiff Karl Kahn alleges that Anthropic’s Claude Max plans deliver far less usage than advertised — the Max 20x plan allegedly provides only six to eight times the base Pro tier’s usage rather than the promised twenty times. Anthropic declined to comment. Both the lawsuit and the pattern of outages trace to the same underlying problem: a subscription model and infrastructure pool that were not designed to sustain the rate at which today’s heaviest users — particularly those running agentic Claude Code workflows — consume compute.