[BUG] Intermittent API Error 500 during runs (Feb 2026, Opus 4.6)
Status Fixed / completed
Reported on v2.1.45
Maintainer reply None cached
Workaround ✓ Mentioned in description ↑
Activity 9 comments · opened Feb 22, 2026 · closed Feb 22, 2026
Bug Report
Description
Intermittent API 500 Internal Server Errors occurring during Claude Code sessions. The errors appear during normal usage runs and disrupt workflow.
Error Details
{
"type": "error",
"error": {
"type": "api_error",
"message": "Internal server error"
},
"request_id": "req_011CYPhsh4jvvwHEaPRuvLm5"
}
Environment
- Claude Code version: 2.1.45
- Platform: macOS (Darwin 25.3.0, Apple Silicon)
- Shell: zsh
- Provider: Anthropic API (direct, not Bedrock)
- Model: Opus 4.6 (
claude-opus-4-6) — default, noANTHROPIC_MODELoverride - Auth: OAuth
- Date of occurrence: February 22, 2026
Steps to Reproduce
- Start a Claude Code session with default Opus 4.6 model via Anthropic API
- Use normally (tool calls, multi-step tasks, subagent usage)
- 500 errors appear intermittently during runs
What I've Ruled Out
- Not a model misconfiguration — using default Opus 4.6, no custom model env vars set
- Not Bedrock-related — running on direct Anthropic API (
CLAUDE_CODE_USE_BEDROCKis not set) - Not context-related — errors occur at various context sizes, including early in sessions
- Not network-related — other HTTPS traffic works fine; claude.ai web works simultaneously
Possibly Related
- There is an ongoing incident on status.claude.com from Feb 18, 2026 ("Intermittent errors in skills-related functionality") still in "Investigating" status as of Feb 22
- Multiple similar 500 error reports filed in February 2026: #22838, #22841, #23120, #16569
- Elevated errors on Sonnet 4.5 were reported and resolved on Feb 20
Expected Behavior
API requests should succeed or return actionable error messages (rate limit, context too large, etc.) — not opaque 500s.
Actual Behavior
Opaque 500 Internal Server Error with no actionable information for the user. Sessions are disrupted and the only workaround is to wait and retry.
9 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Closing as duplicate — likely related to the ongoing Feb 18 incident on status.claude.com. See also: #27579, #27635, #27704.
still happening today
got hit with it just now too
happening to me right now. any solution ?
Lots of this now!
Pretty much every other request for me now
Same. Claude code is unusable now.
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.