From 04.01 to now, too many requests without response after 3 second

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Too many requests has no any response likes no token outputs, almost 10% everyday, sometimes 30%; It affects my workflow very serious!

Steps to Reproduce

Types the chat, waiting the response;
Actually no response in the chat UI, after 5 minutes ~ 30 minutes.
It only has ‘Taking longer than excepted’.

Expected Behavior

If your service is live, then you should give me some response, maybe not token.

Operating System

MacOS

Version Information

Version: 3.1.17
VSCode Version: 1.105.1
Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90
Date: 2026-04-19T19:33:58.189Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

For AI issues: which model did you use?

Any models. Evens ‘Thinking-Model’ is serious

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hi @zhaoxi2000,

Thanks for reporting this. I understand how frustrating it is when requests hang.

I looked into your account’s recent activity. On the server side, the vast majority of your requests are completing successfully with output. The “Taking longer than expected” message is a temporary indicator that appears when the first response takes a bit longer to arrive – it doesn’t necessarily mean the request failed. In most cases, the response should still come through if you wait a bit.

That said, we’ve recently shipped several fixes for cases where chat responses were genuinely getting stuck. Since you’re on version 3.1.17, you should already have those improvements.

A few things that could help:

  1. Run a Network Diagnostic – go to Cursor Settings > Network > Run Diagnostics and share the results here. This will tell us if there’s any connectivity issue between your machine and our servers that could be causing slow first-token delivery.

  2. Try switching models – if a specific model is consistently slow, try Auto mode, which selects the best-performing model available.

  3. Share a Request ID from a specific stuck request – when a request hangs, click the three dots at the top of the chat and select Copy Request ID, then paste it here. This helps us trace exactly what happened on our end. How to find your Request ID

You may also find context in this related thread where other users reported similar symptoms: My chats are just hanging with “Planning next moves” and “Taking longer than expected…”

7

“it doesn’t necessarily mean the request failed”

- → Sorry, as a user experience, I do not agree with you, the IDE UI should receive the response data and take them smoothly.

8

Waste my quota, too much!

10

This month is almost 50 / 500 invalid requests.

11

Hi, brother, do you receive the screenshot and information for your debugger.

12

I hear you on the UX frustration – you’re right that a request sitting on “Taking longer than expected” for minutes feels like a failure, regardless of what’s happening server-side. That’s fair feedback.

To clarify: I don’t see any screenshot or debug information attached to this thread. It’s possible the upload didn’t go through. Could you try sharing the following directly in a reply here?

  1. A Request ID from a specific stuck request – click the three dots at the top of the chat pane and select Copy Request ID, then paste it here. This is the single most helpful thing for us to trace what happened. How to find your Request ID

  2. Network Diagnostics results – go to Cursor Settings > Network > Run Diagnostics, then use the “Copy diagnostics” button and paste the results here.

With a request ID from a stuck request, I can trace exactly what happened on our end and determine whether the issue is network-related or something else.

13

Cursor Network Diagnostic Results

DNS: Success
Logs:
[2026-04-24T13:40:38.913Z] Host: api2.cursor.sh
[2026-04-24T13:40:38.913Z] Servers: 2400:3200::1,2408:8888::8,210.21.196.6
[2026-04-24T13:40:38.913Z] Resolved to 3.213.29.98 in 3ms
[2026-04-24T13:40:39.422Z] Resolved to 3.213.29.98 in 504ms
[2026-04-24T13:40:39.424Z] Resolved to 3.213.29.98 in 1ms
[2026-04-24T13:40:39.425Z] Resolved to 3.213.29.98 in 0ms
[2026-04-24T13:40:39.426Z] Host: api2.cursor.sh
[2026-04-24T13:40:39.426Z] Servers: system
[2026-04-24T13:40:39.426Z] Resolved to 3.213.29.98, 100.29.113.179, 34.239.57.62, 54.173.226.230, 52.73.164.170, 3.93.224.200, 54.158.82.70, 3.234.8.224 in 1ms
[2026-04-24T13:40:39.426Z] Resolved to 3.213.29.98, 100.29.113.179, 34.239.57.62, 54.173.226.230, 52.73.164.170, 3.93.224.200, 54.158.82.70, 3.234.8.224 in 0ms
[2026-04-24T13:40:39.426Z] Resolved to 3.213.29.98, 100.29.113.179, 34.239.57.62, 54.173.226.230, 52.73.164.170, 3.93.224.200, 54.158.82.70, 3.234.8.224 in 0ms
[2026-04-24T13:40:39.426Z] Resolved to 3.213.29.98, 100.29.113.179, 34.239.57.62, 54.173.226.230, 52.73.164.170, 3.93.224.200, 54.158.82.70, 3.234.8.224 in 0ms
[2026-04-24T13:40:39.426Z] Result: true

