Cursor is super slow (Auto & Gork)

Describe the Bug

a simple “hello” mesage can take from a few second (about 5) to 1 minute to responde.

**in addition I am using “fast” mode with Grok4.7 … which cost more. it feel wrong paying for something that isn’t working.

UPDATE: 45 Minutes after posting this “Auto” agent stopped working as well.**

Steps to Reproduce

Send a message to Grok (Grok 4.7)

Expected Behavior

The agent answers …

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.22.12
VS Code Extension API: 1.128.0
Commit: 3a92974361033b2051526321308c2740fe5912c0
Date: 2026-09-26T04:55:12.125Z
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: Darwin arm64 25.1.0

For AI issues: which model did you use?

Grok 4.7

For AI issues: add Request ID with privacy disabled

9a0d1528-d72f-460e-9f5b-4fc12589bbf6

Does this stop you from using Cursor

Yes - Cursor is unusable

Cursor Network dignostic logs:
Cursor Network Diagnostic Results

DNS: Success
Logs:
[2026-09-30T10:31:43.918Z] Host: api2.cursor.sh
[2026-09-30T10:31:43.918Z] Servers: 8.8.8.8
[2026-09-30T10:31:43.918Z] Resolved to 44.219.201.237 in 6ms
[2026-09-30T10:31:44.885Z] Resolved to 44.219.201.237 in 4ms
[2026-09-30T10:31:44.957Z] Resolved to 44.212.239.118 in 3ms
[2026-09-30T10:31:44.980Z] Resolved to 44.212.239.118 in 2ms
[2026-09-30T10:31:44.983Z] Host: api2.cursor.sh
[2026-09-30T10:31:44.983Z] Servers: system
[2026-09-30T10:31:44.983Z] Resolved to 44.212.239.118, 34.192.45.121, 98.90.154.191, 44.208.219.223, 34.193.138.39, 184.192.181.35, 44.219.201.237, 34.225.210.72 in 3ms
[2026-09-30T10:31:44.983Z] Resolved to 44.212.239.118, 34.192.45.121, 98.90.154.191, 44.208.219.223, 34.193.138.39, 184.192.181.35, 44.219.201.237, 34.225.210.72 in 0ms
[2026-09-30T10:31:44.984Z] Resolved to 44.212.239.118, 34.192.45.121, 98.90.154.191, 44.208.219.223, 34.193.138.39, 184.192.181.35, 44.219.201.237, 34.225.210.72 in 0ms
[2026-09-30T10:31:44.984Z] Resolved to 44.212.239.118, 34.192.45.121, 98.90.154.191, 44.208.219.223, 34.193.138.39, 184.192.181.35, 44.219.201.237, 34.225.210.72 in 0ms
[2026-09-30T10:31:44.984Z] Result: true

HTTP/2: Success
Logs:
[2026-09-30T10:31:43.063Z] Start
[2026-09-30T10:31:44.714Z] Host: api2.cursor.sh
[2026-09-30T10:31:44.714Z] Protocol: h2
[2026-09-30T10:31:44.714Z] Result: true in 1651ms

SSL: Success
Logs:
[2026-09-30T10:31:43.063Z] Start
[2026-09-30T10:31:44.724Z] URL: https://api2.cursor.sh/
[2026-09-30T10:31:44.724Z] Status: 200
[2026-09-30T10:31:44.724Z] IP: 44.219.201.237
[2026-09-30T10:31:44.724Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-09-30T10:31:44.724Z] Name: api2.cursor.sh
[2026-09-30T10:31:44.724Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-09-30T10:31:44.724Z] DNS Time: 2ms
[2026-09-30T10:31:44.724Z] Connect Time: 152ms
[2026-09-30T10:31:44.724Z] TLS Time: 146ms
[2026-09-30T10:31:44.724Z] Result: true in 1661ms

API: Success
Logs:
[2026-09-30T10:31:43.063Z] Start
[2026-09-30T10:31:44.972Z] Result: true

