Claude Keeps Going Down, and Anthropic's Own Status Page Says So

Open Claude on a weekday in August 2026 and there’s a fair chance you’ll meet a spinner, an error, or the words “server is busy” where an answer should be. It might be Claude Code stalling mid-task, the app refusing to load a chat, or the API throwing elevated error rates at whatever you built on top of it. You are not imagining it, and you don’t have to take our word for it: the receipts are on Anthropic’s own status page.

Answer first, because the shape of this is simple and the excuses are not. Claude has had a genuinely rough month. By Anthropic’s own count on status.claude.com, there were roughly twenty separate incidents in the first twenty-four days of August — degraded performance, elevated errors, and a couple of outright service disruptions — and as we hit publish on the 24th, a fresh one marked “major” was still unresolved, taking claude.ai, the API, Claude Code and Cowork down together. That is close to an incident a day. The reason it matters isn’t that software sometimes breaks; everything breaks. It’s who pays for it, and how.

We should say up front that Anthropic does a lot right here, and we’ll give it that in full below. A public, granular status page is more honesty than much of the industry offers, and most of these incidents were short. But “short and frequent” is still a pattern, and when you’re paying for a tool with a metered allowance, the frequency is the problem.

What the status page actually shows

The spine of this piece is a primary source, which is how we like it. Anthropic’s status history for August 2026 reads like a metronome: 3 August, elevated errors on Sonnet 5; 4 August, elevated errors across many models; 5 August, degraded performance for multiple models for the best part of a working day; 12 August, degraded performance again; 13 August, elevated errors across Mythos 5, Fable 5 and Sonnet 5; 14 August, two “service disruption” incidents in one day; 16 August, a disruption logged at the most severe “critical” level; 17, 18 and 19 August, more degraded performance, repeatedly naming Opus 5; 20 August, another burst of elevated errors. Then the 24th, and the one that is still open as we write.

That live incident is worth quoting precisely, because the breadth is the point. Anthropic titled it “Elevated errors for multiple models”, began investigating at 05:06 UTC, and within the hour reported it had “identified the cause of elevated errors on requests to Claude Mythos 5, Claude Fable 5, Claude Opus 5, and other Claude models.” The affected components listed were not niche: claude.ai, the Claude API, Claude Code and Claude Cowork — the front door, the developer platform, the coding tool and the agent workspace, all at once. When the failure spans every surface, there’s nowhere for a paying user to route around it.

Why a “degraded” day costs you twice

Here is the detail that turns an engineering story into a consumer one. Claude’s paid plans don’t sell you unlimited use; they meter it, against a rolling five-hour window and a weekly cap. We’ve written before about how Claude’s rate limits are hard to reason about at the best of times. Now layer an unreliable service on top. When the system is overloaded, a request can still draw down your allowance and then fail — you pay the toll and don’t cross the bridge.

Users are describing exactly that. On r/ClaudeAI on 24 August, one poster totted up the damage under the title “23% of 5-hour limit for ‘server is busy’”: “I can wait, but the fact that it Ate up my tokens is wild. 3 prompts and I have to wait 4 more hours.” Another, on the same day, said Claude had “been down for 2 hours now.” We can’t audit any one person’s meter, and we present these as user reports rather than measurements — but the mechanism they describe is real and by design: a fixed budget spent on failed requests is gone whether or not you got anything back. That is the difference between an outage on a free product and an outage on a metered subscription. On the free tier you lose time; on the paid tier you lose time and money.

This is why an outage lands differently on a paid plan than a free one, and why it belongs in the same file as every other way a flat-looking AI plan quietly behaves like a meter. You didn’t buy a fixed number of answers; you bought a fixed number of attempts, and a flaky service spends some of them for you. On a good week that’s invisible. In a month of near-daily incidents, it’s the difference between a weekly limit you’d never reach and one you keep bumping into for reasons that have nothing to do with how much work you actually got done.

The timing: a flagship, then a wobble

Context matters, and the calendar is suggestive without being conclusive. Anthropic launched Claude Opus 5 on 24 July 2026, its new premium flagship. The reliability run we’re describing began within weeks and repeatedly named Opus 5 among the affected models. It is reasonable to read that as capacity strain: a new, heavier, more capable model lands, demand surges, and the plumbing groans. It is not proof of one, and Anthropic hasn’t published a root-cause, so we won’t assert a motive or a mechanism the company hasn’t confirmed. We’ll say only what the record supports: the flagship shipped, and the month after it, the service kept stumbling.

This is a familiar tension in the frontier race, and not unique to Anthropic. The incentive is to ship the biggest new model on the fastest cadence, and reliability is the quiet variable that gets traded against it — the thing that doesn’t make the launch video. We made a version of this argument when OpenAI’s outages stopped being news and became a pattern; the uncomfortable point is that it now applies to the lab most associated with caution. When the whole industry optimises for capability-per-launch, the customer experiences it as capability that isn’t always there.

The steel-man, in full

Now the genuinely fair part, because there is a lot of it. First, transparency: Anthropic runs a detailed public status page, posts incident-by-incident updates with timestamps, and doesn’t hide behind a vague “some users may experience issues.” This entire article is built from data the company published about itself, which is exactly the accountability we keep asking the industry for. Credit where it’s due.

Second, severity. Most of the August incidents were “degraded performance” or “elevated errors” lasting well under a couple of hours, not multi-day blackouts. A slow or flaky Claude is maddening, but it is not the same as a service that vanishes for a week. Third, the underlying difficulty is real: serving a state-of-the-art model to a stampede of users, many of them running long agentic coding sessions that hammer the API, is a hard operational problem, and no lab has solved it perfectly. If you want the biggest model in the world on tap, some of this is the cost of the frontier.

Concede all of that, and the criticism doesn’t vanish; it just gets more precise. Reliability isn’t a bonus feature layered on top of a subscription — for a professional tool it is the product, alongside the honest limits you were sold. A month of near-daily incidents, with a metering system that can bill you for the failures, is a real degradation of the thing people pay for, however transparently it’s logged. The status page is the receipt, not the remedy.

What to actually do

If you rely on Claude and August has been painful, the practical moves are undramatic:

• Check the primary source, not your vibes. Before assuming it’s you, open status.claude.com. If a component is amber or red, it’s Anthropic’s outage, not your prompt.
• Don’t burn quota into a busy server. If you’re getting “server is busy” or errors, stop retrying in a loop — on a metered plan, each attempt can cost you. Wait for the status page to go green.
• Keep a fallback ready. If your work is critical, don’t single-home it on one model’s uptime. A second tool you can switch to for an hour is cheaper than a lost afternoon.
• Log it, for yourself. If failed requests are eating your limit, note the dates and times against the public incident history. If you ever ask about a refund or credit, “your own status page shows a major incident during my failed session” is a stronger position than a feeling.

None of this is a call to cancel, and none of it is a claim that Anthropic acted in bad faith. It’s a plainer observation: for a few weeks in August 2026, one of the most trusted tools in AI kept falling over, its own status page kept the tally, and the people best placed to notice were the ones paying for it by the week. The company that documents its failures this openly is also the one best placed to fix them — and the honest measure of whether it’s working won’t be the next launch, but a September where the status page is boringly green.