api Errors: 500
Status Fixed / completed
Reported on v2.1.31
Maintainer reply None cached
Activity 15 comments · opened Feb 4, 2026 · closed Feb 25, 2026
Bug Description
api Errors: 500
Environment Info
- Platform: darwin
- Terminal: vscode
- Version: 2.1.31
- Feedback ID: b2536bd6-a168-4f32-9b4d-0a6ce4b68b89
Errors
[{"error":"Error: 500 {\"type\":\"error\",\"error\":{\"type\":\"api_error\",\"message\":\"Internal server error\"},\"request_id\":\"req_011CXoMmGPJThuHdzpauejXn\"}\n at generate (/$bunfs/root/claude:344:8942)\n at makeRequest (/$bunfs/root/claude:361:5435)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-04T16:39:25.729Z"},{"error":"SyntaxError: JSON Parse error: Unexpected identifier \"API\"\n at <parse> (:0)\n at parse (unknown)\n at <anonymous> (/$bunfs/root/claude:70:855)\n at A (/$bunfs/root/claude:11:7248)\n at sX_ (/$bunfs/root/claude:761:91950)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-04T16:39:25.729Z"},{"error":"Error: 500 {\"type\":\"error\",\"error\":{\"type\":\"api_error\",\"message\":\"Internal server error\"},\"request_id\":\"req_011CXoMrYpABx8qaTBUwrfDt\"}\n at generate (/$bunfs/root/claude:344:8942)\n at makeRequest (/$bunfs/root/claude:361:5435)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-04T16:40:37.197Z"},{"error":"Error: 500 {\"type\":\"error\",\"error\":{\"type\":\"api_error\",\"message\":\"Internal server error\"},\"request_id\":\"req_011CXoN2qbjhzqttjWZcuYV5\"}\n at generate (/$bunfs/root/claude:344:8942)\n at makeRequest (/$bunfs/root/claude:361:5435)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-04T16:42:52.691Z"},{"error":"Error: 500 {\"type\":\"error\",\"error\":{\"type\":\"api_error\",\"message\":\"Internal server error\"},\"request_id\":\"req_011CXoN4wCe2AcZkzzmVopae\"}\n at generate (/$bunfs/root/claude:344:8942)\n at makeRequest (/$bunfs/root/claude:361:5435)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-04T16:43:21.761Z"}]
15 Comments
Claude is down again.
https://status.claude.com/
I think this is happening again
I am getting a API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server
error"},"request_id":"req_011CXz5EneXnD6UhiQChAcR7"} in code and errors on the web. The status page claude is up and running without issues. I tried logging out, logging in, switching IPs, connecting via VPN, I tried using different browsers. I also tried switching between wsl, command line and powershell. I am on a windows machine.
This has been ongoing for 24# hrs
I am now on a colleagues account, which works. So another sign that there is some server error somewhere and all accounts connected to it are breaking.
Mine was fine again on the same day I have reported the problem. Have to check today again
Are you anywhere near frankfurt by chance? Though it is probably a round-robbin association of the account and the server, my guess is that we are probably in a cluster somehow.
Could be my cluster. I am in the south of Austria
<img width="961" height="236" alt="Image" src="https://github.com/user-attachments/assets/e7b72a94-ede0-4b86-9486-e0f8609c2a1c" />
still problems...
Same
I just tried contacting them over X as well: https://x.com/madppiper/status/2021480414033092774?s=46
and through every other channel imaginable. This is really rough. I had to upgrade my colleagues account to max plan to make up for me wasting all of her pro tokens this morning -> 150USD down the drain
3rd day
5th day. No response on ANY channel...
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.