Persistent ConnectError: [unknown] Network disconnected / read ECONNRESET to api2.cursor.sh

[Edzhod_Ashurov (Эджод Ашуров)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am consistently getting ConnectError: [unknown] Network disconnected and read ECONNRESET errors when using Cursor AI chat. According to Network Diagnostics, api2.cursor.sh resolves correctly to multiple IPs (52.70.238.83 and others) with Result: true, but the connection is dropped after ~10–30 seconds during stream/streamSSE with ECONNRESET or ConnectError: [unknown] Network disconnected. DNS is set to Google DNS (8.8.8.8/8.8.4.4), HTTP/2 is disabled, VPN/proxy is disabled, firewall allows Cursor, and cursor.com opens fine in browser.

Steps to Reproduce

1. Open Cursor IDE
2. Try to use AI chat (type a query or press Ctrl+L)
3. Wait for the chat to attempt to connect to api2.cursor.sh
4. Within 10–30 seconds, observe ConnectError: [unknown] Network disconnected or read ECONNRESET error message
5. Network Diagnostics shows DNS resolution works, but connection drops during stream initialization

Expected Behavior

AI chat should connect successfully to api2.cursor.sh and stream responses without interruption. Instead, the connection fails with ConnectError or ECONNRESET errors.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 0.45.3
VSCode Version: 1.105.2
Commit: [from About Cursor]

For AI issues: which model did you use?

N/A - Connection fails before model selection

For AI issues: add Request ID with privacy disabled

Request ID: 4e66da19-94c9-4056-bce5-803301d5ea82

Additional Information

Network Diagnostics output shows:

• DNS (8.8.8.8): Resolved api2.cursor.sh to 52.70.238.83 in 14ms, Result: true
• System DNS: Resolved to multiple IPs (18.210.204.40, 34.232.47.146, 52.203.195.129, 52.70.238.83, etc.)
• Connection error: read ECONNRESET in ~30 seconds during stream/streamSSE initialization
• No issues found in local network (VPN disabled, firewall allows Cursor, browser works)
• This issue started around Nov 24-28, 2025, appears to be widespread (many users reporting similar errors on forum)

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report. This is a critical issue, and we need to dig deeper.

A few quick tests to isolate the problem:

• Try a mobile hotspot - Connect your phone’s hotspot and check if AI chat works. This rules out ISP/network routing issues.
• Test with Ethernet (if you’re on Wi-Fi) or vice versa - Helps determine if the issue is network interface-specific.

Share full logs:

• Open Help > Developer Tools > Console CTRL+Shift+J, reproduce the error, and share the full error message (screenshot or paste here)
• Check %APPDATA%\Cursor\logs and share the most recent log file

I’m flagging this as a potential issue with our backend or edge routing.

[Edzhod_Ashurov (Эджод Ашуров)]

@deanrie

I tested with mobile hotspot (Tecno Pova 5) and the same issue persists - ConnectError: [unknown] Network disconnected / read ECONNRESET occurs after 10-30 seconds.

Test results:

• Network: Changed from home Wi-Fi to mobile hotspot (different ISP/carrier)
• AI Chat: Still fails with identical error
• Browser & other apps: Work fine on mobile hotspot

This confirms the issue is NOT on my network side. The problem appears to be on Cursor’s backend or edge routing as you suspected.

20251128T145030.zip (91,4 КБ)

[deanrie]

Thanks for the info, and great that you tested with a mobile hotspot - that’s very helpful.

Your data indicates the issue is on the backend or edge routing side. I’m escalating this to the engineering team with priority as urgent.

While it’s being investigated:

• If possible, try a VPN from another country (it might be a geographic edge routing issue).

[Edzhod_Ashurov (Эджод Ашуров)]

I already tested with V2Ray tunneling from different regions:

• V2Ray Germany (Berlin)
• V2Ray Nigeria (Lagos)

Result: Same ConnectError: [unknown] Network disconnected / read ECONNRESET error persists regardless of region or tunneling protocol.

This confirms the issue is NOT related to geographic edge routing or specific network routing paths. The problem appears to be at a deeper level in Cursor’s backend infrastructure.

[Edzhod_Ashurov (Эджод Ашуров)]

After downgrading to version 2.0 and connecting through a German VPN, everything began working. The connection was established over HTTP/1, but issues persisted with HTTP/2.