Claude error 529 appears when Anthropic’s servers reach capacity. In Claude Code, the terminal displays:
API Error (529 {"type":"error","error":{"type":"overloaded_error","message":"Overloaded"}})
Retrying in 1 seconds... (attempt 1/10)The error originates on Anthropic’s servers, not your machine, internet connection, or API key setup. Nothing in your local environment caused it, and nothing local will fix it.
What Is Claude Error 529 Overloaded
A 529 status code signals that Anthropic’s infrastructure temporarily rejects new connections to prevent a full system crash. Think of it like a restaurant where the kitchen is fully operational but every table is occupied. The server is running, but it cannot accept new requests at that exact moment.
Three things define a 529 error:
- Server-side origin: The problem lives entirely on Anthropic’s end
- Temporary rejection: The server “breathes” by refusing new connections for a short period to maintain stability
- No local cause: Your code, API key, and internet connection are already working fine if you received the error message at all
What Causes Claude Error 529
Peak Usage Hours
Traffic on the Claude API peaks during US business hours, particularly between 10:00 AM and 2:00 PM PST on Tuesday through Thursday. Thousands of developers calling the API simultaneously strain server capacity, and requests start getting rejected.
New Model Launches
When Anthropic releases a major model update, demand spikes sharply as everyone tests the new capabilities at once. These launch surges create capacity bottlenecks that can last several hours.
Agentic Workloads in Claude Code
Claude Code operates as an agentic tool. In a single session, it sends multiple parallel requests covering file reads, terminal commands, and log analysis. These large context windows and high request frequencies trigger 529 errors more often than the standard Claude web interface.
Claude Error 529 vs 429: What Is the Difference
These two errors look similar in the terminal but require different responses.
| Feature | Error 529 (Overloaded) | Error 429 (Rate Limit) |
|---|---|---|
| Source | Anthropic’s server | Your usage pattern |
| Meaning | “We are too busy right now” | “You are sending too fast” |
| Cause | Server-side capacity issue | You hit your plan’s rate limit |
| Fix | Wait and retry | Optimize or queue your requests |
If you see 529, stop troubleshooting your API key or network. The issue is external and outside your control.
How to Check If Claude Is Down
Before trying any workarounds, confirm the service status at status.anthropic.com.
Look for two separate entries: Claude API and Claude Code. The web chat interface sometimes stays responsive while the API struggles under load.
Status indicators:
- Green (Operational): All systems running normally
- Yellow (Partial Outage): Expect intermittent 529 errors or slower response times
- Red (Major Outage): Most requests will fail until Anthropic resolves the incident
How to Fix Claude Error 529 Overloaded
Work through these steps in order. Most 529 errors resolve at step one or two.
Step 1: Let the Automatic Retry Finish
Claude Code includes built-in retry logic. It attempts to reconnect up to 10 times using exponential backoff, waiting 1 second, then 2, then 4, doubling each time.
Wait through at least three to five attempts before doing anything else. Most 529 errors clear within 30 seconds as server capacity opens up.
Step 2: Reduce Context Size with /compact
Large context windows require more compute resources and face higher rejection rates during peak load. If you work inside a large codebase, your session context grows quickly over time.
Run this command in your Claude Code terminal:
/compactThis compresses your conversation context and makes your next request lighter, increasing the chance the server accepts it.
Step 3: Switch to a Different Model
Claude models run in separate capacity pools. When Opus is overloaded, Sonnet often has available bandwidth.
Run this command:
/model claude-sonnet-4-6Switch back to Opus after traffic normalizes.
Step 4: Avoid Peak Usage Hours
The highest 529 frequency occurs between 10 AM and 2 PM PST on weekdays. Shifting heavy tasks outside these windows significantly reduces the chance of hitting an overloaded server.
Schedule compute-intensive work before 9 AM PST or after 6 PM PST. Weekends see far fewer 529 errors than weekday peak hours.
Step 5: Monitor the Status Page for Wider Outages
If every prompt fails and none of the steps above help, a wider outage is likely in progress. Check status.anthropic.com for active incident reports. Anthropic posts estimated resolution times when incidents are confirmed.
Step 6: Skip These Local Fixes That Do Not Work
Reinstalling Claude Code, clearing browser cache, resetting your router, and flushing DNS will not resolve a 529 error. Receiving the error message already proves your local installation and internet connection are functional. The problem is at the server level, and local actions cannot reach it.
How to Prevent 529 Impact in Production Apps
Developers building on the Claude API cannot stop the server from overloading, but they can prevent it from breaking user experience.
Queue requests: Send requests through a controlled queue instead of large parallel bursts. Staggering requests reduces the chance of hitting capacity limits simultaneously.
Implement exponential backoff: Add retry logic that waits 1 second, then 2, then 4 before each retry. This matches the approach Claude Code uses internally and gives the server time to recover.
Track your 529 patterns: Log when 529 errors occur and look for time-of-day trends specific to your usage. Adjust your processing schedule to avoid those windows.
Add a fallback provider: Route requests to an alternative API such as OpenAI or Mistral when Claude returns a 529. This keeps your application available during Anthropic capacity events.
Claude API Error Code Reference
| Error Code | Category | Meaning | Recommended Action |
|---|---|---|---|
| 400 | Client | Bad Request | Check JSON formatting or missing parameters |
| 401 | Client | Authentication | Verify your API key is active and correct |
| 403 | Client | Permission | Upgrade your plan tier for restricted features |
| 404 | Client | Not Found | Check for typos in the endpoint URL |
| 413 | Client | Request Too Large | Reduce file size or prompt length (32MB limit) |
| 429 | Client | Rate Limit | Implement request queuing and reduce speed |
| 500 | Server | Internal Error | Anthropic-side glitch; retry after 60 seconds |
| 529 | Server | Overloaded | Wait it out; server is at capacity |
Frequently Asked Questions
What does Claude API error 529 mean?
Anthropic’s servers are handling more traffic than they can process at that moment. The error is temporary and clears when server capacity becomes available.
Is Claude down when I see error 529?
Not necessarily. A 529 often signals a partial outage where the server is at capacity but still operational for users already in queue. Check status.anthropic.com to confirm the scope.
How long does Claude error 529 last?
Most 529 errors clear within seconds or a few minutes. During major model launches or unexpected capacity events, they can persist for an hour or longer.
Can I fix error 529 myself?
No direct fix exists because the problem is on Anthropic’s servers. You can work around it by switching models, running /compact to reduce context size, or scheduling work outside peak hours.
What is the difference between error 529 and error 429?
Error 529 is a server-side capacity problem on Anthropic’s end. Error 429 is a rate limit triggered by your own usage pattern. They require completely different responses.
Why does Claude Code get 529 errors more often than the web interface?
Claude Code sends multiple parallel requests per session because it reads files, runs commands, and analyzes output simultaneously. This agentic workload places more demand on the API than a single chat message and increases the chance of hitting capacity limits.
Why does Claude Code get 529 errors more often than the web interface?
Claude Code sends multiple parallel requests per session because it reads files, runs commands, and analyzes output simultaneously. This agentic workload places more demand on the API than a single chat message and increases the chance of hitting capacity limits.
Claude error 529 overloaded is a server-side capacity issue that reflects high demand on Anthropic’s infrastructure. It does not indicate a problem with your code, credentials, or local setup.
When the error hits, let the automatic retry run first. If it persists, switch to Claude Sonnet with /model claude-sonnet-4-6, use /compact to trim your context, and shift heavy work to off-peak hours. For production systems, pairing exponential backoff with a fallback provider gives the most reliable protection against Anthropic capacity events disrupting your users.
