Cursor completely unusable - "Provider Error" on all models

[Pablo_Hortal]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor completely unusable - “Provider Error” on all models, all networks, even with my own API key.
Every chat message fails with: “We’re having trouble connecting to the model provider.”
What I’ve tried (all unsuccessful):

Fresh install (v2.4)
Sign out / sign in
Both fiber and mobile networks
HTTP/1.1 mode
Multiple models: Opus 4.5, GPT-5.2, Composer 1
My own Anthropic API key (BYOK)
Network diagnostics - all pass

Request IDs:

f13e1788-b2d9-4f3b-84b4-c47934987f5d
4341e4ce-9e98-43e3-bc2c-7562feddb279

Steps to Reproduce

1. Open any chat in Cursor
2. Type any message and send
3. Error appears: “We’re having trouble connecting to the model provider”

Expected Behavior

The model should respond normally to chat messages.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.4 (fresh install)

For AI issues: which model did you use?

Opus 4.5, Composer 1, Sonnet 4.5, GPT-5.2…

For AI issues: add Request ID with privacy disabled

f13e1788-b2d9-4f3b-84b4-c47934987f5d
4341e4ce-9e98-43e3-bc2c-7562feddb279

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report.

I can see the issue started on Feb 5. That same day there was an Anthropic-side service incident that lasted about 6 hours and was resolved. It’s possible the issue is already gone, can you try again?

If the issue is still happening, error 57 plus resource_exhausted is most often related to third-party API key settings. Please try:

1. Cursor Settings > Models

   • Make sure Override OpenAI Base URL is turned off
   • Temporarily disable your Anthropic API key, just toggle it off, don’t delete it

2. Fully sign out and sign back in (Cursor Settings > Sign Out, then Sign In)

3. Try creating a new test chat in a different project

This fixed it in similar cases: Persistent Connection Error - #3 by deanrie

If that doesn’t help, let me know and I’ll share extra diagnostic steps.

[Pablo_Hortal]

Hi Dean, thank you very much for your response. It is very much appreciated

It turns out that the problem was on the Perplexity MCP (weird!). Once I disabled that, everything started working again.