Performance BUG!

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi, I’m honestly at the point where I regret paying for Cursor.

I’m paying $200/month and the service quality has become incredibly frustrating. The number of times requests get stuck in “reconnecting” is ridiculous. Sometimes I wait 10–15 minutes for a request to recover, only for it to fail anyway and produce absolutely nothing.

This isn’t an occasional hiccup anymore. It’s a recurring issue that completely destroys workflow and productivity. When I’m in the middle of development, having requests hang indefinitely, reconnect endlessly, or simply never complete is unacceptable for a premium product at this price point.

What’s even more frustrating is the lack of reliability. I never know whether a request will complete in 30 seconds or waste 15 minutes of my time before failing.

At $200/month, I’m not paying for excuses. I’m paying for a tool that works consistently. Right now, the experience feels unstable, unreliable, and nowhere near the standard expected from a professional-grade product.

Please stop focusing solely on new features and start fixing the core reliability issues. Stability should be the highest priority. Many of us would happily trade a dozen new features for a product that simply works when we need it.

Steps to Reproduce

Any try even Hi are you there!!!

Operating System

MacOS

Version Information

Version: 3.2.11
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z (1 mo ago)
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hi Ahmad, thanks for the detailed write-up, and I’m sorry this has been so frustrating. Rest assured we will help you sort this out and we value you as an Ultra subscriber.

A few things to try, roughly in order:

  1. Update Cursor. Your build (3.2.11, from April) is a couple of months old, and we’ve shipped a large number of reconnect and reliability fixes since then. Moving to the latest stable build is the highest-impact first step.

  2. Test your network path. If you’re on a VPN, corporate proxy, or strict firewall, try toggling the VPN off (or switching to a different network, like a personal hotspot) and see whether the reconnect hangs stop. That quickly tells us whether the network path is the cause.

  3. Lower the HTTP mode. Go to Settings → Network → HTTP Compatibility Mode and switch it from HTTP/2 to HTTP/1.1. HTTP/2 is best for low-latency streaming, but some proxy/VPN setups don’t handle it well, and HTTP/1.1 is the usual fix when streaming keeps dropping.

  4. Run Network Diagnostics. In Settings → Network there’s a built-in diagnostic. Running it will flag any blocked domains or connection problems specific to your setup. More background here: Network, proxy, and remote connections | Cursor Docs

If the hangs continue after updating and checking the network, the most useful thing you can send us is a Request ID from a request that got stuck.