Is there an issue with Cursor today? Repeated connection fail

Continuously get :
It normally happens for brief moments, but I’ve been unable to use cursor at all this morning.
Tried different agents, etc. same result.

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Agents are not connecting. Been the case the full morning.

“Agent encountered ena error - we failed to reach the AI provider despite multiple retry attempts”


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. go to agent and ask something

Expected Behavior
What is meant to happen here that isn’t working correctly?
Well… the agent does something.


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)
You got it


Operating System

  • Windows 10/11
  • MacOS
  • Linux
  • Irrelevant I’m using your cloud

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy

  • For Cursor CLI: Run agent about in your terminal

    Not sure that’s what you meant but :

    -bash: agent: command not found

    root@cursor:/workspace#

IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66


For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
Currently Composer 2.5 previously gemini pro, and I had to also request a billing review this morning (sent to hi@cursor - but don’t think it’s linked, though who knows).


For AI issues: add Request ID with privacy disabled
Request ID: not really relevant but for instance this agent : bc-f4297082-ab4d-48af-943a-ef9872aed98c (also the one from my support email).


Additional Information
Add any other context about the problem here.
No, it’s pretty clear.


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!

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

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!

done

If you can investigate urgently because I can’t use Cursor anymore.
All new agents end up failing in the same way after a few minutes.

Thanks, @FredP. We’re currently seeing high load on Composer 2.5. Our team is aware of the issue and is actively investigating. In the meantime, we’d recommend switching to another model as a workaround. We appreciate your patience!

So the current workaround for overloaded Composer 2.5 is to switch to a more expensive model? :sweat_smile:
Not exactly the kind of graceful degradation users hope for. :rofl: