Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
For at least 4 hours, AI models have been responding with very long response times: about 5 minutes (sometimes even longer). The message “Taking longer than expected…” is displayed. I set the network to http/1.1, but it didn’t work. I restarted Cursor, but that didn’t work either. Network diagnostics indicate that everything is functioning properly. Are there any problems? It’s impossible to work with response times like that.
Steps to Reproduce
Questioning AI models
Expected Behavior
That the models respond within an acceptable time frame and that we can work.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Version Information
Version: 2.5.25 (user setup)
VSCode Version: 1.105.1
Commit: 7150844152b426ed50d2b68dd6b33b5c5beb73c0
Date: 2026-02-24T07:17:49.417Z
Build Type: Stable
Release Track: Early Access
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200
For AI issues: which model did you use?
Sonnet 4.6, Gemini 3.1 Pro, GPT 5.3 Codex
For AI issues: add Request ID with privacy disabled
b63268d9-cfe9-4a52-9e09-bbfc96975957
Additional Information
Cursor Network Diagnostic Results
DNS: Success
Logs:
[2026-02-25T14:25:40.673Z] Host: api2.cursor.sh
[2026-02-25T14:25:40.673Z] Servers: 192.168.1.1,fe80::321f:48ff:fe11:5bac
[2026-02-25T14:25:40.673Z] Resolved to 98.95.140.133 in 18ms
[2026-02-25T14:25:40.727Z] Resolved to 98.95.140.133 in 21ms
[2026-02-25T14:25:40.805Z] Resolved to 98.95.140.133 in 59ms
[2026-02-25T14:25:40.822Z] Resolved to 98.95.140.133 in 3ms
[2026-02-25T14:25:40.871Z] Host: api2.cursor.sh
[2026-02-25T14:25:40.871Z] Servers: system
[2026-02-25T14:25:40.871Z] Resolved to 52.86.248.14, 54.85.38.176, 54.164.221.176, 3.211.161.153, 44.219.86.106, 107.21.32.129, 100.51.11.180, 98.95.140.133 in 40ms
[2026-02-25T14:25:40.874Z] Resolved to 52.86.248.14, 54.85.38.176, 54.164.221.176, 3.211.161.153, 44.219.86.106, 107.21.32.129, 100.51.11.180, 98.95.140.133 in 0ms
[2026-02-25T14:25:40.882Z] Resolved to 52.86.248.14, 54.85.38.176, 54.164.221.176, 3.211.161.153, 44.219.86.106, 107.21.32.129, 100.51.11.180, 98.95.140.133 in 0ms
[2026-02-25T14:25:40.884Z] Resolved to 52.86.248.14, 54.85.38.176, 54.164.221.176, 3.211.161.153, 44.219.86.106, 107.21.32.129, 100.51.11.180, 98.95.140.133 in 1ms
[2026-02-25T14:25:40.884Z] Result: true
SSL: Success
Logs:
[2026-02-25T14:25:40.632Z] Start
[2026-02-25T14:25:41.141Z] URL: https://api2.cursor.sh/
[2026-02-25T14:25:41.141Z] Status: 200
[2026-02-25T14:25:41.141Z] IP: 98.95.140.133
[2026-02-25T14:25:41.141Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-02-25T14:25:41.141Z] Name: api2.cursor.sh
[2026-02-25T14:25:41.141Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-02-25T14:25:41.141Z] DNS Time: 16ms
[2026-02-25T14:25:41.141Z] Connect Time: 170ms
[2026-02-25T14:25:41.141Z] TLS Time: 118ms
[2026-02-25T14:25:41.141Z] Result: true in 509ms
API: Success
Logs:
[2026-02-25T14:25:40.633Z] Start
[2026-02-25T14:25:41.258Z] Result: true
Ping: Success
Logs:
[2026-02-25T14:25:40.636Z] Sending ping 1
[2026-02-25T14:25:41.204Z] Response: ‘ping’ in 568ms
[2026-02-25T14:25:41.204Z] Sending ping 2
[2026-02-25T14:25:41.590Z] Response: ‘ping’ in 386ms
[2026-02-25T14:25:41.590Z] Sending ping 3
[2026-02-25T14:25:41.967Z] Response: ‘ping’ in 377ms
[2026-02-25T14:25:41.967Z] Sending ping 4
[2026-02-25T14:25:42.336Z] Response: ‘ping’ in 369ms
[2026-02-25T14:25:42.336Z] Sending ping 5
[2026-02-25T14:25:42.700Z] Response: ‘ping’ in 364ms
[2026-02-25T14:25:42.700Z] Result: true
Chat: Success
Logs:
[2026-02-25T14:25:40.638Z] Starting streamSSE
[2026-02-25T14:25:41.203Z] Response: ‘foo’ in 563ms
[2026-02-25T14:25:42.149Z] Response: ‘foo’ in 946ms
[2026-02-25T14:25:43.172Z] Response: ‘foo’ in 1023ms
[2026-02-25T14:25:44.150Z] Response: ‘foo’ in 978ms
[2026-02-25T14:25:45.149Z] Response: ‘foo’ in 999ms
[2026-02-25T14:25:46.152Z] Result: true
Agent: Success
Logs:
[2026-02-25T14:25:40.639Z] Starting stream
[2026-02-25T14:25:40.640Z] Pushing first message
[2026-02-25T14:25:41.401Z] Response: ‘foo’ in 761ms
[2026-02-25T14:25:41.915Z] Pushing next message
[2026-02-25T14:25:42.398Z] Response: ‘foo’ in 997ms
[2026-02-25T14:25:42.905Z] Pushing next message
[2026-02-25T14:25:43.337Z] Response: ‘foo’ in 939ms
[2026-02-25T14:25:43.842Z] Pushing next message
[2026-02-25T14:25:44.308Z] Response: ‘foo’ in 971ms
[2026-02-25T14:25:44.815Z] Pushing next message
[2026-02-25T14:25:45.207Z] Response: ‘foo’ in 899ms
[2026-02-25T14:25:45.207Z] Result: true
Marketplace: Success
Logs:
[2026-02-25T14:25:40.624Z] Host: marketplace.cursorapi.com
[2026-02-25T14:25:41.092Z] Response in 468ms
[2026-02-25T14:25:41.092Z] Response: 200
[2026-02-25T14:25:41.092Z] Response Type: cors
[2026-02-25T14:25:41.092Z] Server: null
[2026-02-25T14:25:41.092Z] Result: OK in 468ms
Authentication: Success
Logs:
[2026-02-25T14:25:40.626Z] Host: prod.authentication.cursor.sh
[2026-02-25T14:25:40.764Z] Response: 200 in 138ms
Authentication UI: Success
Logs:
[2026-02-25T14:25:40.632Z] DNS lookup: authenticator.cursor.sh
[2026-02-25T14:25:40.724Z] Resolved authenticator.cursor.sh to 172.64.152.23 in 41ms
Cursor Tab: Success
Logs:
[2026-02-25T14:25:40.632Z] DNS lookup: api3.cursor.sh
[2026-02-25T14:25:40.677Z] Resolved api3.cursor.sh to 104.18.19.125 in 12ms
Agent Endpoint: Success
Logs:
[2026-02-25T14:25:40.632Z] DNS lookup: agent.api5.cursor.sh
[2026-02-25T14:25:40.726Z] Resolved agent.api5.cursor.sh to 100.30.166.181 in 40ms
Codebase Indexing: Success
Logs:
[2026-02-25T14:25:40.632Z] DNS lookup: repo42.cursor.sh
[2026-02-25T14:25:40.727Z] Resolved repo42.cursor.sh to 18.232.37.46 in 42ms
Downloads: Success
Logs:
[2026-02-25T14:25:40.629Z] Host: downloads.cursor.com
[2026-02-25T14:25:41.145Z] Response: 403 in 516ms
CDN: Success
Logs:
[2026-02-25T14:25:40.631Z] Host: cursor-cdn.com
[2026-02-25T14:25:41.035Z] Response: 404 in 404ms
Does this stop you from using Cursor
No - Cursor works, but with this issue