Claude went down on Tuesday morning. Anthropic confirmed a partial outage affecting claude.ai, Claude Code, Claude Cowork, the public API, and the developer Console, with user reports spiking just before 10:30am ET. The company said it was aware of the disruption within the hour and pushed a mitigation within minutes — a short but conspicuous blip for one of the most-used AI services on the planet.

Reports started climbing on Downdetector at the top of the hour, and within minutes Anthropic's own status dashboard was showing "partial outage" across nearly the entire Claude surface. The company said it was aware of the problem just prior to 10:30am ET (7:30am PT).

The timeline, as tracked by the incident hub that r/ClaudeAI's moderators set up, was short: investigation began around 14:00 UTC, a mitigation went in by about 14:36 UTC, and error rates started falling afterward — a roughly 40-minute window. Users in the United States and Brazil confirmed failures on the thread, suggesting the impact was global rather than confined to one region. Some people could log in but hit errors the moment they started a new conversation; others were locked out entirely, at least intermittently.

Illustration of people staring at laptops and phones showing error screens during a cloud service outage
Illustration: AI-generated for AI Frontier Post

What users saw — and what they ruled out#

The r/ClaudeAI thread turned into a live triage board. One early theory — that a terms-of-service popup was blocking access — was quickly knocked down: plenty of users who never saw the popup were getting errors anyway. A joke suggesting sabotage ahead of OpenAI's DevDay got laughs but was dismissed as exactly that. (DevDay is scheduled for September 30, which this blog will be covering separately.)

What nobody disputed was the shape of the problem: the services loaded, the interface responded, and the inference layer behind it didn't. Some users described agentic workflows and looping tasks that hit dead ends mid-run — the exact kind of workload that makes even a half-hour outage expensive for developers building on the API.

Illustration of a chatbot interface going dark with a dimming sunburst logo shattering like glass
Illustration: AI-generated for AI Frontier Post

A rough September for uptime#

Tuesday's outage lands in a month that has already had more than its share of red on the status pages. Anthropic logged partial outages on September 22, September 15, and September 11, plus a major outage on September 3 that arrived at the same time as disruptions at ChatGPT and Grok. The September 3 event hit multiple labs at once; this one, by contrast, appears to be Anthropic's alone — this morning's scattered reports of ChatGPT and Gemini problems were not confirmed by either OpenAI or Google.

The timing is awkward in one specific way: Claude Sonnet 5.5 launched just the day before, and a fresh model release is exactly when new users pile on and existing users run it hard. Anthropic has not said the launch was related — and to be clear, nothing in the public record ties the two together. But outages in launch week are the kind of thing customers remember.

What to watch#

Anthropic has not publicly named a root cause. The questions that matter now: does the company post a postmortem explaining what broke and what it is changing; does "partial outage" become a recurring line on the status page this quarter; and how do developers building on the API calibrate their retry and fallback logic after a morning that proved even a 40-minute window can strand real workloads.

For casual users, the takeaway is simple: the outage was real, it was company-confirmed, and it was over before noon on the East Coast. For everyone building production systems on top of hosted models, it's another reminder that the cloud has always had bad mornings — AI just makes them everyone's business.

Sources#