[Bug] Rate limit exceeded despite low session usage percentage
Resolved 💬 16 comments Opened Mar 28, 2026 by anbu369 Closed May 10, 2026
Bug Description
My usage says I've used only 7% of my 5 hour session and 8% of my 1 week session but I keep getting Rate limit reached for the past hour
Environment Info
- Platform: darwin
- Terminal: iTerm.app
- Version: 2.1.86
- Feedback ID: 0be7c8d2-3441-4a17-ba01-80ea6ba4903d
Errors
[{"error":"Error: 429 {\"type\":\"error\",\"error\":{\"type\":\"rate_limit_error\",\"message\":\"Rate limited\"},\"request_id\":\"req_011CZUhacp1t8vHvxzSDCAx2\"}\n at generate (/$bunfs/root/src/entrypoints/cli.js:11:51105)\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:5435)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-03-28T02:36:52.477Z"},{"error":"Error: 429 {\"type\":\"error\",\"error\":{\"type\":\"rate_limit_error\",\"message\":\"Rate limited\"},\"request_id\":\"req_011CZUhxK7GMuA5ekdB2uXyQ\"}\n at generate (/$bunfs/root/src/entrypoints/cli.js:11:51105)\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:5435)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-03-28T02:41:47.975Z"}]
16 Comments
same, but it charged me and is still charging me extra usage instead of using my actual plan
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I'm getting this as well.
Had the same issue, I solved it by switching a model, ("/model" then I pressed enter) I switched to the recommended Sonnet model by typing "/Model" then enter, it let me pick the model, I pressed enter on Sonnet and Claude got back to working.
I then wrote "/Model" again and switched back to Opus 4.6 and it was working, no more the API error.
That didn't solve it for me.
@andrewroth mine overcharged me on extra usage beyond my cieling. I had to raise my ceiling and then turn extra usage off before it would work. Not sure if that applies for you
Thanks for the heads up -- it did in fact charge me extra usage even though I'm well under all usage limits.
<img width="962" height="454" alt="Image" src="https://github.com/user-attachments/assets/fc9d1d34-9948-4222-80ba-f8625d7da69a" />
I've turned off extra usage for now.
I did use some legitimate extra usage yesterday, but I assumed it would jump back to my usual usage and not keep burning extra usage once the limits went down. In fact, I know I did more development with claude code that didn't use extra usage. But right now the extra usage spent is definitely higher than yesterday and I'm 100% sure I never went over any limits.
@andrewroth yea, mine had a ceiling of $50, it charged me $57.44. I had to pay off the $7.44, set my ceiling to $58, turn extra usage off and then switch the model. This also seems to be a machine specific issue. Between my mac, my home pc, and my work pc, only my mac was affected - its the one I do the most on anyway
No errors since -- This was of the extra usage that claude gifted me, and it's not a lot that it used. But it still leaves me a bit unnerved that this anthropic bug decided to use extra usage when it wasn't necessary. Really, the proper thing would be for anthropic to own up and refund the extra credit balance this bug stole. But since it's not much, and I can keep working now, I'll probably let it go.
I spoke too soon -- " API Error: Rate limit reached" is back.
Could you please clarify this situation? My 5-hour quota was exhausted entirely in just 10 to 15 minor prompts, processing a maximum of 2,000 lines of code. Correspondingly, my weekly quota usage has already reached 13%.
<img width="943" height="411" alt="Image" src="https://github.com/user-attachments/assets/17eadb8e-5885-42e2-ae9d-cae59d62fc6f" />
Furthermore, the following error has been occurring continuously throughout the day: API Error: Request rejected (429) · Rate limited.
For me, 01/04/2026, this morning: rate limit 100% exhausted in ~50 minutes. I waited 4 hours and the rate limit was 100% exhausted again with a single prompt.
A user in #40584 may have found the root cause for your rate limit issue. Two findings:
See #40584 for the full analysis with log evidence from two independent occurrences.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
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.