We have been able to reproduce this issue using an Ukranian VPN and are investigation. There should be a mitigation in place now while we update with a long term fix.
I’m from Ukraine as well.
Yesterday the network test was failing but I’ve checked just now, and it started working.
Whatever you did I wish you keep it.)
Version: 2.4.22 (user setup)
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Date: 2026-01-26T22:51:47.692Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200
1 Like
У меня заработало HTTP/2 само по себе.
Good day!
I’ve been experiencing persistent connection issues with Cursor when using Ukrainian IP addresses. The Network Diagnostics tool reports critical SSL Handshake errors (SSLV3_ALERT_HANDSHAKE_FAILURE) for API, Ping, and Chat services. Everything works fine only when a VPN is active, which is not an acceptable long-term solution. I am not willing to downgrade to HTTP/1 as it negatively impacts performance. Paying $20/month for a product that doesn’t function properly in my region is frustrating. Could you please provide an ETA on when this connectivity issue will be resolved for Ukrainian users?
I should also clarify that the issue is intermittent: very rarely (about 5% of the time), it starts working spontaneously without a VPN, but 95% of the time it remains broken. This inconsistency makes it nearly impossible to use the editor for professional work.
Today the issue has returned. There were great few days when everything was working.
Version: 2.4.27 (user setup)
VSCode Version: 1.105.1
Commit: 4f2b772756b8f609e1354b3063de282ccbe7a690
Date: 2026-01-31T21:24:58.143Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200
Hey @lp1641
Last night, we fixed a broken cert that we thought was causing the issue and removed the flag that sent Ukraine traffic elsewhere. We may have caused the issue to come back. Following up with the team.
1 Like
I am experiencing a similar issue to the user above (Ukrainian IP). For a period of several days (late January), HTTP/2 functioned correctly after a month of malfunctioning. However, the situation has now recurred
Version: 2.4.27 (user setup)
VSCode Version: 1.105.1
Commit: 4f2b772756b8f609e1354b3063de282ccbe7a690
Date: 2026-01-31T21:24:58.143Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.19045
Can you let us know how things are looking now? We implemented another fix and removed the mitigation.
Personally, I am currently encountering error 530. I cannot guarantee that this is true, as I saw this error two hours ago and am seeing it now as well
Ack. 530 is Cloudflare-specific, so definitely related. Letting the team know.
Handshake Failure issue seems to be not more topical for me since upgrade to Version: 2.4.28 starting this morning. 
cc @condor
@timagixe was it fixed for you with latest version upgrade?
Yes, it was fixed once I have upgraded to 2.4.28 this morning.
1 Like
HTTP/2 is working for me, according to Network, but when working with the agent, specifically when trying to implement the plan, I encounter an error: Request ID: 4127700f-00bd-4820-9fb8-bfd3a299db71
Спойлер
{“error”:“ERROR_CUSTOM”,“details”:{“title”:“Agent Execution Timed Out”,“detail”:“The agent execution provider did not respond within 16 seconds. This may indicate the extension host is not running or is unresponsive.”,“isRetryable”:false,“shouldShowImmediateError”:true,“additionalInfo”:{},“buttons”:[{“label”:“Reload Window”,“reloadWindow”:{}}],“planChoices”:}}
Agent Execution Timed Out [deadline_exceeded]
ConnectError: [deadline_exceeded] Agent Execution Timed Out
at vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11431:8256
at async sWf.createExecInstance (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11431:6308)
at async dMg (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:529:549852)
at async _W.execute (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:16084)
at async l1a.execute (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11431:1205)
at async Pcb.execute (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34235:14275)
at async jpc.buildComposerRequestContext (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34245:3573)
at async jpc.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34245:5171)
at async jpc.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34245:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14623)
at async ips.acceptPlan (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:731:1916)
at async ips.acceptPlanByUri (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:731:3003)
at async R (vscode-file://vscode-app/c:/Users/Admin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34745:1443)
Thanks, its working good for me now! 