Network slowness in Cursor

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The IDE is slow, that’s a fact, but network interactions is also slow, which I find strange since my diagnostics at the OS level are giving good results.

  • Reasoning steps can take 10min without streaming new token
  • Each chat / agent is generally slow
  • In the Diagnostics I see ping duration are 300ms…
  • In the Diagnostics Chat I see “Response: ‘foo’ in 1005ms”

Steps to Reproduce

n/a

Expected Behavior

Be fast

Operating System

MacOS

Version Information

Version: 2.7.0-pre.148.patch.0
VSCode Version: 1.105.1
Commit: 5ff7eda14604490cfa9ed615b378b85ed859bae0
Date: 2026-03-27T05:53:19.866Z
Layout: editor
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Sonnet 4.6 Medium, GPT 4 High, Composer 2

Request id

ea3ca322-a37c-454b-bcb9-89b8199a1fe5

Additional Information

My network diagnostics :

Cursor Network Diagnostic Results

DNS: Success
Logs:
  [2026-03-27T10:23:04.306Z] Host: api2.cursor.sh
  [2026-03-27T10:23:04.306Z] Servers: 192.168.1.1
  [2026-03-27T10:23:04.306Z] Resolved to 54.234.179.216 in 18ms
  [2026-03-27T10:23:04.333Z] Resolved to 54.157.75.46 in 25ms
  [2026-03-27T10:23:04.355Z] Resolved to 54.157.75.46 in 20ms
  [2026-03-27T10:23:04.357Z] Resolved to 54.157.75.46 in 2ms
  [2026-03-27T10:23:04.358Z] Host: api2.cursor.sh
  [2026-03-27T10:23:04.358Z] Servers: system
  [2026-03-27T10:23:04.358Z] Resolved to 54.234.179.216, 18.210.88.102, 54.157.75.46, 98.89.177.120, 54.204.15.132, 52.72.228.217, 100.55.212.207, 98.82.102.40 in 1ms
  [2026-03-27T10:23:04.358Z] Resolved to 54.234.179.216, 18.210.88.102, 54.157.75.46, 98.89.177.120, 54.204.15.132, 52.72.228.217, 100.55.212.207, 98.82.102.40 in 0ms
  [2026-03-27T10:23:04.358Z] Resolved to 54.234.179.216, 18.210.88.102, 54.157.75.46, 98.89.177.120, 54.204.15.132, 52.72.228.217, 100.55.212.207, 98.82.102.40 in 0ms
  [2026-03-27T10:23:04.358Z] Resolved to 54.234.179.216, 18.210.88.102, 54.157.75.46, 98.89.177.120, 54.204.15.132, 52.72.228.217, 100.55.212.207, 98.82.102.40 in 0ms
  [2026-03-27T10:23:04.358Z] Result: true

HTTP/2: Success
Logs:
  [2026-03-27T10:23:04.286Z] Start
  [2026-03-27T10:23:04.525Z] Host: api2.cursor.sh
  [2026-03-27T10:23:04.525Z] Protocol: h2
  [2026-03-27T10:23:04.525Z] Result: true in 239ms

