Claude Overloaded Error (529): What It Means and Fixes

The Claude overloaded error — HTTP 529, type overloaded_error — means Anthropic's servers are temporarily at capacity across all users. It is not your account, plan, API key, or code. Wait 30 seconds to a few minutes and retry; on the API, retry with exponential backoff, and switch to a lighter model if it keeps firing.

We run this site's content pipeline against the Claude API and build with Claude Code daily, so the Claude overloaded error finds us at the worst moments — mid-refactor, mid-publish, once mid-demo. The good news: it's the most benign error Anthropic returns, and the fix is mostly patience applied correctly. Below: where it appears, how it differs from a 500 and a 429, the fixes ordered by effort, and when the status page becomes your next stop.

What the Claude overloaded error actually means

Anthropic's official API error reference defines the 529 in one line: overloaded_error — "The API is temporarily overloaded." The docs add the detail that settles most confusion: 529 errors occur when the API experiences high traffic across all users. Demand briefly exceeds serving capacity, so healthy servers shed load rather than melt down. On the API the response looks like this:

{
  "type": "error",
  "error": {
    "type": "overloaded_error",
    "message": "Overloaded"
  },
  "request_id": "req_011CSHoEeqs5C35K2UUqR7Fy"
}

Read what the Anthropic overloaded error is not saying. Nothing malfunctioned — that would be a 500. You didn't exceed a personal quota — that would be a 429. Your request never got processed, so it doesn't count against your usage limits either. The 529 is a bouncer at a full venue: the club is fine, you're fine, there's no room this second. That's why every "fix" aimed at your own machine — reinstalling, clearing caches, regenerating API keys — does nothing. Capacity lives on Anthropic's side, and searches for "Claude servers overloaded" spike in the same minutes for everyone.

Where the 529 shows up: claude.ai, the API, and Claude Code

The Claude overloaded error wears different costumes depending on the surface in front of you. This table saves the cross-referencing we had to do the hard way:

Two useful implications. First, when the chat app cites capacity constraints and your API dashboard shows 529s in the same window, that's one event, not two problems. Second, if a wrapper tool reports Claude as "overloaded," debugging the wrapper is wasted effort — the error originated at api.anthropic.com and merely traveled through.

529 vs 500 vs 429: same red text, different problems

The Claude 529 error gets misdiagnosed constantly because its siblings look identical in a terminal at 11pm. They demand different responses, and the error.type field is how your code — and your instincts — should tell them apart:

The 429/529 confusion is the expensive one. A 429 says change your behavior; a 529 says your behavior is irrelevant. Treating a 529 like a 429 wastes an afternoon auditing quotas you never touched; treating a 429 like a 529 — "just retry harder" — digs the hole deeper. One nuance from Anthropic's docs: a sharp ramp in your organization's traffic can trigger 429s from acceleration limits even below quota, so grow volume gradually.

How to fix the Claude overloaded error

There is no secret fix — capacity is Anthropic's to add — but there is a right order of moves, and it beats angry refreshing by a wide margin:

1. Wait one to five minutes, then retry once. Most Claude overloaded errors clear inside five minutes as load shifts and capacity auto-scales. In Claude Code your prompt stays in the conversation, so typing "try again" resends it. Calm single retries succeed; tight retry loops join the stampede that caused the spike.
2. Check status.claude.com. Ten seconds. If a capacity incident is posted, stop troubleshooting and come back later; if it's green, you're in a transient spike that will pass without ceremony.
3. Switch to a lighter model. Capacity is tracked per model, and the biggest model saturates first. When Claude Opus 4.8 is refusing traffic, Claude Sonnet 4.6 or Claude Haiku 4.5 usually answers immediately — use the model picker on claude.ai or /model in Claude Code. Our Claude models guide covers what you give up in the swap (often less than you'd think).
4. Shift heavy jobs off-peak. Overload clusters in weekday US business hours, roughly late morning through early afternoon Pacific. We moved our bulk generation runs to early morning UTC and stopped seeing 529s almost entirely.
5. Skip the folk remedies. Reinstalling the app, clearing caches, regenerating keys, and upgrading your plan share one property: they don't add servers. A paid tier buys higher usage limits, not reserved capacity — Pro and Max users hit the same wall.

For API developers: retry logic that survives 529s

The official SDKs already retry twice by default with backoff, and that covers 529s along with the rest of the 5xx family. For anything production-shaped, we layer three policies on top:

Backoff with jitter, tuned longer than for 500s. A 500 usually clears in seconds; a 529 means sustained load, so start around one second, double each attempt toward a 60-second cap, and randomize each wait ±30% so your fleet doesn't retry in synchronized waves:

for attempt in range(5):
    try:
        message = client.messages.create(...)
        break
    except anthropic.InternalServerError as e:
        delay = min(60, 2 ** attempt)
        time.sleep(delay * random.uniform(0.7, 1.3))

Bound it, then fail over. Never retry infinitely. Our rule: roughly three 529s inside a minute opens a circuit breaker and the request falls back to a lighter model or a queue. Claude Haiku 4.5 at $1/$5 per million tokens is a cheap pressure valve when Claude Opus 4.8 ($5/$25) is saturated — a degraded answer beats a spinner.

Branch on error.type, not the exception class. SDK exceptions lump every 5xx together, so inspect the type string: api_error gets the short ladder, the overloaded_error Claude returns gets the long one. Note that a 529 arrives before processing starts — if your stream dies midway through a response instead, that's a different failure with different fixes, covered in our stream idle timeout guide.

Claude Code and the 529: what the CLI already does for you

If Claude Code prints "API Error: Repeated 529 Overloaded errors," understand what already happened: per the Claude Code error reference, the CLI retries transient failures — overloaded responses included — up to 10 times with exponential backoff, showing a Retrying in Ns · attempt x/y countdown while it works. The message you finally see is the end of a patience budget, not the start of one.

Two environment variables tune that budget, and the second one transformed our CI:

The sore spot is long agentic tasks: a 529 that outlives the retry budget aborts the run, with no automatic resume of the plan in flight — a known open request on Anthropic's tracker. Our mitigations: have the agent commit or checkpoint as it goes, keep tasks cheap to re-run, and set the watchdog variable for overnight jobs. When one model is under acute load, Claude Code even prompts you to /model down a tier — take the hint.

When to check the status page — and when to just wait

Our decision rule after two years of this: one 529 is weather, ten minutes of 529s is news. A single Claude overloaded error deserves a shrug and a retry, not an investigation. Repeated failures across several minutes deserve ten seconds on status.claude.com, because genuine capacity incidents get posted there — Anthropic has publicly acknowledged capacity-driven outages, including a widely reported one attributed to "unexpected capacity constraints."

If the status page is green and the 529s keep coming, you're most likely inside a peak-hours squeeze: switch models, shift the job, or give it twenty minutes. And if what you're seeing isn't a clean 529 at all — timeouts, dead connections, nothing reaching Anthropic — you've wandered into different territory: work through our can't reach Claude error pillar, which triages connectivity failures the same way this guide triages capacity.

Claude pricing at a glance

For the full breakdown of every plan, see our how much Claude costs guide.