If Claude's chat suddenly stops responding or shows a "529" error, it's usually not a problem with your account — it means Claude's servers are temporarily overloaded with more requests than they can handle right now. Working through the steps below usually gets you back to a normal conversation within a few minutes.
🟢 Model references match the current lineup · model notice · Fable subscription
Fable 5 and 5.1 subscription (updated September 7, 2026): Claude Fable 5.1, released September 1, 2026, is the current Fable model and Fable 5 is now legacy. Plan terms are the same for both — Max and Team Premium plans include Fable at up to 50% of the weekly usage limit; Pro and Team Standard use usage credits (
Before you start
This guide needs no installation or special setup — it's meant to be followed the moment you hit the error. All you need is an active claude.ai session (web or app) and an internet connection.
- 529 — a standard HTTP status code servers use across the web to say "I can't handle your request right now." It's not unique to Claude; many online services use the same number.
- Overloaded error (overloaded_error) — the name Claude's official API documentation gives to a 529 response: the server is getting more requests than it can currently process.
- status.claude.com — Anthropic's official status page showing whether claude.ai, the apps, and the API are currently operating normally, plus any ongoing incidents.
Why does the 529 error happen?
A 529 error appears when a surge of requests hits Claude's servers all at once and temporarily exceeds what they can process. Anthropic's API documentation states that "529 errors can occur when the API experiences high traffic across all users" — meaning it's tied to overall demand across everyone using Claude, not to how much you personally have used.
The number 529 itself is the response code developers see when they call Claude's API directly. Since claude.ai's web app and the mobile/desktop apps ultimately run on the same backend, a server-side overload can affect the chat interface too. That said, whether the chat screen shows the literal number "529" or a plain-language message like "unable to respond right now" can vary by client version and over time, so this guide doesn't assert one exact wording. Treat whatever message actually appears on your screen as the accurate one.
What to do right now
The first thing to try is simply waiting a moment and refreshing. Use the steps below alongside the diagram above.
- Wait a moment — give it 30 seconds to a minute before trying again. Server overloads usually clear quickly.
- Refresh the page or start a new chat — on the web, refresh the page; in the app, open a new conversation and send your message again.
- Check status.claude.com — status.claude.com shows the current status of claude.ai, the apps, and the API, along with any active incidents. If an incident is listed as "Investigating" or "Identified," waiting until it's marked "Resolved" is the most reliable approach.
- Retry later, outside peak hours — trying again after busy periods (commonly understood to include US business hours) can help. Official documentation doesn't specify exact peak times, though, so treat this as a rough guideline.
Watch out — repeatedly refreshing and resending requests in quick succession can add to server load or trigger a different error. Space out your retries by a few seconds at least.
When it appears in Claude Code
If you see the message below in the terminal or on the mobile remote screen while using Claude Code, it is the same overload (as of the September 2026 official docs).
API Error: 529 Overloaded. This is a server-side issue, usually temporary — try again in a moment. If it persists, check https://status.claude.com.Claude Code shows the status code and the API message as-is for any 5xx response, retries automatically (10 attempts by default) with a Retrying in Ns · attempt x/y countdown, and if that still fails the wording changes to API Error: Repeated 529 Overloaded errors. A 529 is not your usage limit and does not count against your quota.
- Check the status page — look for capacity notices at status.claude.com (on Bedrock, Vertex or a gateway, the message names that provider's status page instead).
- Try again in a few minutes — your message is still in the conversation, so you can type
try againinstead of pasting a long prompt again. - Switch models with
/model— capacity is tracked per model, so moving to another model lets you keep working. Claude Code may prompt this itself, e.g. "Opus is experiencing high load, please use /model to switch to Sonnet". - If it persists with no posted incident — run
/feedbackso the request details can be investigated.
In unattended sessions such as CI, set CLAUDE_CODE_RETRY_WATCHDOG=1 to keep retrying 429/529 capacity errors instead of failing (v2.1.199 or later).
How is 529 different from other errors?
529 is a server-wide overload, while 429 is specific to your own account's usage limit — the two are not the same problem. Here's how they compare.
| 529 overloaded error | 429 usage limit error | Internet/connection issue | |
|---|---|---|---|
| Cause | Traffic across all of Claude's servers temporarily exceeds capacity | Your account (or organization) has reached its usage/request limit | Your device's network connection is down or unstable |
| Related to your usage? | No — affects everyone using Claude at once | Yes — caused by using up your own account's limit | No — a device/network issue |
| What to do | Wait, refresh, check status.claude.com | Check your plan's usage limits and wait for them to reset | Check Wi-Fi/data connection, restart your device |
If it keeps happening
If 529 errors show up repeatedly rather than once or twice, it's worth checking for causes beyond a simple server overload.
- Confirm your internet connection isn't dropping or slow — try loading another site to test.
- If you're on a browser, try an incognito/private window to rule out extensions or cached data as the cause.
- If you're on the app, make sure it's updated to the latest version, and reinstall if needed.
- Check status.claude.com for an active incident. If one is listed, waiting for it to be marked "Resolved" is the most reliable fix.
- If the error message mentions a "usage limit" rather than overload, that's a separate issue — check your plan's usage limits instead.
- If the problem persists after all of the above, contact support through support.claude.com.
Frequently asked questions
Q. Does a 529 error mean something is wrong with my account?
No. According to official documentation, 529 occurs when Claude's servers experience high traffic across all users, and it isn't tied to any individual account's usage.
Q. How is 529 different from a 429 (usage limit) error?
529 is a server-side overload; 429 happens when your account or organization hits its own usage limit. The comparison table above breaks down the difference.
Q. How long should I wait before trying again?
Official documentation doesn't specify an exact wait time. Waiting briefly, refreshing, and checking status.claude.com is the safest approach.
Q. Do paid plans (Pro/Max) avoid 529 errors?
Official documentation doesn't state that 529 occurrence differs by plan. It's most accurate to treat 529 as tied to overall server load rather than any per-account limit.
Next steps
If you're building on Claude's API directly, this site's article on Claude API errors and retry strategies covers how to make your code automatically retry on 529 and 429 responses — that article is written for developers calling the API, while this one focuses on what chat users see in the web and app interfaces. Bookmarking status.claude.com makes it quicker to check the next time something similar happens.
Related articles
- Troubleshooting Claude Error Messages: Limits, Capacity, Login
- Fix "Your Previous Message Wasn't Sent" in Claude — Causes & Steps (2026)
- Claude "Something Went Wrong" Error: How to Fix It
- Claude "Your previous response is still processing" error: cause and fix
- Claude Not Working? Fix Login, Access & Errors (2026)