I have some problems?

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hey everyone :waving_hand:

Is anyone else experiencing massive slowdowns today (Nov 7, 2025)?
For me, Cursor has become almost unusable — code completions take 10–30 seconds, and GPT-5 / GPT-5 Codex often hang or timeout completely.
Even switching to Sonnet 4.5 or Haiku 4.5 only helps a little.

I’ve tried:
– Restarting the app
– Switching between different models (GPT-5 Low Fast, Haiku, Sonnet, etc.)
– Clearing cache and local data

Nothing seems to fix it — everything just feels super laggy today.
Is there any official info about degraded performance or a known outage?
Would appreciate a quick update from the team :folded_hands:

Thanks!
Flo

Steps to Reproduce

How can I?

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Cursor: 2.0.64
VS CODE: 1.99.3

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @flo1109, thanks for the detailed report!

I’m not seeing other reports of slowdowns today, so this might be a network or local configuration issue. Could you please help diagnose:

  1. Network Diagnostics:
  • Go to Cursor Settings > Network > Run Diagnostics
  • Share the results
  1. Try disabling HTTP/2:
  • Open Settings (CMD + ,) > search “HTTP/2”
  • Enable “Disable HTTP/2”
  • Restart Cursor and test
  1. Check for extension conflicts:
  • Run cursor --disable-extensions from terminal
  • Does performance improve?
  1. Share Request IDs:
  • After a slow/failed completion, open CMD + Shift + P > “Report AI Action”
  • Share a few Request IDs from recent failures

This will help us figure out if it’s network-related, an extension conflict, or something else. Let me know what you find!

Here are my results:

DNS:
[2025-11-08T09:00:36.646Z] Host: api2.cursor.sh
[2025-11-08T09:00:36.646Z] Servers: 192.168.2.1
[2025-11-08T09:00:36.646Z] Resolved to 3.214.104.99 in 13ms
[2025-11-08T09:00:36.661Z] Resolved to 3.214.104.99 in 2ms
[2025-11-08T09:00:36.663Z] Resolved to 3.214.104.99 in 1ms
[2025-11-08T09:00:36.665Z] Resolved to 3.214.104.99 in 2ms
[2025-11-08T09:00:36.669Z] Host: api2.cursor.sh
[2025-11-08T09:00:36.669Z] Servers: system
[2025-11-08T09:00:36.669Z] Resolved to 3.214.104.99, 52.20.137.141, 52.73.164.13, 23.22.77.176, 3.91.140.233, 52.204.102.74, 3.224.55.137, 54.90.17.71 in 4ms
[2025-11-08T09:00:36.669Z] Resolved to 3.214.104.99, 52.20.137.141, 52.73.164.13, 23.22.77.176, 3.91.140.233, 52.204.102.74, 3.224.55.137, 54.90.17.71 in 0ms
[2025-11-08T09:00:36.669Z] Resolved to 3.214.104.99, 52.20.137.141, 52.73.164.13, 23.22.77.176, 3.91.140.233, 52.204.102.74, 3.224.55.137, 54.90.17.71 in 0ms
[2025-11-08T09:00:36.670Z] Resolved to 3.214.104.99, 52.20.137.141, 52.73.164.13, 23.22.77.176, 3.91.140.233, 52.204.102.74, 3.224.55.137, 54.90.17.71 in 1ms
[2025-11-08T09:00:36.670Z] Result: true

HTTP/2

[2025-11-08T09:00:36.627Z] Start
[2025-11-08T09:00:36.897Z] Host: api2.cursor.sh
[2025-11-08T09:00:36.897Z] Protocol: h2
[2025-11-08T09:00:36.897Z] Result: true in 270ms

SSL

