Model 529 api proxy

Claude Code API Error: 529 Overloaded

A 529 means the Anthropic API is temporarily overloaded. Check Claude Status first; during an active incident, wait for recovery or temporarily switch models instead of retrying continuously.

Snapshot

For API Error: 529 Overloaded, check status.claude.com, then wait, reduce concurrency, or switch models. Anthropic has not linked the Opus 5 incident to the alleged German payment loophole.

#api error 529 overloaded #claude code 529 overloaded #opus 5 529 overloaded #claude service is busy #claude server overloaded #claude code service busy

Claude Code or Opus 5 shows:

Service is busy
Try again in a moment, or switch to a different model.

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.

What This Error Means

Anthropic defines 529 as overloaded_error: the API is temporarily overloaded because of high traffic across users.

Was This an Opus 5 Incident?

Yes. On July 26, 2026, Claude Status recorded Elevated errors for Opus 5 with major impact and marked the incident resolved later that day. LINUX DO users also reported the same API Error: 529 Overloaded during this and earlier service disruptions.

For a 529 seen on another date, check the incident status at that time on Claude Status. A resolved historical incident does not explain every later error.

How To Fix It

Open Claude Status and check for an active Opus 5, Claude Code, or Claude API incident.
During an active incident, stop clicking Try again continuously. Wait a few minutes, or temporarily switch to a model that is operating normally.
For direct API integrations, use exponential backoff with a retry limit. Anthropic’s official SDKs retry transient connection, rate-limit, and 5xx failures a limited number of times by default.
If only your sessions keep failing, close extra Claude Code windows, reduce concurrency, and test with one short request.
If the status page is clear but the error persists, separate direct Anthropic access from an API proxy. Keep the request_id for Anthropic support, or ask the proxy provider to check its upstream model pool and error passthrough.

Did the Alleged German Payment Loophole Cause It?

There is not enough evidence to make that claim. Community screenshots and posts alleged that asynchronous German SEPA Direct Debit settlement could become out of sync with subscription entitlement, allowing some accounts to receive Max access before payment was finally confirmed. That mechanism could create a window where access is active while a payment remains pending or later becomes overdue.

Those screenshots do not establish how many accounts were involved, whether payments settled, or how much platform load they generated. Even if abnormal sign-ups added traffic, they could only be described as a possible contributor. As of July 26, 2026, Anthropic had confirmed elevated Opus 5 errors and a subsequent fix, but had not attributed the incident to SEPA payments or abnormal registrations.

FAQ

Common questions

How long does a Claude Code 529 usually last?

There is no fixed recovery time. Follow the incident on Claude Status and retry after Anthropic marks it resolved.

Should I keep clicking Try again when Opus 5 returns 529?

No. Wait a few minutes and use bounded retries with backoff. If the task is urgent, temporarily switch to a model that is operating normally.

Was the 529 caused by the alleged German SEPA payment loophole?

As of July 26, 2026, Anthropic had not confirmed the alleged loophole's scale or linked it to the Opus 5 incident. The claim remains an unverified community theory.