Keep getting connection error since yeterday

Support Help
1

Hi folks, I keep getting connection errors since yesterday. Can anyone help? Thanks!

Request ID: 06916c66-595d-47bd-b355-b79d0ff5eba1
Canceled
RetriableError: Canceled
at Hqi (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9066:8640)
at Scp (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9067:11962)
at Object.classify (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9067:16467)
at pdf (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9067:5856)
at async fWo.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9067:15819)
at async xV.runAgentLoop (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20459:3067)
at async aba.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20487:14009)
at async aba.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20487:23432)
at async jIe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9229:2399)
at async wk (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:19518:83910)

Version: 3.10.17 (user setup)
VS Code Extension API: 1.125.0
Commit: c89f45b831621cdc5e951694db44fecd8fab1150
Date: 2026-07-05T06:39:45.228Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

5

network diagnose seems to be fine:

Cursor Network Diagnostic Results

DNS: Success
Logs:
[2026-07-07T11:07:32.262Z] Host: api2.cursor.sh
[2026-07-07T11:07:32.264Z] Servers: 127.0.0.1
[2026-07-07T11:07:32.264Z] Resolved to 44.217.42.239 in 1ms
[2026-07-07T11:07:32.628Z] Resolved to 44.217.42.239 in 331ms
[2026-07-07T11:07:32.834Z] Resolved to 44.217.42.239 in 204ms
[2026-07-07T11:07:32.835Z] Resolved to 44.217.42.239 in 1ms
[2026-07-07T11:07:32.837Z] Host: api2.cursor.sh
[2026-07-07T11:07:32.837Z] Servers: system
[2026-07-07T11:07:32.837Z] Resolved to 44.217.42.239, 3.225.94.140, 18.235.130.131, 50.19.233.21, 50.17.235.107, 34.224.159.153, 18.205.69.111, 44.195.122.65 in 0ms
[2026-07-07T11:07:32.845Z] Resolved to 44.217.42.239, 3.225.94.140, 18.235.130.131, 50.19.233.21, 50.17.235.107, 34.224.159.153, 18.205.69.111, 44.195.122.65 in 0ms
[2026-07-07T11:07:32.846Z] Resolved to 44.217.42.239, 3.225.94.140, 18.235.130.131, 50.19.233.21, 50.17.235.107, 34.224.159.153, 18.205.69.111, 44.195.122.65 in 0ms
[2026-07-07T11:07:32.847Z] Resolved to 44.217.42.239, 3.225.94.140, 18.235.130.131, 50.19.233.21, 50.17.235.107, 34.224.159.153, 18.205.69.111, 44.195.122.65 in 0ms
[2026-07-07T11:07:32.847Z] Result: true

HTTP/2: Success
Logs:
[2026-07-07T11:07:32.122Z] Start
[2026-07-07T11:07:32.725Z] Host: api2.cursor.sh
[2026-07-07T11:07:32.725Z] Protocol: h2
[2026-07-07T11:07:32.725Z] Result: true in 603ms

SSL: Success
Logs:
[2026-07-07T11:07:32.124Z] Start
[2026-07-07T11:07:33.756Z] URL: https://api2.cursor.sh/
[2026-07-07T11:07:33.757Z] Status: 200
[2026-07-07T11:07:33.757Z] IP: 44.217.42.239
[2026-07-07T11:07:33.757Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-07-07T11:07:33.757Z] Name: api2.cursor.sh
[2026-07-07T11:07:33.757Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-07-07T11:07:33.757Z] DNS Time: 1ms
[2026-07-07T11:07:33.757Z] Connect Time: 221ms
[2026-07-07T11:07:33.757Z] TLS Time: 1103ms
[2026-07-07T11:07:33.757Z] Result: true in 1633ms

API: Success
Logs:
[2026-07-07T11:07:32.150Z] Start
[2026-07-07T11:07:33.605Z] Result: true

Ping: Success
Logs:
[2026-07-07T11:07:32.172Z] Sending ping 1
[2026-07-07T11:07:34.205Z] Response: ‘ping’ in 2033ms
[2026-07-07T11:07:34.205Z] Sending ping 2
[2026-07-07T11:07:34.910Z] Response: ‘ping’ in 705ms
[2026-07-07T11:07:34.910Z] Sending ping 3
[2026-07-07T11:07:35.152Z] Response: ‘ping’ in 242ms
[2026-07-07T11:07:35.152Z] Sending ping 4
[2026-07-07T11:07:35.395Z] Response: ‘ping’ in 243ms
[2026-07-07T11:07:35.395Z] Sending ping 5
[2026-07-07T11:07:35.644Z] Response: ‘ping’ in 249ms
[2026-07-07T11:07:35.644Z] Result: true