Ping: Success
Logs:
[2026-09-30T10:31:43.063Z] Sending ping 1
[2026-09-30T10:31:46.118Z] Response: ‘ping’ in 3055ms
[2026-09-30T10:31:46.118Z] Sending ping 2
[2026-09-30T10:31:46.203Z] Response: ‘ping’ in 85ms
[2026-09-30T10:31:46.203Z] Sending ping 3
[2026-09-30T10:31:46.286Z] Response: ‘ping’ in 83ms
[2026-09-30T10:31:46.286Z] Sending ping 4
[2026-09-30T10:31:46.363Z] Response: ‘ping’ in 77ms
[2026-09-30T10:31:46.363Z] Sending ping 5
[2026-09-30T10:31:46.493Z] Response: ‘ping’ in 130ms
[2026-09-30T10:31:46.493Z] Result: true

Chat: Success
Logs:
[2026-09-30T10:31:43.063Z] Starting stream
[2026-09-30T10:31:45.043Z] Response: ‘foo’ in 1978ms
[2026-09-30T10:31:46.075Z] Response: ‘foo’ in 1032ms
[2026-09-30T10:31:47.072Z] Response: ‘foo’ in 997ms
[2026-09-30T10:31:48.074Z] Response: ‘foo’ in 1002ms
[2026-09-30T10:31:49.076Z] Response: ‘foo’ in 1002ms
[2026-09-30T10:31:50.047Z] Result: true

Agent: Success
Logs:
[2026-09-30T10:31:43.063Z] Starting stream
[2026-09-30T10:31:43.065Z] Pushing first message
[2026-09-30T10:31:45.009Z] Response: ‘foo’ in 1944ms
[2026-09-30T10:31:45.509Z] Pushing next message
[2026-09-30T10:31:45.605Z] Response: ‘foo’ in 596ms
[2026-09-30T10:31:46.107Z] Pushing next message
[2026-09-30T10:31:46.423Z] Response: ‘foo’ in 818ms
[2026-09-30T10:31:46.924Z] Pushing next message
[2026-09-30T10:31:47.024Z] Response: ‘foo’ in 601ms
[2026-09-30T10:31:47.525Z] Pushing next message
[2026-09-30T10:31:47.622Z] Response: ‘foo’ in 598ms
[2026-09-30T10:31:47.622Z] Result: true

Marketplace: Success
Logs:
[2026-09-30T10:31:43.056Z] Host: marketplace.cursorapi.com
[2026-09-30T10:31:44.224Z] Response in 1168ms
[2026-09-30T10:31:44.224Z] Response: 200
[2026-09-30T10:31:44.224Z] Response Type: cors
[2026-09-30T10:31:44.224Z] Server: null
[2026-09-30T10:31:44.224Z] Result: OK in 1168ms

Authentication: Success
Logs:
[2026-09-30T10:31:43.057Z] Host: prod.authentication.cursor.sh
[2026-09-30T10:31:44.562Z] Response: 200 in 1505ms

Authentication UI: Success
Logs:
[2026-09-30T10:31:43.063Z] DNS lookup: authenticator.cursor.sh
[2026-09-30T10:31:43.924Z] Resolved authenticator.cursor.sh to 172.64.152.23 in 82ms

Cursor Tab: Success
Logs:
[2026-09-30T10:31:43.063Z] DNS lookup: api3.cursor.sh
[2026-09-30T10:31:43.923Z] Resolved api3.cursor.sh to 104.18.19.125 in 68ms

Agent Endpoint: Success
Logs:
[2026-09-30T10:31:43.063Z] DNS lookup: agent.api5.cursor.sh
[2026-09-30T10:31:44.703Z] Resolved agent.api5.cursor.sh to 44.197.141.31 in 135ms

Downloads: Success
Logs:
[2026-09-30T10:31:43.057Z] Host: downloads.cursor.com
[2026-09-30T10:31:44.562Z] Response: 403 in 1505ms

CDN: Success
Logs:
[2026-09-30T10:31:43.057Z] Host: cursor-cdn.com
[2026-09-30T10:31:44.561Z] Response: 404 in 1504ms

Me also, extremly slow Grok responses! and Grok status websites shows “green”. how bizzare.

3afd003a-0b6d-4f7b-80f4-18d0c4b15c13

Hey all,

We’re aware of some slowness around the time of your report, which has been fixed. Sorry for the nuisance! Please give it another try.

Still happening.. just happened right now in a new chat:

e25bbad0-3c16-4c9e-9214-a04eb4b4b6b3

I can confirm it is a bit faster …

and yet … it is much slower then 2 weeks ago.

during 10/09 - 20/09 it was much faster then now.