Home / Guides / Cursor Rate Limits
Cursor “Rate Limited by Model Provider”: What It Means
It means the model you picked is at capacity at the company that serves it, not that your Cursor plan ran out. Cursor retries automatically. To get unblocked now, switch to Auto or another model in the model picker; the error usually clears on its own within minutes.
Checked 17 October 2026 against Cursor staff answers on forum.cursor.com and Cursor's pricing docs · By Soren Starck
On Windows? Cursor usage on Windows: a native app for Windows 10 and 11, with alerts before you hit a limit.
Is it wider than one model? Cursor's own status, right now:
Cursor is up
Cursor reports no problem with Cursor right now.
- IDEOperational
- CLIOperational
- Cloud AgentsOperational
- cursor.comOperational
If Cursor has stopped working for you anyway, the cause is almost certainly your own usage limit, not Cursor.
Source: status.cursor.com, Cursor’s official status page. Refreshes every minute while this page is open.
What to do, in order
- Switch model. Pick Auto or a model from a different provider. Cursor staff describe this as the way to get unblocked right away.
- Wait a few minutes. Capacity limits at a provider are usually short, and Cursor keeps retrying for you.
- Check the panel above. If Cursor has an open incident naming a model or provider, the fix is on their side.
- Only then look at your usage. A provider rate limit is not your plan. On the new plans, your remaining usage and next reset are in your editor settings and under Usage at grok.com/dashboard; on a legacy plan, look at the Spending tab of cursor.com/dashboard (where it was when we last checked, on 3 October).
One pattern worth knowing: if Auto keeps routing to a provider that is struggling, every retry can hit the same busy endpoint. Picking a specific model from another provider breaks the loop.
How Cursor limits work now
Cursor no longer counts “fast requests” and no longer has a slow mode. Each paid plan now includes a weekly pool of usage for Cursor models, shared with Grok (Plus $8, Premium $30, Super $100, Ultra $200 a month; Teams $30, $100 or $200 per seat). When it runs out you wait for the weekly reset, pay with prepaid credit, or upgrade. Legacy plans (Pro, Pro+, the old Ultra, Start, Teams Standard and Premium) keep monthly usage and use on-demand usage instead of top-ups. Cursor's docs say requests are never downgraded in quality or speed.
So there are two different things people call a Cursor rate limit. A provider rate limit is temporary, affects one model, and costs you minutes. Running through your included usage affects every model, lasts until your weekly pool refreshes (on a legacy plan, until the billing cycle resets), and costs money only if you pay past it with prepaid credit or on-demand usage. Full prices are in our Cursor pricing guide.
| Provider rate limit | Included usage used up | |
|---|---|---|
| What you see | “Rate limited by model provider”, retries | The weekly pool running out in your editor settings |
| Affects | One model or provider | Every model on your plan |
| Lasts | Usually minutes | Until the weekly reset (legacy plans: the billing cycle) |
| Fix | Switch model, or wait | Prepaid credit (legacy plans: on-demand usage), or upgrade |
What changed
Older Cursor Pro plans included 500 “fast requests” a month and dropped you into a slower queue after that. A lot of advice still describes that model. It is gone: plans now include a weekly pool of model usage, and faster variants of some models (“fast mode”) cost more per token, mostly twice the standard rate.
SessionWatcher
See your Cursor spend before the bill does.
Native app for the Mac menu bar and the Windows taskbar. Track Claude, Codex and 20 more tools' usage, costs, and rate limits in real time.
“Fast, simple, and does exactly what it should. Definitely worth it.”
@nicojerome on GitHub
macOS 14+. Free for 7 days, no credit card.
Keep your Cursor usage in view
SessionWatcher for Cursor is a native app for the Mac menu bar and the Windows taskbar. On a legacy Cursor plan it keeps (support for the new weekly pool is being checked):
- Spend and remaining budget for the current cycle, without opening the dashboard
- Usage pace, so you know whether today is light, normal or running hot
- A 7-day history and a model breakdown
- Notifications at 70% and 90% by default
Frequently asked questions
What does "rate limited by model provider" mean in Cursor?
The model you picked is at capacity at the company that serves it, so Cursor is being throttled upstream and retries your request. It is not your Cursor plan running out and not something in your setup. Switching to Auto or another model in the model picker usually unblocks you at once, and the error normally clears on its own within minutes.
Did I hit my Cursor usage limit?
Probably not, if the message names the model provider. On Cursor's new plans each paid plan has a weekly pool of usage shared with Grok; when it runs out you wait for the weekly reset, pay with prepaid credit, or upgrade, and Cursor says requests are never downgraded in quality or speed. Your remaining usage and next reset are in your editor settings and under Usage at grok.com/dashboard. Legacy plans keep monthly usage and use on-demand usage instead of top-ups; their usage was on the Spending tab of cursor.com/dashboard when we last checked, on 3 October.
Does Cursor still have 500 fast requests and slow mode?
No. That was the older Pro plan. On the new plans (Plus $8, Premium $30, Super $100, Ultra $200 a month) each plan gets a weekly pool of usage, and past it you use prepaid credit or wait for the reset; legacy plans use on-demand usage instead. Cursor's docs say requests are never downgraded in quality or speed, so there is no slow lane to fall into.
What is Cursor fast mode?
A faster variant of some models, such as Grok and Composer. Cursor prices it per model, mostly at twice the standard rate and up to about six times on Composer 2.5 Fast. It is off on Plus; Premium and above can turn it on.
How do I know if Cursor itself is down?
The live panel on this page shows Cursor's own status for the IDE, the CLI, Cloud Agents and cursor.com, read from status.cursor.com. If one model provider is struggling you will usually see an incident naming it there.