SSL: Success
Logs:
  [2026-03-27T10:23:04.286Z] Start
  [2026-03-27T10:23:04.650Z] URL: https://api2.cursor.sh/
  [2026-03-27T10:23:04.650Z] Status: 200
  [2026-03-27T10:23:04.650Z] IP: 54.157.75.46
  [2026-03-27T10:23:04.650Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
  [2026-03-27T10:23:04.650Z] Name: api2.cursor.sh
  [2026-03-27T10:23:04.650Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
  [2026-03-27T10:23:04.650Z] DNS Time: 16ms
  [2026-03-27T10:23:04.650Z] Connect Time: 112ms
  [2026-03-27T10:23:04.650Z] TLS Time: 110ms
  [2026-03-27T10:23:04.650Z] Result: true in 364ms

API: Success
Logs:
  [2026-03-27T10:23:04.287Z] Start
  [2026-03-27T10:23:05.219Z] Result: true

Ping: Success
Logs:
  [2026-03-27T10:23:04.287Z] Sending ping 1
  [2026-03-27T10:23:05.187Z] Response: 'ping' in 900ms
  [2026-03-27T10:23:05.187Z] Sending ping 2
  [2026-03-27T10:23:05.503Z] Response: 'ping' in 316ms
  [2026-03-27T10:23:05.503Z] Sending ping 3
  [2026-03-27T10:23:05.875Z] Response: 'ping' in 372ms
  [2026-03-27T10:23:05.875Z] Sending ping 4
  [2026-03-27T10:23:06.003Z] Response: 'ping' in 128ms
  [2026-03-27T10:23:06.003Z] Sending ping 5
  [2026-03-27T10:23:06.318Z] Response: 'ping' in 315ms
  [2026-03-27T10:23:06.318Z] Result: true

Chat: Success
Logs:
  [2026-03-27T10:23:04.288Z] Starting stream
  [2026-03-27T10:23:05.146Z] Response: 'foo' in 858ms
  [2026-03-27T10:23:06.146Z] Response: 'foo' in 1000ms
  [2026-03-27T10:23:07.147Z] Response: 'foo' in 1001ms
  [2026-03-27T10:23:08.152Z] Response: 'foo' in 1005ms
  [2026-03-27T10:23:09.147Z] Response: 'foo' in 995ms
  [2026-03-27T10:23:10.152Z] Result: true

Agent: Success
Logs:
  [2026-03-27T10:23:04.288Z] Starting stream
  [2026-03-27T10:23:04.288Z] Pushing first message
  [2026-03-27T10:23:05.173Z] Response: 'foo' in 885ms
  [2026-03-27T10:23:05.674Z] Pushing next message
  [2026-03-27T10:23:05.702Z] Response: 'foo' in 529ms
  [2026-03-27T10:23:06.203Z] Pushing next message
  [2026-03-27T10:23:06.226Z] Response: 'foo' in 524ms
  [2026-03-27T10:23:06.728Z] Pushing next message
  [2026-03-27T10:23:06.782Z] Response: 'foo' in 556ms
  [2026-03-27T10:23:07.287Z] Pushing next message
  [2026-03-27T10:23:07.308Z] Response: 'foo' in 526ms
  [2026-03-27T10:23:07.308Z] Result: true

Marketplace: Success
Logs:
  [2026-03-27T10:23:04.282Z] Host: marketplace.cursorapi.com
  [2026-03-27T10:23:04.419Z] Response in 137ms
  [2026-03-27T10:23:04.419Z] Response: 200 
  [2026-03-27T10:23:04.419Z] Response Type: cors
  [2026-03-27T10:23:04.419Z] Server: null
  [2026-03-27T10:23:04.419Z] Result: OK in 137ms

Authentication: Success
Logs:
  [2026-03-27T10:23:04.283Z] Host: prod.authentication.cursor.sh
  [2026-03-27T10:23:04.397Z] Response: 200  in 114ms

Authentication UI: Success
Logs:
  [2026-03-27T10:23:04.286Z] DNS lookup: authenticator.cursor.sh
  [2026-03-27T10:23:04.307Z] Resolved authenticator.cursor.sh to 104.18.35.233 in 3ms

Cursor Tab: Success
Logs:
  [2026-03-27T10:23:04.286Z] DNS lookup: api3.cursor.sh
  [2026-03-27T10:23:04.332Z] Resolved api3.cursor.sh to 104.18.19.125 in 28ms

Agent Endpoint: Success
Logs:
  [2026-03-27T10:23:04.286Z] DNS lookup: agent.api5.cursor.sh
  [2026-03-27T10:23:04.332Z] Resolved agent.api5.cursor.sh to 54.163.65.150 in 28ms

Codebase Indexing: Success
Logs:
  [2026-03-27T10:23:04.286Z] DNS lookup: repo42.cursor.sh
  [2026-03-27T10:23:04.355Z] Resolved repo42.cursor.sh to 34.231.22.153 in 46ms

Downloads: Success
Logs:
  [2026-03-27T10:23:04.285Z] Host: downloads.cursor.com
  [2026-03-27T10:23:04.584Z] Response: 403  in 299ms

CDN: Success
Logs:
  [2026-03-27T10:23:04.286Z] Host: cursor-cdn.com
  [2026-03-27T10:23:04.501Z] Response: 404  in 215ms

❯ networkQuality -v
==== Verbose Results ====
---
Capacity:
---
   Uplink capacity: 106.759 Mbps
      Accuracy: High
      Uplink bytes transferred: 236.500 MB
      Uplink Flow count: 16
   Downlink capacity: 496.878 Mbps
      Accuracy: High
      Downlink bytes transferred: 1.090 GB
      Downlink Flow count: 16
---
Latency:
---
   Idle Latency:
      2570 RPM (23.345 milliseconds)
         Transport: 4324 RPM (13.875 milliseconds)
         Security: 1655 RPM (36.250 milliseconds)
         HTTP: 3013 RPM (19.911 milliseconds)
      Accuracy: High
   Responsiveness: Medium
      281 RPM (213.270 milliseconds)
         Transport: 621 RPM (96.584 milliseconds)
         Security: 403 RPM (148.653 milliseconds)
         HTTP: 362 RPM (165.545 milliseconds)
         HTTP loaded: 175 RPM (341.728 milliseconds)
      Accuracy: High
---
Protocols Used:
---
    HTTP/2: 100%
---
Transport-layer info:
---
    ECN Disabled: 100%, L4S Disabled: 100%
---
Other Info:
---
   Test Endpoint: nlams2-edge-bx-028.aaplimg.com
   Interface: en0
   Start: 2026-03-27 11:18:31.704
   End: 2026-03-27 11:18:51.175
   OS Version: Version 15.6 (Build 24G84)

==== SUMMARY ====
Uplink capacity: 106.759 Mbps
Downlink capacity: 496.878 Mbps
Responsiveness: Medium (213.270 milliseconds | 281 RPM)
Idle Latency: 23.345 milliseconds | 2570 RPM

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report and diagnostics.

Looking at your network diagnostics, the ping times 128 to 900 ms are expected for a transatlantic connection. Your DNS resolves to US-East servers, and you’re connecting from France. The chat diagnostic showing around 1 000 ms per response is also consistent with this. That part is normal and shouldn’t cause major issues on its own.

However, reasoning steps hanging for 10 minutes is definitely not normal, even with EU latency. A couple of things to check:

  • You’re on a Nightly build 2.7.0-pre.148. Can you try switching to the Stable release track to see if the issue persists? Nightly builds can have regressions that haven’t been caught yet.
  • The request ID you provided ea3ca322-a37c-454b-bcb9-89b8199a1fe5. Was this from one of the 10-minute hangs specifically? If not, could you grab a Request ID right after the next time reasoning gets stuck for an extended period? Chat context menu top right > Copy Request ID.
  • Which model specifically triggers the 10-minute hangs? Does it happen with all three Sonnet 4.6 Medium, GPT 4 High, Composer 2, or just one?

Also noticed your macOS networkQuality reports Medium responsiveness 281 RPM, which suggests some bufferbloat on your network. This probably isn’t the root cause of 10-minute hangs, but it could contribute to general sluggishness. If you’re on WiFi, trying a wired connection might help with consistency.

The team is aware of latency and lag reports. Your details help with prioritization. Let me know the above and we can dig deeper.