Hi all,
I’m encountering persistent connectivity issues with Cursor 1.0.0, while version 0.5 continues to work without any problems in the same environment. This is happening for an update from 0.50 to 1.0 or a clean install.
I renamed folders (not deleted):
C:\Users\user\.cursor
C:\Users\user\AppData\Local\Programs\cursor
C:\Users\user\AppData\Roaming\Cursor
Bug Summary
- DNS resolution is successful and consistent (both IPv4 and IPv6) for
api2.cursor.sh
andmarketplace.cursorapi.com
. - Connection fails within the Cursor 1.0.0 app itself, despite external tools resolving correctly.
- Verified across multiple DNS resolvers (local, Cloudflare, Google 8.8.8.8).
- No firewall, proxy, or host-level blocking is in place.
- Running over a TLS 1.3-VPN, fragmented packets, IP geolocation in AWS Netherlands.
Packet Capture Highlights (sanitized)
Wireshark outside the Cursor seems working:
Query: A, AAAA -> api2.cursor.sh
Response: CNAME chain → api2geo → api2direct → multiple A records (e.g., 52.206.197.22)
Query: A, AAAA -> marketplace.cursorapi.com
Response: Multiple valid A records (e.g., 54.86.196.189, 35.169.198.175)
TLS Handshakes: Attempted to multiple IPs (e.g., 172.67.126.242, 93.123.102.179)
TCP ACKs & TLSv1.2 Application Data seen, but client does not complete session.
Version: 1.0.0 (user setup)
VSCode Version: 1.96.2
Commit: 53b99ce608cba35127ae3a050c1738a959750860
Date: 2025-06-04T19:44:25.253Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
Hypothesis
This appears to be a client-level regression or configuration or account-level issue introduced in Cursor 1.0.0. Anybody confirming this, or know the fix for the issue?
Thanks in advance for any insights or patches you can provide!