[BUG] 529 overloaded errors causing full-day productivity loss (2026-03-17)

Resolved 💬 5 comments Opened Mar 17, 2026 by KI7MT Closed Apr 16, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Summary

Persistent 529 overloaded errors throughout 2026-03-17 made Claude Code effectively unusable for extended periods. Multiple agents/sessions affected across different hosts.

What Should Happen?

## Environment

  • Claude Code CLI (Max plan)
  • Two hosts: Mac Studio M3 Ultra (macOS) and Threadripper 9975WX (Rocky Linux 9.7)
  • Multiple concurrent sessions experiencing the same issue

## Impact

  • Full working day lost — unable to complete planned development work
  • Mid-response failures requiring repeated restarts
  • Affected both interactive coding sessions and MCP server development

## Example Error

529 {"type":"error","error":{"type":"overloaded_error","message":"Overloaded. https://docs.claude.com/en/api/errors"},"request_id":"req_011CZ9PSW1MDS8ct2QHyHhNL"}

## Request

As a paying Max customer actively building production systems with Claude Code (14 MCP servers, multi-agent workflows, preparing for CCA certification), reliable availability is critical. I'd rather help improve the platform than complain — but today was a full loss.

Would appreciate:

  1. Visibility into known capacity issues or maintenance windows
  2. A status page or incident feed we can monitor
  3. Consideration of SLA commitments for paying tiers

Error Messages/Logs

Steps to Reproduce

Hard to say, varies on the day/time.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.77

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