SSL: Success
Logs:
[2026-04-24T13:40:38.901Z] Start
[2026-04-24T13:40:40.850Z] URL: https://api2.cursor.sh/
[2026-04-24T13:40:40.850Z] Status: 200
[2026-04-24T13:40:40.850Z] IP: 3.213.29.98
[2026-04-24T13:40:40.850Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-04-24T13:40:40.850Z] Name: api2.cursor.sh
[2026-04-24T13:40:40.850Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-04-24T13:40:40.850Z] DNS Time: 3ms
[2026-04-24T13:40:40.850Z] Connect Time: 13ms
[2026-04-24T13:40:40.850Z] TLS Time: 1653ms
[2026-04-24T13:40:40.850Z] Result: true in 1949ms

API: Success
Logs:
[2026-04-24T13:40:38.901Z] Start
[2026-04-24T13:40:40.822Z] Result: true

Ping: Success
Logs:
[2026-04-24T13:40:38.902Z] Sending ping 1
[2026-04-24T13:40:40.846Z] Response: ‘ping’ in 1944ms
[2026-04-24T13:40:40.846Z] Sending ping 2
[2026-04-24T13:40:42.465Z] Response: ‘ping’ in 1619ms
[2026-04-24T13:40:42.465Z] Sending ping 3
[2026-04-24T13:40:43.445Z] Response: ‘ping’ in 980ms
[2026-04-24T13:40:43.445Z] Sending ping 4
[2026-04-24T13:40:44.787Z] Response: ‘ping’ in 1342ms
[2026-04-24T13:40:44.787Z] Sending ping 5
[2026-04-24T13:40:45.697Z] Response: ‘ping’ in 910ms
[2026-04-24T13:40:45.697Z] Result: true

Chat: Success
Logs:
[2026-04-24T13:40:38.902Z] Starting streamSSE
[2026-04-24T13:40:40.842Z] Response: ‘foo’ in 1939ms
[2026-04-24T13:40:41.879Z] Response: ‘foo’ in 1037ms
[2026-04-24T13:40:42.850Z] Response: ‘foo’ in 971ms
[2026-04-24T13:40:43.854Z] Response: ‘foo’ in 1004ms
[2026-04-24T13:40:44.854Z] Response: ‘foo’ in 1000ms
[2026-04-24T13:40:45.845Z] Result: true

Agent: Success
Logs:
[2026-04-24T13:40:38.903Z] Starting stream
[2026-04-24T13:40:38.903Z] Pushing first message
[2026-04-24T13:40:40.888Z] Response: ‘foo’ in 1985ms
[2026-04-24T13:40:41.389Z] Pushing next message
[2026-04-24T13:40:42.607Z] Response: ‘foo’ in 1719ms
[2026-04-24T13:40:43.107Z] Pushing next message
[2026-04-24T13:40:44.309Z] Response: ‘foo’ in 1702ms
[2026-04-24T13:40:44.810Z] Pushing next message
[2026-04-24T13:40:45.910Z] Response: ‘foo’ in 1601ms
[2026-04-24T13:40:46.410Z] Pushing next message
[2026-04-24T13:40:47.412Z] Response: ‘foo’ in 1502ms
[2026-04-24T13:40:47.412Z] Result: true

Marketplace: Success
Logs:
[2026-04-24T13:40:38.899Z] Host: marketplace.cursorapi.com
[2026-04-24T13:40:39.859Z] Response in 960ms
[2026-04-24T13:40:39.859Z] Response: 200
[2026-04-24T13:40:39.859Z] Response Type: cors
[2026-04-24T13:40:39.859Z] Server: null
[2026-04-24T13:40:39.859Z] Result: OK in 960ms

Authentication: Success
Logs:
[2026-04-24T13:40:38.900Z] Host: prod.authentication.cursor.sh
[2026-04-24T13:40:40.872Z] Response: 200 in 1972ms

Authentication UI: Success
Logs:
[2026-04-24T13:40:38.901Z] DNS lookup: authenticator.cursor.sh
[2026-04-24T13:40:39.127Z] Resolved authenticator.cursor.sh to 172.64.152.23 in 223ms

Cursor Tab: Success
Logs:
[2026-04-24T13:40:38.901Z] DNS lookup: api3.cursor.sh
[2026-04-24T13:40:38.980Z] Resolved api3.cursor.sh to 104.18.19.125 in 76ms

Agent Endpoint: Success
Logs:
[2026-04-24T13:40:38.901Z] DNS lookup: agent.api5.cursor.sh
[2026-04-24T13:40:40.004Z] Resolved agent.api5.cursor.sh to 50.18.248.73 in 1099ms

Codebase Indexing: Success
Logs:
[2026-04-24T13:40:38.901Z] DNS lookup: repo42.cursor.sh
[2026-04-24T13:40:39.413Z] Resolved repo42.cursor.sh to 34.192.179.182 in 509ms

Downloads: Success
Logs:
[2026-04-24T13:40:38.901Z] Host: downloads.cursor.com
[2026-04-24T13:40:40.055Z] Response: 403 in 1154ms

CDN: Success
Logs:
[2026-04-24T13:40:38.901Z] Host: cursor-cdn.com
[2026-04-24T13:40:39.805Z] Response: 404 in 904ms