Anthropic’s Claude went dark for more than five and a half hours on June 2, 2026, cutting off Claude.ai, the Claude API, Claude Console, and Claude Code for users from Sydney to San Francisco. Anthropic’s status page marked the incident as “investigating” at 06:04 UTC and didn’t call it resolved until 11:49 UTC, a run of 5 hours and 44 minutes that ranks among the longest disruptions the company has logged this year. Far from an isolated event, that stretch of June 2026 turned out to be Claude’s 10th disruption in 12 days, according to TechTimes, and the pattern kept going well past June: a July 2026 outage across multiple models that MacRumors reported as resolved at 09:13 UTC, and August 2026 brought no relief, with TechTimes counting 28 separate outages across Claude’s commercial infrastructure in a single 30-day stretch, including one disruption that hit four flagship models at once — Mythos 5, Fable 5, Opus 5, and Opus 4.8 — in a run one tracker counted as Anthropic’s 164th outage overall, followed by a roughly 40-minute August 20, 2026 incident that knocked out Claude.ai, Claude Code, and the newer Cowork product together, described in coverage as hitting “nearly the entire Claude product line.” The disruptions carried into fall, too: BleepingComputer reported Anthropic confirmed Claude was down again in September 2026, with errors spreading across Mythos/Fable 5.1, Mythos/Fable 5, Opus 5, Opus 4.8, and Opus 4.6. The timing stings: Anthropic told the market weeks earlier that its annualized run-rate revenue had crossed $47 billion, up from roughly $9 billion at the end of 2025. Explosive growth and repeat downtime are now landing in the same news cycle, and that combination is what makes June 2 worth examining rather than filing away as routine.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Happened: Inside Anthropic’s Claude Outage on June 2
Anthropic’s own status page logged the first sign of trouble at 06:04 UTC on Tuesday, June 2, 2026, under the incident title “Elevated errors on multiple models.” By 06:39 UTC the company marked the issue “Identified,” language it paired with a note that a fix was being implemented. Users trying to send messages during the window saw one of two error strings depending on which part of the stack they hit: “Due to unexpected capacity constraints, Claude is unable to respond to your message. Please try again soon,” and the shorter “A bit longer, thanks for your patience,” according to The National. A fix appears to have started deploying by 10:42 UTC, based on Anthropic’s own timeline, with full resolution logged at 11:49 UTC. That puts total downtime at 5 hours and 44 minutes, a figure corroborated by Moneycontrol’s report that the disruption ran “for nearly six hours before services were restored,” and separately confirmed by Tech Insider, which likewise logged the incident’s span as 06:04 UTC to 11:49 UTC for a total of 5 hours 44 minutes.
Outage-report volume spiked hard and fast. TechRadar’s live coverage clocked 216 user reports in the UK and 139 in the US on Downdetector within the first stretch of the incident, with those numbers still climbing as the outlet filed updates. Times of India separately reported a sharp spike in complaints originating in India, reinforcing that this wasn’t a regional blip. It hit Claude’s user base across time zones at roughly the same time, which is part of why the June 2 Claude outage generated so much real-time chatter compared with smaller, single-region incidents earlier in the year.
Which Claude Services Went Down, and Which Didn’t
The outage’s reach is part of what made it painful. Reporting from Moneycontrol and the Times of India both list four separate surfaces as affected: Claude.ai (the consumer web app), the Claude API (what third-party apps and enterprise tools call under the hood), Claude Console (the developer dashboard), and Claude Code, Anthropic’s command-line coding agent. That’s notable because in some past Claude incidents, Anthropic kept the API running while consumer-facing claude.ai struggled. A Trending Topics report on the March disruptions specifically noted the API was “not affected” during that earlier episode. June 2 didn’t offer that same partial shelter. Developers building on Claude Code described losing their coding agent mid-task, a scenario that has grown more disruptive as more engineering teams lean on it for daily work rather than occasional use.
One question that didn’t get a clean answer from Anthropic’s own status updates: whether Claude access sold indirectly through Amazon Bedrock or Google Vertex AI was affected the same way as Anthropic’s first-party surfaces. None of the outlets covering the incident in real time reported a Bedrock- or Vertex-specific breakdown, which leaves that part of the blast radius unclear for enterprises that access Claude exclusively through those channels.
Anthropic’s Response and the Root Cause Question
Anthropic’s own account of what went wrong stayed narrow. The status page’s incident title, “Elevated errors on multiple models,” paired with the company’s public framing of “unexpected capacity constraints,” is as specific as Anthropic got in real time. That phrasing points toward a demand-versus-capacity problem rather than a code defect, which fits a company whose run-rate revenue has been roughly doubling every one to two months for most of 2026.
Not every outlet settled on that explanation. One India-focused tech outlet reported a more specific claimed cause: a bug in Claude Code’s sub-agent system. That claim doesn’t appear in Anthropic’s own status updates and wasn’t corroborated by TechRadar, Moneycontrol, or The National, all of which stuck to Anthropic’s “elevated errors” and “capacity constraints” language. Absent a public postmortem from Anthropic itself, the capacity-constraints explanation is the best-supported version of events, and the sub-agent bug claim should be treated as an unconfirmed, single-source report rather than a confirmed root cause. Anthropic has not published a detailed technical postmortem for the June 2 incident, and none of the coverage reviewed here documents an SLA credit, refund, or other compensation offered to Claude Pro, Max, or API customers affected by the downtime.
| Time (UTC) | Status Update | Detail |
|---|---|---|
| 06:04 | Investigating | Status page opens incident: “Elevated errors on multiple models” |
| 06:39 | Identified | Anthropic says the cause has been identified |
| ~07:10 | Downdetector spike | Reports climb to 216 in the UK and 139 in the US, per TechRadar’s live blog |
| 10:42 | Fix in progress | Anthropic’s own timeline shows a fix being deployed |
| 11:49 | Resolved | Incident marked resolved (5h 44m total) |
Developers and Enterprises React to Another Claude Outage
The loudest real-time reaction came from Reddit’s r/ClaudeAI community, where a thread tracking the status update drew roughly 40 comments within hours. Posters described the outage as unusually prolonged compared with Claude’s typical incidents, and at least one user in Australia reported still seeing errors well after the official start time, underscoring how the disruption followed the sun rather than clearing in one region before hitting the next.
This wasn’t developers’ first time voicing outage fatigue. Business Insider covered the mood after the March 2 incident under a headline about developers’ growing reliance on AI, capturing one developer’s complaint that losing Claude access made them feel like they’d have to “write code like a caveman.” Hearing that same frustration resurface in June, three months later, is itself a data point: it suggests Claude’s user base has grown more dependent on the tool between incidents, not less, which raises the stakes of every subsequent outage.
How to Check If Claude Is Down Right Now
Anthropic runs an official status page at status.claude.com, the fastest way to confirm whether an outage is real versus a local network or account issue. It’s also where the company posted every update during the June 2 incident, from “Investigating” through “Resolved.” Third-party trackers add a second layer of confirmation: Downdetector aggregates self-reported outages in real time and was where many users first saw proof the problem wasn’t isolated to them, while StatusGator maintains a longer-running incident history useful for spotting patterns like the one this article covers. For developers specifically, checking Claude API status separately from claude.ai matters, since Anthropic’s status page breaks out Claude.ai, Claude Console, Claude API, and Claude Code as distinct components that don’t always fail together.
Not a One-Off: Claude’s Outage Pattern in 2026
June 2 wasn’t the first Claude outage of 2026, and it wouldn’t be the last. A “last instance of elevated errors” before the March 2 outage occurred on February 28, 2026, tied to Claude Opus 4.6, according to Mashable, which also traced the March 2026 outage itself back to elevated errors on that same Opus 4.6 model via Anthropic’s status page. Then came the March 2 incident itself: Bloomberg reported that outage drew nearly 2,000 Downdetector complaints at its peak, with Anthropic attributing it to “unprecedented demand,” while The Hill reported the disruption ran for close to three hours before Claude was “operational again.” TechCrunch reported that Anthropic’s consumer-facing surfaces, including claude.ai and its apps, were offline for the duration while the company worked on a fix. Less than a month later, incident trackers documented a separate multi-day event on March 26-27, described as degradation tied to networking problems inside Anthropic’s serving infrastructure, resolved by migrating workloads to healthier hardware. The trend carried into spring, too: CNBC reported that Anthropic saw another round of elevated errors in April 2026 spanning the Claude chatbot, the API, and Claude Code, with roughly 2,000 reports again piling up on Downdetector.
Line those incidents up against June 2 and a pattern emerges: each one gets pinned on the same underlying tension between subscriber and API growth and the compute capacity needed to serve it. The pattern didn’t even wait a week to repeat: Cybersecurity News reported a separate June 5, 2026 outage that opened at 15:08 UTC and wasn’t fully restored until 18:27 UTC, with recovery landing in stages across Opus 4.6, Sonnet 4.6, Opus 4.7, Opus 4.8, and Opus 4.5, again hitting the Claude API, Claude Code, and claude.ai. TechTimes then documented a June 16, 2026 incident affecting Opus 4.8 and Haiku 4.5 across Claude.ai, the API, Claude Code, and the Cowork product, in which a status-page fix attempt logged at 2:00 PM ET failed to hold, and by June 23, 2026 a fresh outage across those same four surfaces drew more than 8,000 Downdetector reports in the U.S. alone before a fix tied to a 10:53 a.m. ET rollout finally held. Anthropic’s incident cadence, tracked independently by StatusGator, is unusual for a vendor now processing enterprise-critical workloads for more than 1,000 customers each paying over $1 million a year, according to VentureBeat’s reporting on Anthropic’s enterprise growth.
Claude’s Documented Incidents Since August 2025
| Period | Incident | Reported Scope | Source |
|---|---|---|---|
| Aug-Sep 2025 | Three overlapping infrastructure bugs degraded response quality | Multi-week, with a detailed postmortem published by Anthropic | Industry incident archives |
| Feb 28, 2026 | Elevated errors on Claude Opus 4.6 | Duration not specified | Mashable |
| Mar 2, 2026 | Widespread outage tied to “unprecedented demand” | ~3 hours, ~2,000 Downdetector reports at peak | Bloomberg, The Hill |
| Mar 26-27, 2026 | Networking degradation in serving infrastructure | Multi-day, fixed via workload migration | Incident tracking logs |
| Jun 2, 2026 | “Elevated errors on multiple models,” capacity constraints | 5h 44m. Claude.ai, API, Console, and Code all affected | Anthropic status page, TechRadar |
Claude vs ChatGPT vs Gemini vs Grok: Who Fared Better on June 2
Coverage of June 2 split on whether Claude was alone in struggling that day, a relevant question for anyone tracking the wider AI models market. LetsDataScience published a dedicated fact-check concluding the event was “primarily a Claude incident rather than a simultaneous, coordinated outage across ChatGPT, Grok, and other services,” arguing that headlines grouping multiple AI assistants together overstated what the evidence showed. Anthropic’s competitors, in that framing, mostly benefited as a landing spot for frustrated Claude users switching over rather than as fellow victims.
At least one other tracker disagreed. A post from infrastructure blog Ssimplifi described Claude, ChatGPT, and Grok as all logging outages “inside the same window” on June 2, though it offered less detail than the Claude-specific coverage and didn’t specify durations for the other two services. Neither OpenAI nor Google has published uptime or reliability statistics for ChatGPT or Gemini that would let outsiders check either claim independently, and neither company issued a public statement about its own status on June 2 in any of the coverage reviewed for this piece.
What is well documented is that ChatGPT has its own outage history, including a widely reported global disruption in July 2025. The bigger competitive story isn’t really about who went down on one Tuesday. It’s that none of the three leading consumer AI labs publish the kind of standardized uptime figures that cloud vendors like AWS and Azure have reported for years, which makes apples-to-apples reliability comparisons across ChatGPT, Gemini, Grok, and Claude difficult for anyone outside those companies to verify.
The Growth-Versus-Infrastructure Gap Behind the Outages
Anthropic’s growth curve in 2026 is genuinely unusual. The company ended 2025 with roughly $9 billion in annualized run-rate revenue. Bloomberg reported that figure had surpassed $19 billion by early March 2026. It kept climbing past $30 billion by early April and past $47 billion by mid-May, according to Anthropic’s own disclosures around its most recent funding round. That’s better than a fourfold increase in under five months, layered on top of a customer base that VentureBeat reported had grown to more than 1,000 enterprise accounts each spending upward of $1 million a year, roughly double the count Anthropic had in February 2026 alone. The consumer side scaled just as fast: Claude AI Statistics 2026 data compiled by Sensor Tower put monthly active users at roughly 245 million by mid-2026, a surge Anthropic tried to monetize from multiple directions, restructuring enterprise pricing in April 2026 from a flat $200-a-month plan to a $20-a-month base tier plus usage-based billing, according to Biz Chosun, while also launching Claude Fable 5 in June 2026 with API pricing set at $10 per million input tokens and $50 per million output tokens, per The AI Insider.
No infrastructure plan built for a $9 billion company scales cleanly to a $47 billion one in the same fiscal year. Anthropic has been diversifying its compute supply to keep pace, expanding partnerships around Google’s TPU fleet and Broadcom alongside its existing reliance on Amazon’s Trainium chips, but multi-vendor compute brings its own coordination overhead. “Unexpected capacity constraints” is Anthropic’s own phrase for what happened on June 2, and it lines up with a company adding enterprise customers faster than it can provision hardware to serve them. The pattern across the February, March, and June 2026 incidents all trace back to some version of the same story: demand outrunning capacity, not a single bad code deploy.
Anthropic’s Revenue Curve in 2026
| Period | Annualized Run-Rate Revenue | Source |
|---|---|---|
| Dec 2025 | ~$9 billion | Bloomberg |
| Early Mar 2026 | >$19 billion | Bloomberg |
| Early Apr 2026 | >$30 billion | Contemporary industry reporting |
| Early May 2026 | ~$30 billion+ | VentureBeat |
| Mid-May 2026 | >$47 billion | Anthropic company disclosure |
Market Impact: What Downtime Costs When AI Is the Product
For a company selling chat subscriptions, an afternoon outage is an inconvenience. For a company whose product increasingly sits inside other companies’ production pipelines, as Claude does through the API and Claude Code, an outage is a supply-chain event. Businesses that have wired Claude into customer support, coding pipelines, or internal automation don’t have an easy manual fallback when the model goes dark for nearly six hours in the middle of a workday.
None of the coverage reviewed here documents a quantified revenue-loss estimate, a stock-price reaction (Anthropic remains private), or a formal SLA credit issued to affected customers, and that absence is itself worth flagging. As more of the economy routes through a small number of frontier model providers, the financial accounting for AI downtime is still immature compared with how cloud providers report and compensate for outages. What is measurable is customer behavior: Moneycontrol ran a companion piece during the outage window listing alternatives users could switch to, a genre of article that has become a predictable feature of every major Claude outage and a signal that switching costs for casual chat use are low even where switching costs for deeply integrated coding workflows are not.
Historical Context: From Chatbot Downtime to Mission-Critical Risk
Outages used to be a footnote in AI coverage. When Claude, ChatGPT, or Gemini went down in 2023 or 2024, the story was mostly about inconvenienced consumers unable to get a chatbot answer. That framing doesn’t fit 2026. Claude Code alone has become embedded enough in professional software development that Business Insider was documenting developer anxiety about Claude dependence back in March, months before June 2 added a fresh data point. Anthropic’s own claimed enterprise base, over 1,000 accounts each spending seven figures annually, is not a base of casual chatbot users. It’s a base of companies that made build decisions assuming Claude would be there.
The closest precedent for the current run of incidents is Anthropic’s own August-September 2025 episode, when three overlapping infrastructure bugs degraded Claude’s output quality over several weeks. That earlier event was serious enough that Anthropic published an unusually detailed public postmortem, an approach the company hasn’t repeated for any of its 2026 incidents so far. The contrast matters: 2025’s problems were arguably more severe but came with more transparency, while 2026’s incidents have been more frequent but explained in a few short status-page sentences. It’s a trade worth watching, since it shapes how much enterprises can plan around Claude’s reliability going forward, including teams already comparing Claude Opus 4.8’s benchmark performance against how often the model is actually reachable.
What Anthropic Needs to Fix Next
Three fixes stand out from the pattern of 2026 incidents. First, capacity planning needs to catch up with sales: a company whose enterprise account count is doubling every few months cannot keep provisioning compute reactively. Second, Anthropic’s public communication during incidents has been thinner than its own 2025 precedent set. A “capacity constraints” status update is not the same as the kind of postmortem that lets enterprise customers assess their own risk. Third, and hardest to fix quickly, Anthropic needs a credible answer for customers asking whether Claude Code and API traffic can be isolated from consumer claude.ai traffic during a crunch, so a spike in casual chatbot usage doesn’t take down a paying enterprise’s production coding pipeline in the same incident. That isolation problem hasn’t gone away: an August 20, 2026 incident took down Claude.ai, the API, Claude Code, and the newer Cowork collaboration product all at once, exactly the kind of undifferentiated, product-line-wide failure the third fix is meant to prevent. Access restrictions are already part of Anthropic’s playbook elsewhere: the company’s own Claude Mythos 5 access limits show it’s willing to segment who can reach a given model when circumstances demand it, a precedent it extended just weeks later when a U.S. export-control directive forced Claude Fable 5 offline for foreign nationals starting June 12, 2026, according to TechTimes, with Sensor Tower’s Claude AI Statistics 2026 report noting Fable 5 access wasn’t restored for U.S.-based users until July 1, 2026.
None of this is unique to Anthropic. Every frontier AI lab scaling this fast will hit some version of the same wall. But Anthropic is the one whose growth numbers and incident count both spiked in full public view during the same quarter, which makes it the test case the rest of the industry is watching, in the same way repeat cloud outages forced AWS customers to rethink single-region designs a decade earlier.
5 Predictions for AI Reliability Through the Rest of 2026
- Published uptime SLAs arrive for enterprise tiers. As more $1 million-plus accounts pile onto Claude, expect Anthropic and its rivals to start publishing formal uptime commitments and credits for enterprise and API customers, rather than relying on status-page language alone.
- More frequent, shorter incidents before things improve. Expect the pace of minor-to-moderate incidents to stay elevated through the rest of 2026 as Anthropic’s revenue keeps climbing faster than any single capacity expansion can absorb, before new TPU and Broadcom-linked capacity comes fully online.
- Multi-provider failover becomes a standard enterprise pattern. Expect more engineering teams to formalize automatic failover between Claude, GPT, and Gemini API endpoints for production workloads, following the same logic that pushed cloud architects toward multi-region designs after early AWS outages.
- Anthropic publishes a fuller postmortem for at least one 2026 incident. Pressure from enterprise customers and the contrast with Anthropic’s own 2025 transparency will likely push the company toward at least one detailed technical writeup before year-end, even if routine incidents stay terse.
- Rivals stay quiet on their own numbers. Don’t expect OpenAI or Google to start publishing standardized ChatGPT or Gemini uptime statistics just because Claude’s outages are drawing scrutiny. Without regulatory or contractual pressure, frontier labs have shown little appetite for that kind of public accountability.
Here’s what that incident sequence looked like on Anthropic’s own status log, reconstructed from the company’s public timeline for June 2:
Jun 2, 06:04 UTC - Investigating
Elevated errors on multiple models. We are investigating.
Jun 2, 06:39 UTC - Identified
The issue has been identified. A fix is being implemented.
Jun 2, 10:42 UTC - Fix in progress
A fix has been implemented and we are monitoring the results.
Jun 2, 11:49 UTC - Resolved
This incident has been resolved. Total duration: 5h 44m.Related Coverage
For more on Anthropic, Claude, and how AI providers are handling 2026’s infrastructure crunch, see:
- Claude Opus 4.8 Hits 61.4, Tops AI Leaderboard [2026]
- Claude Mythos 5 Blackout: GPT-5.6 Capped at 20 Firms [2026]
- Opus 4.8 vs GPT-5.6 vs Gemini 3.1 Pro: $18 Price Gap [2026]
- Claude Code vs Codex: 23% Higher Cost Per Task [2026]
- AWS Outage Hits US-West-2: 3rd Incident in 3 Months [2026]
- Microsoft Taps AWS as GitHub Outages Hit 9 [2026]
Frequently Asked Questions About the Claude Outage
What caused the June 2, 2026 Claude outage? Anthropic attributed it to “elevated errors on multiple models” and “unexpected capacity constraints.” The company hasn’t published a detailed technical root-cause analysis, and one outlet’s claim of a specific Claude Code sub-agent bug hasn’t been corroborated by Anthropic’s own status updates.
How long was Claude down on June 2, 2026? Anthropic’s status page shows the incident open from 06:04 UTC to 11:49 UTC, a total of 5 hours and 44 minutes.
Which Claude services were affected? Claude.ai, the Claude API, Claude Console, and Claude Code were all listed as affected in reporting from Moneycontrol and the Times of India.
Is this the first time Claude has gone down in 2026? No. Prior and subsequent 2026 incidents include elevated errors on Claude Opus 4.6 on February 28, a widespread outage on March 2 tied to “unprecedented demand,” a networking-related degradation on March 26-27, an April 2026 round of elevated errors across the chatbot, API, and Claude Code reported by CNBC, a June 5 outage running from 15:08 to 18:27 UTC per Cybersecurity News, a June 16 incident hitting Opus 4.8 and Haiku 4.5 across Claude.ai, the API, Claude Code, and Cowork, a June 23 outage across those same surfaces that drew more than 8,000 U.S. Downdetector reports before a 10:53 a.m. ET fix took hold, a July 2026 multi-model outage MacRumors reported as resolved at 09:13 UTC, a roughly 40-minute August 20 incident that knocked out nearly the entire Claude product line including Cowork, an August 24, 2026 bout of elevated errors spanning Mythos 5, Fable 5, Opus 5, and Opus 4.8 that one tracker counted as Anthropic’s 164th outage to date — part of a stretch TechTimes tallied at 28 separate outages across Claude’s commercial infrastructure in just 30 days — and, into September 2026, a further outage BleepingComputer reported hitting Mythos/Fable 5.1, Mythos/Fable 5, Opus 5, Opus 4.8, and Opus 4.6.
Did Anthropic offer refunds or SLA credits for the outage? None of the coverage reviewed for this article documents a compensation or SLA-credit announcement tied to the June 2 incident.
Were ChatGPT and Gemini also down on June 2, 2026? Reports conflict. A dedicated fact-check from LetsDataScience concluded the Claude outage was primarily a Claude-specific incident, while at least one other tracker described brief, less-detailed disruptions at ChatGPT and Grok in the same window. Neither OpenAI nor Google has published an official statement confirming outages of their own that day.
How big is Anthropic’s business right now? Anthropic’s annualized run-rate revenue crossed $47 billion by mid-May 2026, up from around $9 billion at the end of 2025, with more than 1,000 enterprise customers each spending over $1 million a year, according to VentureBeat.
What should businesses relying on Claude do to reduce outage risk? Common approaches include building failover logic to a second model provider for production workloads, caching or queuing requests during degraded periods, and monitoring Anthropic’s status page directly rather than relying solely on in-app error messages.
