Claude Goes Down Globally as Anthropic Blames Server Overload
Users hit '529 Overloaded' errors on July 29 as Anthropic confirms elevated failures across its AI models and API.
Key points
- Anthropic confirmed a global outage of its Claude AI assistant starting 7:49 p.m. UTC on July 29, 2025.
- Users saw an 'API Error: 529 Overloaded' message, meaning Claude's servers could not handle the volume of requests.
- Anthropic said at 8:33 p.m. UTC that it had identified the cause but did not share a fix time.
- The failure hit both the Claude chat product and third-party apps that call Claude through its API, the software bridge that lets other programs talk to Claude.
Anthropic's Claude chatbot went offline for users around the world on Tuesday evening, with the company confirming raised error rates across several of its AI models.
The outage started at 7:49 p.m. UTC on July 29, according to Anthropic's own status updates. Requests failed with a blunt message: 'API Error: 529 Overloaded. This is a server-side issue, usually temporary, try again in a moment.' BleepingComputer staff hit the same error repeatedly during testing.
By 8:33 p.m. UTC, Anthropic said it had identified the root cause and was working on a fix. No cause was given. No recovery timeline followed.
What is a '529 Overloaded' error?
It's Claude's way of saying its servers are swamped: too many requests arriving at once, with the system turning some away rather than collapsing entirely. Everyday users found Claude refusing to answer or cutting off mid-response. Businesses felt it further.
Why does this matter beyond the chat window?
Claude doesn't just power its own app. A growing number of companies build products on top of Claude's API, the connection that lets outside software send questions to Claude and receive answers. Customer support bots, internal search tools, and coding assistants all run through that pipe. Our June story on security protocols for SMBs adopting Claude noted how tightly some smaller businesses have wired Claude into daily operations, which makes an outage like this harder to absorb than it might look from the outside.
When the API returns 529s, every downstream product returns errors too. A small business using a Claude-powered helpdesk tool would've seen its assistant go silent with no obvious explanation.
Timeline of the outage
| Time (UTC) | Event |
|---|---|
| 7:49 p.m., July 29 | Anthropic begins investigating elevated errors |
| Shortly after | Users report '529 Overloaded' failures worldwide |
| 8:33 p.m., July 29 | Anthropic says root cause identified, fix in progress |
| Not disclosed | Full recovery time |
Should users be worried about their data?
No, not based on what Anthropic has said. A 529 error is a capacity problem, not a breach. Nothing in Anthropic's statements suggests anyone accessed conversations or interfered with the models. This is an availability issue: the service couldn't be reached, not compromised.
That said, outages at AI providers are worth tracking carefully. More companies are wiring critical workflows into a handful of large model providers. When one stumbles, the ripple travels well beyond its own front door.
Common questions
Is Claude working again now?
Anthropic said it had identified the cause and was applying a fix. Users should check Anthropic's status page for the latest before assuming full recovery.
Do I need to change my password?
No. This was a capacity outage, not a hack. There's no security action for regular users to take.
What can businesses relying on the Claude API do during outages like this?
Build in a fallback. Route traffic to a second model provider or show users a clear holding message rather than a raw error code.
