[BUG] API Error 500 on all prompts including /feedback command - Sonnet 4.5 and Opus 4.5
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?
Claude Code CLI returns API Error 500 on every single prompt, including system commands like /feedback. Complete inability to use Claude Code.
Error message:
API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"req_011CXmP4Qsci57hDQdqh3MLp"}
Additional request IDs:
- req_011CXmPt4mUMXok6C4NZMFgG (when trying /feedback command)
What Should Happen?
Claude Code should accept prompts and execute commands normally. The /feedback command should open a feedback form.
Bug Description
API Error 500 on ALL prompts including /feedback command
Error:
API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"req_011CXmP4Qsci57hDQdqh3MLp"}
Environment:
- Platform: Windows
- Terminal: PowerShell
- Version: 2.1.29
- Model: claude-opus-4-5 (Sonnet 4.5 also fails)
- Date: February 3, 2026, ~12:00 PM Mexico City time
What I tried:
- claude update → already on latest (2.1.29)
- claude auth logout/login → tried 2 times
- Restarted Claude Code multiple times
- Even
claude feedbackcommand returns 500 error
Usage limits checked:
- Current week (Sonnet): 3% used ✓
- Have available quota ✓
Impact:
Complete inability to use Claude Code CLI. Cannot send feedback, cannot execute any prompts.
Related issues:
Similar reports: #20177, #21443, #19166, #21445
Error Messages/Logs
API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"req_011CXmP4Qsci57hDQdqh3MLp"}
API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"req_011CXmPt4mUMXok6C4NZMFgG"}
Steps to Reproduce
- Open PowerShell terminal
- Navigate to project directory: C:\Users\abela\prweb\web26-602-shopify-woocommerce-link
- Run: claude
- Type any prompt (e.g., "hello")
- Observe API Error 500
- Try: /feedback
- Observe same API Error 500
Note: Issue persists after:
- Running claude auth logout/login (tried 2 times)
- Restarting terminal multiple times
- Closing and reopening Claude Code
- Verifying latest version with claude update
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
until February 3, 2026 around 940 AM Mexico City time
Claude Code Version
2.1.29
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
- Verified usage limits: Only 3% Sonnet usage for the week - well under limits
- Located in San Luis Potosí, Mexico
- Issue started suddenly on Feb 3, 2026
- claude.ai web interface works normally
- Related issues: #20177 (20 users affected), #21443, #19166, #21445
This appears to be a server-side issue affecting multiple users simultaneously.
5 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
✅ RESOLVED
The issue has been fixed on Anthropic's side. Claude Code CLI is working normally again.
Thanks @anthropics team for the quick fix! 🙏
🚨 ISSUE RETURNED - Feb 4, 2026
The same API Error 500 started again today at 10:30 AM Mexico City time.
Same symptoms:
This appears to be a recurring issue. Yesterday's fix was temporary.
New request_ids:
Error message:
API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"req_011CXoMqN7TPun5zFSHQpPuC"}
✅ RESOLVED AGAIN - Feb 4, 2026
Issue resolved at 11:00 AM Mexico City time.
Time to resolution: ~30 minutes from when it started (10:30 AM)
⚠️ IMPORTANT: This is now a RECURRING pattern
Root cause appears unresolved. This may return again.
@anthropics team: Please investigate the underlying infrastructure issue to prevent future recurrences.
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.