[Bug] Cursor IDE cannot connect to API from

Support Help
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Title: [Bug] Cursor IDE cannot connect to API from
Cameroon (Starlink) — Pro subscriber

CURSOR VERSION
Product: Cursor IDE (standalone desktop application)
Version: 3.21.16 (system setup)
VS Code Extension API: 1.128.0
Commit: 8ae78e8eee1e63479c7e0504b664bc0a80c68000
Date: 2026-09-19T06:43:22.276Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.19045

SYSTEM SPECS
Device: DESKTOP-26ABSG6
Processor: Intel Core i7-4610M @ 3.00GHz
RAM: 8.00 GB
Graphics: Intel HD Graphics 4600
OS: Windows 10 64-bit
Location: Yaoundé, Cameroon
ISP: Starlink

DESCRIPTION
Since this morning, every prompt in the Cursor IDE
desktop app shows “Taking longer than expected” and
never responds. The app opens normally but no AI
response is ever returned.

Root cause identified: the Cursor API endpoint
“api dot cursor dot sh” cannot be resolved from
Starlink Cameroon. Navigating to that address in
the browser returns DNS_PROBE_FINISHED_NXDOMAIN.

STEPS TO REPRODUCE

  1. Open Cursor IDE desktop app on Windows 10
    Location: Yaoundé, Cameroon, ISP: Starlink

  2. Wait for the app to fully load — opens normally
    with no error message

  3. Open a new chat panel using Ctrl + L

  4. Type any simple prompt: “say hello”

  5. Press Enter to send

  6. Observe: message shows “Taking longer than
    expected…” and never receives a response

  7. Open a browser and navigate to the Cursor API
    address: api dot cursor dot sh
    Observe: “This site can’t be reached”
    Error code: DNS_PROBE_FINISHED_NXDOMAIN

  8. Switch AI model (claude-sonnet-4-6, gpt-4o,
    gpt-4o-mini) and repeat steps 4 and 5
    Observe: same result on every model

  9. Run an internet speed test using fast dot com
    Result: 21 Mbps — internet connection is fine

  10. Open the Cursor Background Agent in browser
    Observe: responds instantly — account is active
    and credits available (only 2.3% used)

EXPECTED BEHAVIOUR
Cursor IDE should connect to its API and respond
to prompts normally for all Pro subscribers
regardless of geographic location or ISP.

ACTUAL BEHAVIOUR
Every prompt times out indefinitely.
The Cursor API domain fails DNS resolution
entirely from Starlink Cameroon.
All other internet services work normally.

WHAT I HAVE ALREADY TRIED

  • Cleared all Cursor cache folders
  • Switched AI models — same result on all models
  • Disabled Windows Defender real-time scanning
  • Fixed disk usage (was 100%, now at 6%)
  • Credits confirmed available (only 2.3% used)
  • Restarted Cursor and computer multiple times
  • Changed DNS to Google DNS (8.8.8.8) — no change

WHAT STILL WORKS

  • Internet speed: 21 Mbps confirmed
  • All other websites load normally
  • Cursor website itself loads fine
  • Cursor Background Agent works perfectly
  • GitHub, Azure, all dev tools work normally

IMPACT
Full working day lost as a paying Pro subscriber.
Is this a known DNS routing issue for Starlink
users in Central Africa? Is there a recommended
workaround while this is being investigated?

Steps to Reproduce

STEPS TO REPRODUCE

  1. Open Cursor IDE desktop app on Windows 10
    Location: Yaoundé, Cameroon, ISP: Starlink

  2. Wait for the app to fully load — opens normally
    with no error message

  3. Open a new chat panel using Ctrl + L

  4. Type any simple prompt: “say hello”

  5. Press Enter to send

  6. Observe: message shows “Taking longer than
    expected…” and never receives a response

  7. Open a browser and navigate to the Cursor API
    address: api dot cursor dot sh
    Observe: “This site can’t be reached”
    Error code: DNS_PROBE_FINISHED_NXDOMAIN

  8. Switch AI model (claude-sonnet-4-6, gpt-4o,
    gpt-4o-mini) and repeat steps 4 and 5
    Observe: same result on every model

  9. Run an internet speed test using fast dot com
    Result: 21 Mbps — internet connection is fine

  10. Open the Cursor Background Agent in browser
    Observe: responds instantly — account is active
    and credits available (only 2.3% used)

Expected Behavior

EXPECTED BEHAVIOUR
Cursor IDE should connect to its API and respond
to prompts normally for all Pro subscribers
regardless of geographic location or ISP.

ACTUAL BEHAVIOUR
Every prompt times out indefinitely.
The Cursor API domain fails DNS resolution
entirely from Starlink Cameroon.
All other internet services work normally.

WHAT I HAVE ALREADY TRIED

  • Cleared all Cursor cache folders
  • Switched AI models — same result on all models
  • Disabled Windows Defender real-time scanning
  • Fixed disk usage (was 100%, now at 6%)
  • Credits confirmed available (only 2.3% used)
  • Restarted Cursor and computer multiple times
  • Changed DNS to Google DNS (8.8.8.8) — no change

WHAT STILL WORKS

  • Internet speed: 21 Mbps confirmed
  • All other websites load normally
  • Cursor website itself loads fine
  • Cursor Background Agent works perfectly
  • GitHub, Azure, all dev tools work normally

Screenshots / Screen Recordings

cursor.PNG
cursor.PNG427×218 1.95 KB

Operating System

Windows 10/11

Version Information

Version: 3.21.16 (system setup)
VS Code Extension API: 1.128.0
Commit: 8ae78e8eee1e63479c7e0504b664bc0a80c68000
Date: 2026-09-19T06:43:22.276Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.19045

For AI issues: which model did you use?

I used Auto and Grok new agent.

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the detailed report and all the troubleshooting steps, that really helps.

Quick note on networking. api.cursor.sh is not an address Cursor actually uses, so everyone gets NXDOMAIN for it in any region. That’s not what’s blocking you. Based on our data, Cursor can reach our servers from your connection, and the fact that the Background Agent in the browser responds instantly confirms that.

About Starlink. This issue isn’t tied to Starlink, we see the same hang on other networks too, so switching ISP or DNS won’t fix it. With Starlink and CGNAT you can sometimes get short DNS hiccups, and switching to Google DNS 8.8.8.8 like you did is the right step for those, but in your case that’s not the root cause.

What you’re seeing is a known issue in Cursor 3.21 on Windows. A chat request can hang before it’s actually sent and then it stays on “Taking longer than expected” forever. I can’t share an ETA yet, but I’ve passed this to the team and added your case.

For now, here’s a workaround. Try these steps and let me know what happens.

  1. Fully close Cursor and open it again.
  2. Wait about a minute for everything to finish loading.
  3. Close all editor tabs Ctrl+K, then W so no file is open.
  4. Press Ctrl+L and start a new chat.
  5. Send “say hello”.
  6. If you get a reply, open any file, click inside it, and send another message in the same chat.

Does step 5 respond. Does step 6 hang again. If anything still hangs, send the Request ID three dots in the top right of the chat > Copy Request ID and your Cursor version, and we’ll dig in further.

6

Thank you for the reply. The indefinite loop was solved, i can now continue using cursor chat.