API Error 500: Internal server error affecting all chats simultaneously (Claude Max)
Status Fixed / completed
Reported on v2.1.38
Maintainer reply None cached
Activity 5 comments · opened Feb 10, 2026 · closed Feb 25, 2026
Bug Description
Persistent API 500 Internal Server Error affecting all chats and terminals simultaneously.
API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"req_011CY14wgpph7Qvc838Fmtvm"}
Environment
- Platform: macOS
- Subscription: Claude Max ($200/month)
- Claude Code version: 2.1.38 (latest)
- Issue started: February 10, 2026, ~15:00 CET
Behavior
- Error occurs on ALL chats/terminals simultaneously
- Was working seconds before the error started
- Restarting terminal doesn't fix it
- Affects all conversations, not just one
- Updated Claude Code to latest version (2.1.38) — issue persists
Request IDs
req_011CY14wgpph7Qvc838Fmtvm
Additional Context
Multiple terminals with different conversations all failed at the same time. A clean update to the latest CLI version did not resolve the issue. This appears to be a server-side issue affecting all API calls for the account simultaneously.
5 Comments
I switched to /model sonnet and working so far, its opus model thats having issues
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
same to me, switching to other modes not working, no model working for me.
Hi folks, thanks for reporting this. These 500 errors were caused by transient API outages on the Anthropic side — not a bug in Claude Code itself. The API is currently healthy, so I'm closing this out. If you're still experiencing 500 errors, you can check the API status at https://status.anthropic.com, and if the issue persists while the status page is green, please open a new issue with your request ID and we'll investigate.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.