Client: Cursor 3.24.18 (stable, updated Oct 14)
Account: [email protected] — Pro+ $60/mo
Usage: Cursor Models 28% used, Other Models 0% used (quota NOT exhausted)
Issue: All requests fail with resource_exhausted (capacity error),
including a brand-new empty conversation with no attachments and
a single short message.
grok-4.7: ConnectError [not_found] and [resource_exhausted]
claude-opus-4-8: [resource_exhausted] after 4 automatic retries
Notes: UI shows “Network Error” but logs confirm RPC code 8
(resource_exhausted). This matches the official Oct 15-16 incident
“Elevated errors affecting Grok models - some requests may fail with
a capacity error”. Network path to api2.cursor.sh verified healthy
(HTTP 200 via both direct and proxy).
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Hey @gu_lingle, thanks for the request IDs! This isn’t the Oct 15-16 capacity issue and your Pro+ plan is fine — those requests are going through a personal API key. Use Azure OpenAI is turned on in your settings with empty fields, so every non-Cursor model (Claude, Grok) fails before reaching a provider, which is why Auto still works.
Fix:
Cursor Settings > Models > API Keys
Turn off Use Azure OpenAI and clear its fields (plus any other personal-key toggles / custom OpenAI Base URL you aren’t using).
Start a new chat and try Claude Opus 4.8, then Grok 4.7.
They should work right away and count against your Pro+ usage as normal. If anything still fails, reply with a new Request ID. More: Bring your own API key