Cursor "Too many requests": causes and fixes (request limit / rate limit)
Is there an outage right now?
Cursor official status is operational. If this error persists, it is likely an implementation or environment issue on your side.
View Cursor status →What this error means
You hit Cursor's request limit — typically the monthly fast/premium request quota, a short burst, or model congestion.
Common causes
- •Monthly fast-request quota exceeded (Free/Pro)
- •Too many requests in a short time
- •Congestion on the target model
- •Subscription issue (e.g. not renewed)
- •Temporary Cursor-side outage
How to fix
- 1.Switch to slow requests or wait a bit
- 2.Upgrade to Pro / usage-based pricing
- 3.Switch to a lighter model
- 4.Use it at a different time
- 5.Check Cursor-side status at the top of this page
When waiting helps (and when it won't)
Monthly quota clears at reset — wait or upgrade. If congestion, it improves over time.
Alternatives when Cursor is down
Related errors
FAQ
What is Too many requests / rate limit?
You hit Cursor's request limit — typically the monthly fast/premium request quota, a short burst, or model congestion.
How do I fix Too many requests / rate limit?
Switch to slow requests or wait a bit / Upgrade to Pro / usage-based pricing / Switch to a lighter model / Use it at a different time / Check Cursor-side status at the top of this page