[BUG] Rate limit 429 errors despite dashboard showing available quota - Two Max accounts, documented inconsistencies

Open 💬 11 comments Opened Feb 3, 2026 by C0dino

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?

Receiving persistent HTTP 429 rate limit errors while the dashboard shows available quota on multiple metrics.
Account: [thesage2412@gmail.com](mailto:thesage2412@gmail.com) (Max $100/month)
At time of 429 errors, dashboard showed:

Current session: 72% used (not 100%)
Weekly limits: 6% used (not 100%)
Claude Code: 0% used (not 100%)

Yet API returned:
HTTP 429: rate_limit_error: This request would exceed your account's rate limit.
Paradoxically, I could use claude.ai web interface on the same account while API returned 429s.
Request IDs demonstrating the issue:
req_011CXmMeQYEgck2Xmq78hGEw
req_011CXmS53VctxC2L8gCV1sjG
req_011CXmbcu6Xxi8WyYRtNkLDp
req_011CXmcB77V8XH8BoTcatsZd
req_011CXjjPpsr44MDCs6XAhpba
req_011CXjjRvsJzZrvBifd7bU7X
req_011CXjjTzWtjSDSjAyNzxQcc
req_011CXjjVz6u3AcrRKapZTeY5

What Should Happen?

What Should Happen?

If dashboard shows available quota (session, weekly, Claude Code all below 100%), API should not return 429
All rate limits that can trigger 429s should be visible in the dashboard
Rate limiting behavior should be consistent and predictable

Error Messages/Logs

HTTP 429: rate_limit_error: This request would exceed your account's rate limit. Please try again later. (request_id: req_011CXmbcu6Xxi8WyYRtNkLDp)

HTTP 429: rate_limit_error: This request would exceed your account's rate limit. Please try again later. (request_id: req_011CXmcB77V8XH8BoTcatsZd)

Also experienced 500 errors during the same debugging session:
API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"req_011CXmPE58F6DVFELUrLQGBY"}

Steps to Reproduce

Steps to Reproduce

Subscribe to Claude Max ($100 or $200 plan)
Use Claude Code or API via OAuth authentication
Send messages until session usage reaches ~70%
Observe dashboard showing available quota on all metrics
Continue sending messages
Receive 429 errors despite dashboard showing available capacity
Attempt same account on claude.ai web interface - works fine
Return to API/Claude Code - still 429

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

Unknown - I've only recently started using Max at this intensity. Other users report this started January 2026.

Claude Code Version

2.1.29 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Financial Impact
I spent ~$160 today trying to diagnose what I believed was a configuration issue:

~$40 in extra usage burned on primary account
$20 for new Pro subscription
$100 upgrade to Max on second account (*Pro Rated to $80 because it was an upgrade)

Two Accounts Affected
Account 1 ([spendino@gmail.com](mailto:spendino@gmail.com) - Max $200):

Weekly: 100% used
Session: 0% used
Extra usage: $33.93 spent, $11.06 remaining
Burned through extra usage rapidly (possibly related to #22297 infinite loop bug which may have burned this all in the first place spawning claude code sessions via the agent)

Account 2 ([thesage2412@gmail.com](mailto:thesage2412@gmail.com) - Max $100):

Weekly: 6% used
Session: 72% used
Getting 429s despite available quota

Related Issues

#22297 - /rate-limit-options infinite loop bug
#22435 - Inconsistent quota accounting on Max plan
#22439 - Usage limit reached despite available quota
#17084 - Opus 4.5 limits reduced since January 2026

Use Case
I run an AI agent via OpenClaw gateway using Claude Code OAuth. The agent performs legitimate work (meeting analysis, document processing). The rate limiting inconsistencies make it impossible to predict or budget actual usage.
Request

Refund for extra usage charges incurred debugging platform inconsistencies
Transparency on hidden rate limits not shown in dashboard
Dashboard fix to display ALL limits that can trigger 429s

Notes:
Using the sage account I can still talk to Claude Opus 4.5 with no issues.,. yet through openclaw i get 429s?; Opus helped write this with appropriate context from debugging it in the first place

View original on GitHub ↗

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