Chat: Success
Logs:
[2026-07-07T11:07:32.204Z] Starting stream
[2026-07-07T11:07:33.857Z] Response: ‘foo’ in 1604ms
[2026-07-07T11:07:34.859Z] Response: ‘foo’ in 1002ms
[2026-07-07T11:07:35.861Z] Response: ‘foo’ in 1001ms
[2026-07-07T11:07:36.863Z] Response: ‘foo’ in 1001ms
[2026-07-07T11:07:37.862Z] Response: ‘foo’ in 999ms
[2026-07-07T11:07:39.409Z] Result: true

Agent: Success
Logs:
[2026-07-07T11:07:32.250Z] Starting stream
[2026-07-07T11:07:32.254Z] Pushing first message
[2026-07-07T11:07:33.182Z] Response: ‘foo’ in 928ms
[2026-07-07T11:07:33.683Z] Pushing next message
[2026-07-07T11:07:33.911Z] Response: ‘foo’ in 729ms
[2026-07-07T11:07:34.417Z] Pushing next message
[2026-07-07T11:07:34.661Z] Response: ‘foo’ in 749ms
[2026-07-07T11:07:35.163Z] Pushing next message
[2026-07-07T11:07:35.396Z] Response: ‘foo’ in 734ms
[2026-07-07T11:07:35.898Z] Pushing next message
[2026-07-07T11:07:36.149Z] Response: ‘foo’ in 753ms
[2026-07-07T11:07:36.149Z] Result: true

Marketplace: Success
Logs:
[2026-07-07T11:07:32.063Z] Host: marketplace.cursorapi.com
[2026-07-07T11:07:33.307Z] Response in 1244ms
[2026-07-07T11:07:33.307Z] Response: 200
[2026-07-07T11:07:33.307Z] Response Type: cors
[2026-07-07T11:07:33.307Z] Server: null
[2026-07-07T11:07:33.307Z] Result: OK in 1244ms

Authentication: Success
Logs:
[2026-07-07T11:07:32.071Z] Host: prod.authentication.cursor.sh
[2026-07-07T11:07:32.390Z] Response: 200 in 319ms

Authentication UI: Success
Logs:
[2026-07-07T11:07:32.126Z] DNS lookup: authenticator.cursor.sh
[2026-07-07T11:07:32.421Z] Resolved authenticator.cursor.sh to 172.64.152.23 in 232ms

Cursor Tab: Success
Logs:
[2026-07-07T11:07:32.128Z] DNS lookup: api3.cursor.sh
[2026-07-07T11:07:32.365Z] Resolved api3.cursor.sh to 104.18.18.125 in 232ms

Agent Endpoint: Success
Logs:
[2026-07-07T11:07:32.129Z] DNS lookup: agent.api5.cursor.sh
[2026-07-07T11:07:32.629Z] Resolved agent.api5.cursor.sh to 50.18.248.73 in 472ms

Codebase Indexing: Success
Logs:
[2026-07-07T11:07:32.130Z] DNS lookup: repo42.cursor.sh
[2026-07-07T11:07:32.596Z] Resolved repo42.cursor.sh to 52.201.84.25 in 462ms

Downloads: Success
Logs:
[2026-07-07T11:07:32.111Z] Host: downloads.cursor.com
[2026-07-07T11:07:33.339Z] Response: 403 in 1228ms

CDN: Success
Logs:
[2026-07-07T11:07:32.121Z] Host: cursor-cdn.com
[2026-07-07T11:07:33.212Z] Response: 404 in 1091ms

6

Hi @shawnwang!

I can see you’ve successfully made requests since you posted. Did the issue resolve itself?

This is usually caused by a misbehaving proxy/VPN. Disabling HTTP 2 (Settings > Network) is typically a good troubleshooting step.

8

Hi Colin, thanks for reply. I did give HTTP 1.1 a try. It’s weird that I get one or two requests successfully and then getting the same error again and again.

Here is my latest error:

Request ID: 5412a150-944f-48d9-ae60-6d77bd977847
{“error”:“ERROR_EXTENSION_HOST_TIMEOUT”,“details”:{“title”:“Agent Execution Timed Out”,“detail”:“The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.”,“isRetryable”:false,“shouldShowImmediateError”:true,“additionalInfo”:{},“buttons”:[{“label”:“Reload Window”,“reloadWindow”:{}}],“planChoices”:}}
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.
Agent Execution Timed Out [deadline_exceeded]
ConnectError: [deadline_exceeded] Agent Execution Timed Out
at phm (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9123:32674)
at wXn.waitForProviderRegistration (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9123:37730)
at async ill._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20514:3912)
at async FOe (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7918:12028)
at async vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20514:8047
at async FOe (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7918:12028)
at async ill.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20514:7971)
at async ill.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:20514:23428)
at async uBe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9231:2399)
at async tdm.submitMessage (vscode-file://vscode-app/c:/Users/shawn/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9120:31175)

9

Thanks!

I had a look in the backend, and it looks like your VPN is getting in the way (it looks like the same issue reported over here: Can't use cursor over Astrill VPN - #12 by deanrie)

10

Yes, that looks like the case. It’s strange cursor and Astrill worked fine till a few days ago after updates. Thanks for the info. I’ll give that a try.