[2025-11-08T09:00:36.627Z] Start
[2025-11-08T09:00:37.050Z] URL: https://api2.cursor.sh/
[2025-11-08T09:00:37.050Z] Status: 200
[2025-11-08T09:00:37.050Z] IP: 3.214.104.99
[2025-11-08T09:00:37.050Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M03
[2025-11-08T09:00:37.050Z] Name: api2.cursor.sh
[2025-11-08T09:00:37.050Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2025-11-08T09:00:37.050Z] DNS Time: 12ms
[2025-11-08T09:00:37.050Z] Connect Time: 143ms
[2025-11-08T09:00:37.050Z] TLS Time: 132ms
[2025-11-08T09:00:37.050Z] Result: true in 423ms

API

[2025-11-08T09:00:36.627Z] Start
[2025-11-08T09:00:37.062Z] Result: true

Ping

[2025-11-08T09:00:36.628Z] Sending ping 1
[2025-11-08T09:00:37.062Z] Response: ‘ping’ in 434ms
[2025-11-08T09:00:37.062Z] Sending ping 2
[2025-11-08T09:00:37.197Z] Response: ‘ping’ in 135ms
[2025-11-08T09:00:37.197Z] Sending ping 3
[2025-11-08T09:00:37.322Z] Response: ‘ping’ in 125ms
[2025-11-08T09:00:37.322Z] Sending ping 4
[2025-11-08T09:00:37.487Z] Response: ‘ping’ in 165ms
[2025-11-08T09:00:37.487Z] Sending ping 5
[2025-11-08T09:00:37.613Z] Response: ‘ping’ in 126ms
[2025-11-08T09:00:37.613Z] Result: true

Chat

[2025-11-08T09:00:36.628Z] Starting stream
[2025-11-08T09:00:37.063Z] Response: ‘foo’ in 434ms
[2025-11-08T09:00:38.035Z] Response: ‘foo’ in 972ms
[2025-11-08T09:00:39.054Z] Response: ‘foo’ in 1019ms
[2025-11-08T09:00:40.038Z] Response: ‘foo’ in 984ms
[2025-11-08T09:00:41.063Z] Response: ‘foo’ in 1025ms
[2025-11-08T09:00:42.037Z] Result: true

Agent

[2025-11-08T09:00:36.629Z] Starting stream
[2025-11-08T09:00:36.629Z] Pushing first message
[2025-11-08T09:00:37.064Z] Response: ‘foo’ in 435ms
[2025-11-08T09:00:37.565Z] Pushing next message
[2025-11-08T09:00:37.686Z] Response: ‘foo’ in 622ms
[2025-11-08T09:00:38.187Z] Pushing next message
[2025-11-08T09:00:38.322Z] Response: ‘foo’ in 636ms
[2025-11-08T09:00:38.823Z] Pushing next message
[2025-11-08T09:00:38.945Z] Response: ‘foo’ in 623ms
[2025-11-08T09:00:39.447Z] Pushing next message
[2025-11-08T09:00:39.664Z] Response: ‘foo’ in 719ms
[2025-11-08T09:00:39.664Z] Result: true

Marketplace

[2025-11-08T09:00:36.626Z] Host: marketplace.cursorapi.com
[2025-11-08T09:00:37.069Z] Response in 443ms
[2025-11-08T09:00:37.069Z] Response: 200
[2025-11-08T09:00:37.069Z] Response Type: cors
[2025-11-08T09:00:37.069Z] Server: null
[2025-11-08T09:00:37.069Z] Result: OK in 443ms

No Antwort?

cursor is so slow :frowning:

I can’t work so….

Thanks for sharing the diagnostics!

Since the issue persists, could you please try the remaining diagnostic steps:

  1. Disable HTTP/2: Open Settings (CMD + ,) > search “HTTP/2” > Enable “Disable HTTP/2” > restart Cursor and test
  2. Test without extensions: Run cursor --disable-extensions from terminal - does performance improve?
  3. Share Request IDs: After a slow/timeout completion, open CMD + Shift + P > “Report AI Action” and share a few Request IDs

Let me know what you find!

There are no general wide issues as seen on https://status.cursor.com/

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.