My chats are just hanging with "Planning next moves" and "Taking longer than expected..."

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In all my windows, cursor has stopped responding to my prompts. This is now almost 24 hours of this problem. My chats are just hanging with “Planning next moves” and “Taking longer than expected…” and then “Reconnecting”.
0. Monthly usage 21%, using composer/auto

  1. internet connection is fine
  2. I have wiped the caches (and lost all chat history)
  3. reloaded windows
  4. restarted the app
  5. checked for updates (none)

Steps to Reproduce

It is a permanent issue right now

Expected Behavior

I get a response

Screenshots / Screen Recordings

Screenshot 2026-04-04 at 10.08.22.png
Screenshot 2026-04-04 at 10.08.22.png3189×1740 453 KB

Operating System

MacOS

Version Information

Version: 3.0.9 (Universal)
VSCode Version: 1.105.1
Commit: 93e276db8a03af947eafb2d10241e2de17806c20
Date: 2026-04-03T02:06:46.446Z
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.2.0

For AI issues: which model did you use?

Composer 2. Auto.

Does this stop you from using Cursor

Yes - Cursor is unusable

Screenshot 2026-04-04 at 10.14.04
Screenshot 2026-04-04 at 10.14.043191×1740 395 KB

3 Likes
5

Same issue, but it eventually starts doing stuff but in slowmotion, a job that usually takes 3 minutes for it to fix have been taking +30 minutes

2 Likes
6

Hey, thanks for the detailed report. We can see a lot of requests from your side are failing on the server. This is on our end, not yours.

As a workaround for now, try switching from Auto to a specific model, like Claude 4.6 Sonnet or GPT-5, instead of Composer 2 Auto. This can sometimes bypass routing issues.

Also try:

  • Cursor Settings > Network > Run Diagnostics, then send the results here
  • Disable HTTP/2: Settings Cmd+, > search for HTTP/2 > turn on Disable HTTP/2

The team is aware of this issue. Let me know if the specific model workaround helped.

7

I have used all my API-usage for this payment period so i’ll just have to wait for you to solve the issue, thanks for the update :slight_smile:

9

I tried but I get this: “An error occurred: Sorry, new users can only put 2 links in a post.”

Here’s the error sections:

Cursor Network Diagnostic Results

FAILED (4): DNS, Ping, Chat, Agent

DNS: Error: DNS lookup took 1728ms
Logs:
[2026-04-04T09:25:26.054Z] Host: api2.cursor.sh
[2026-04-04T09:25:26.054Z] Servers: 192.168.0.5,10.20.254.4,8.8.4.4
[2026-04-04T09:25:26.054Z] Resolved to 3.90.75.202 in 16ms
[2026-04-04T09:25:27.790Z] Resolved to 3.90.75.202 in 1728ms
[2026-04-04T09:25:27.792Z] Resolved to 3.90.75.202 in 1ms
[2026-04-04T09:25:27.795Z] Resolved to 3.90.75.202 in 2ms
[2026-04-04T09:25:27.803Z] Host: api2.cursor.sh
[2026-04-04T09:25:27.803Z] Servers: system
[2026-04-04T09:25:27.803Z] Resolved to 3.90.75.202, 98.86.206.31, 44.206.88.252, 52.70.205.129, 3.217.208.76, 52.204.191.200, 34.235.197.189, 44.209.56.242 in 7ms
[2026-04-04T09:25:27.803Z] Resolved to 3.90.75.202, 98.86.206.31, 44.206.88.252, 52.70.205.129, 3.217.208.76, 52.204.191.200, 34.235.197.189, 44.209.56.242 in 0ms
[2026-04-04T09:25:27.803Z] Resolved to 3.90.75.202, 98.86.206.31, 44.206.88.252, 52.70.205.129, 3.217.208.76, 52.204.191.200, 34.235.197.189, 44.209.56.242 in 0ms
[2026-04-04T09:25:27.803Z] Resolved to 3.90.75.202, 98.86.206.31, 44.206.88.252, 52.70.205.129, 3.217.208.76, 52.204.191.200, 34.235.197.189, 44.209.56.242 in 0ms
[2026-04-04T09:25:27.803Z] Result: Error: DNS lookup took 1728ms

Ping: Error: Response took 1031ms
Logs:
[2026-04-04T09:25:26.004Z] Sending ping 1
[2026-04-04T09:25:31.590Z] Response: ‘ping’ in 5586ms
[2026-04-04T09:25:31.590Z] Sending ping 2
[2026-04-04T09:25:32.599Z] Response: ‘ping’ in 1009ms
[2026-04-04T09:25:32.599Z] Sending ping 3
[2026-04-04T09:25:33.630Z] Response: ‘ping’ in 1031ms
[2026-04-04T09:25:33.630Z] Sending ping 4
[2026-04-04T09:25:34.691Z] Response: ‘ping’ in 1061ms
[2026-04-04T09:25:34.691Z] Sending ping 5
[2026-04-04T09:25:35.722Z] Response: ‘ping’ in 1031ms
[2026-04-04T09:25:35.722Z] Result: Error: Response took 1031ms

Chat: Error: Streaming responses are being buffered by a proxy in your network environment
Logs:
[2026-04-04T09:25:26.005Z] Starting stream
[2026-04-04T09:25:31.533Z] Response: ‘foo’ in 5519ms
[2026-04-04T09:25:32.538Z] Response: ‘foo’ in 1005ms
[2026-04-04T09:25:33.563Z] Response: ‘foo’ in 1025ms
[2026-04-04T09:25:34.564Z] Response: ‘foo’ in 1001ms
[2026-04-04T09:25:35.711Z] Response: ‘foo’ in 1147ms
[2026-04-04T09:25:36.681Z] Result: Error: Streaming responses are being buffered by a proxy in your network environment

Agent: Error: Bidirectional streaming is not supported by the http2 proxy in your network environment
Logs:
[2026-04-04T09:25:26.014Z] Starting stream
[2026-04-04T09:25:26.014Z] Pushing first message
[2026-04-04T09:25:31.609Z] Response: ‘foo’ in 5595ms
[2026-04-04T09:25:32.110Z] Pushing next message
[2026-04-04T09:25:32.518Z] Response: ‘foo’ in 909ms
[2026-04-04T09:25:33.019Z] Pushing next message
[2026-04-04T09:25:34.226Z] Response: ‘foo’ in 1708ms
[2026-04-04T09:25:34.727Z] Pushing next message
[2026-04-04T09:25:35.114Z] Response: ‘foo’ in 888ms
[2026-04-04T09:25:35.614Z] Pushing next message
[2026-04-04T09:25:35.981Z] Response: ‘foo’ in 867ms
[2026-04-04T09:25:35.982Z] Result: Error: Bidirectional streaming is not supported by the http2 proxy in your network environment

10

Composer 2 has been removed from the list. Will it be back sometime soon?

11

The diagnostics results speak for themselves. Your network has a proxy that blocks bidirectional streaming, which the Agent needs. Key errors:

  • Agent: “Bidirectional streaming is not supported by the http2 proxy in your network environment”
  • Chat: “Streaming responses are being buffered by a proxy”

Main workaround is to disable HTTP/2. If you haven’t enabled this setting yet:

  1. Open Settings Cmd+,
  2. Search for HTTP/2
  3. Turn on Disable HTTP/2
  4. Restart Cursor

This should switch to HTTP/1.1 and work around the proxy issue. After that, run diagnostics again via Cursor Settings > Network > Run Diagnostics and the results should look better.

About Composer 2, which models do you currently see in your model picker? Is Auto still there? For now, try using a specific model directly like Claude 4.6 Sonnet or GPT-5.

Let me know if disabling HTTP/2 helped.

12

I had the same problem with the chat just hanging. Turned off auto, reverted to Composer 2 and it all works fine now.

13

I changed to HTTP/1.1, but still getting those errors (see below). This is a mystery as nothing has been changed on my side - this problem started out of nowhere.

The agent is responding again intermittently, so better than nothing.

14

Good that the agent has started responding at least intermittently, it means disabling HTTP/2 helped a bit.

But if you’re still seeing errors, let’s check a few things:

  1. Make sure Cursor was fully restarted after turning on Disable HTTP/2. Not just Reload Window, fully quit and open it again.
  2. Run diagnostics again via Cursor Settings > Network > Run Diagnostics and paste the results here. We need to see if the errors changed after the switch.

Another option is to try using a VPN. Based on the diagnostics, there’s a proxy in your network that buffers streaming connections. If that proxy is on your ISP side, a VPN can bypass it.

For the model, use a specific model like Claude 4.6 Sonnet or GPT-5 instead of Auto, as @Wayleigh confirmed above.

Let me know what the new diagnostics show.

15

Seem to be having the same problem with coding sessions timing out, being completely unreliable under composer 2.0, but my situation is I am in the web browser (web agent). I’m not using cursor on my local machine.

Screenshot 2026-04-04 at 1.01.39 PM
Screenshot 2026-04-04 at 1.01.39 PM1476×766 7.66 KB

16

Oh and then it times out … Agent encountered an error

Screenshot 2026-04-04 at 4.12.59 PM
Screenshot 2026-04-04 at 4.12.59 PM1516×490 14 KB

17

Me too i have this issues, can’t work with this!

image
image315×122 1.86 KB

18

Im also having the same issue in most of my agents

image
image832×133 13.7 KB

21

Hey, I see a screenshot with “Agent Execution Timed Out.” I’ll need a bit more info to debug:

  1. What OS are you on, and what Cursor version? Help > About
  2. Are you using Remote SSH or running locally?
  3. Is this happening all the time, or only sometimes?
  4. Please run Cursor Settings > Network > Run Diagnostics and paste the results here.

Also try this:

  • Settings Cmd/Ctrl + , > search for HTTP/2 > enable Disable HTTP/2, then fully restart Cursor. Not Reload Window, a full quit and reopen
  • Switch from Auto to a specific model, like Claude 4.6 Sonnet or GPT-5

Let me know how it goes.

22
  1. image
    image279×387 26 KB
  2. Running locally
  3. Its mainly happening in worktree mode

Network Diagnostics

Cursor Network Diagnostic Results

DNS: Success
Logs:
  [2026-04-06T12:45:23.644Z] Host: api2.cursor.sh
  [2026-04-06T12:45:23.644Z] Servers: 192.168.13.1
  [2026-04-06T12:45:23.644Z] Resolved to 98.94.122.138 in 27ms
  [2026-04-06T12:45:24.178Z] Resolved to 44.209.34.209 in 533ms
  [2026-04-06T12:45:24.182Z] Resolved to 44.209.34.209 in 4ms
  [2026-04-06T12:45:24.187Z] Resolved to 44.209.34.209 in 5ms
  [2026-04-06T12:45:24.190Z] Host: api2.cursor.sh
  [2026-04-06T12:45:24.190Z] Servers: system
  [2026-04-06T12:45:24.190Z] Resolved to 44.209.34.209, 98.90.237.240, 98.95.122.213, 100.50.81.127, 44.196.72.42, 52.22.233.8, 44.218.160.42, 18.211.46.118 in 3ms
  [2026-04-06T12:45:24.190Z] Resolved to 44.209.34.209, 98.90.237.240, 98.95.122.213, 100.50.81.127, 44.196.72.42, 52.22.233.8, 44.218.160.42, 18.211.46.118 in 0ms
  [2026-04-06T12:45:24.190Z] Resolved to 44.209.34.209, 98.90.237.240, 98.95.122.213, 100.50.81.127, 44.196.72.42, 52.22.233.8, 44.218.160.42, 18.211.46.118 in 0ms
  [2026-04-06T12:45:24.191Z] Resolved to 44.209.34.209, 98.90.237.240, 98.95.122.213, 100.50.81.127, 44.196.72.42, 52.22.233.8, 44.218.160.42, 18.211.46.118 in 0ms
  [2026-04-06T12:45:24.191Z] Result: true

HTTP/2: Success
Logs:
  [2026-04-06T12:45:23.616Z] Start
  [2026-04-06T12:45:23.977Z] Host: api2.cursor.sh
  [2026-04-06T12:45:23.977Z] Protocol: h2
  [2026-04-06T12:45:23.977Z] Result: true in 361ms

SSL: Success
Logs:
  [2026-04-06T12:45:23.616Z] Start
  [2026-04-06T12:45:24.111Z] URL: https://api2.cursor.sh/
  [2026-04-06T12:45:24.111Z] Status: 200
  [2026-04-06T12:45:24.111Z] IP: 98.94.122.138
  [2026-04-06T12:45:24.111Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
  [2026-04-06T12:45:24.112Z] Name: api2.cursor.sh
  [2026-04-06T12:45:24.112Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
  [2026-04-06T12:45:24.112Z] DNS Time: 3ms
  [2026-04-06T12:45:24.112Z] Connect Time: 173ms
  [2026-04-06T12:45:24.112Z] TLS Time: 159ms
  [2026-04-06T12:45:24.112Z] Result: true in 496ms

API: Success
Logs:
  [2026-04-06T12:45:23.617Z] Start
  [2026-04-06T12:45:25.530Z] Result: true

Ping: Success
Logs:
  [2026-04-06T12:45:23.618Z] Sending ping 1
  [2026-04-06T12:45:25.548Z] Response: 'ping' in 1930ms
  [2026-04-06T12:45:25.548Z] Sending ping 2
  [2026-04-06T12:45:25.904Z] Response: 'ping' in 356ms
  [2026-04-06T12:45:25.904Z] Sending ping 3
  [2026-04-06T12:45:26.083Z] Response: 'ping' in 179ms
  [2026-04-06T12:45:26.083Z] Sending ping 4
  [2026-04-06T12:45:26.448Z] Response: 'ping' in 365ms
  [2026-04-06T12:45:26.448Z] Sending ping 5
  [2026-04-06T12:45:26.624Z] Response: 'ping' in 176ms
  [2026-04-06T12:45:26.624Z] Result: true

Chat: Success
Logs:
  [2026-04-06T12:45:23.618Z] Starting stream
  [2026-04-06T12:45:25.529Z] Response: 'foo' in 1910ms
  [2026-04-06T12:45:26.581Z] Response: 'foo' in 1052ms
  [2026-04-06T12:45:27.538Z] Response: 'foo' in 957ms
  [2026-04-06T12:45:28.691Z] Response: 'foo' in 1153ms
  [2026-04-06T12:45:29.538Z] Response: 'foo' in 847ms
  [2026-04-06T12:45:30.533Z] Result: true

Agent: Success
Logs:
  [2026-04-06T12:45:23.619Z] Starting stream
  [2026-04-06T12:45:23.619Z] Pushing first message
  [2026-04-06T12:45:25.571Z] Response: 'foo' in 1952ms
  [2026-04-06T12:45:26.072Z] Pushing next message
  [2026-04-06T12:45:26.154Z] Response: 'foo' in 583ms
  [2026-04-06T12:45:26.654Z] Pushing next message
  [2026-04-06T12:45:26.739Z] Response: 'foo' in 585ms
  [2026-04-06T12:45:27.240Z] Pushing next message
  [2026-04-06T12:45:27.323Z] Response: 'foo' in 584ms
  [2026-04-06T12:45:27.823Z] Pushing next message
  [2026-04-06T12:45:27.906Z] Response: 'foo' in 583ms
  [2026-04-06T12:45:27.906Z] Result: true

Marketplace: Success
Logs:
  [2026-04-06T12:45:23.611Z] Host: marketplace.cursorapi.com
  [2026-04-06T12:45:23.803Z] Response in 192ms
  [2026-04-06T12:45:23.803Z] Response: 200 
  [2026-04-06T12:45:23.803Z] Response Type: cors
  [2026-04-06T12:45:23.803Z] Server: null
  [2026-04-06T12:45:23.803Z] Result: OK in 192ms

Authentication: Success
Logs:
  [2026-04-06T12:45:23.613Z] Host: prod.authentication.cursor.sh
  [2026-04-06T12:45:24.512Z] Response: 200  in 899ms

Authentication UI: Success
Logs:
  [2026-04-06T12:45:23.616Z] DNS lookup: authenticator.cursor.sh
  [2026-04-06T12:45:23.741Z] Resolved authenticator.cursor.sh to 172.64.152.23 in 120ms

Cursor Tab: Success
Logs:
  [2026-04-06T12:45:23.616Z] DNS lookup: api3.cursor.sh
  [2026-04-06T12:45:23.716Z] Resolved api3.cursor.sh to 104.18.18.125 in 95ms

Agent Endpoint: Success
Logs:
  [2026-04-06T12:45:23.616Z] DNS lookup: agent.api5.cursor.sh
  [2026-04-06T12:45:23.956Z] Resolved agent.api5.cursor.sh to 44.197.141.31 in 335ms

Codebase Indexing: Success
Logs:
  [2026-04-06T12:45:23.616Z] DNS lookup: repo42.cursor.sh
  [2026-04-06T12:45:23.957Z] Resolved repo42.cursor.sh to 54.161.233.146 in 334ms

Downloads: Success
Logs:
  [2026-04-06T12:45:23.615Z] Host: downloads.cursor.com
  [2026-04-06T12:45:24.101Z] Response: 403  in 486ms

CDN: Success
Logs:
  [2026-04-06T12:45:23.616Z] Host: cursor-cdn.com
  [2026-04-06T12:45:23.954Z] Response: 404  in 338ms
23

Thanks for the info. Your diagnostics are completely clean and your network looks fine, so the issue is most likely not on your side.

It’s interesting that this only happens in worktree mode. A couple of questions:

  1. Does it reproduce in normal mode without worktree?
  2. Which model are you using, Auto or a specific one?
  3. Can you share the Request ID from the stuck request? In the chat, click the context menu in the top right corner > Copy Request ID.

As a workaround, try switching from Auto to a specific model like Claude 4.6 Sonnet or GPT-5, and check if it still hangs outside worktree.

The team is aware of agent hanging issues. Your report helps us prioritize, especially since it seems tied to worktree mode.

24
  1. Normal mode works fine without issues
  2. Im using Opus 4.6 with High thinking and 1M Context window
  3. The request ID: b0411b71-4525-4440-8702-6fec68b0f3da
1 Like
25

same issue, auto hangs up badly… switched to http/2 no improvement - this is cyclical ive noticed it occurs about every 3-4 hours of coding.

Cursor Network Diagnostic Results

DNS: Success
Logs:
[2026-04-06T19:11:00.099Z] Host: api2.cursor.sh
[2026-04-06T19:11:00.099Z] Servers: 127.0.0.1
[2026-04-06T19:11:00.099Z] Resolved to 44.199.105.94 in 52ms
[2026-04-06T19:11:00.521Z] Resolved to 44.199.105.94 in 421ms
[2026-04-06T19:11:00.522Z] Resolved to 44.199.105.94 in 0ms
[2026-04-06T19:11:00.522Z] Resolved to 44.199.105.94 in 0ms
[2026-04-06T19:11:00.525Z] Host: api2.cursor.sh
[2026-04-06T19:11:00.525Z] Servers: system
[2026-04-06T19:11:00.525Z] Resolved to 44.199.105.94, 98.84.210.115, 54.144.78.98, 32.195.192.78, 23.21.41.17, 3.224.138.163, 34.198.194.111, 100.52.56.189 in 2ms
[2026-04-06T19:11:00.525Z] Resolved to 44.199.105.94, 98.84.210.115, 54.144.78.98, 32.195.192.78, 23.21.41.17, 3.224.138.163, 34.198.194.111, 100.52.56.189 in 0ms
[2026-04-06T19:11:00.525Z] Resolved to 44.199.105.94, 98.84.210.115, 54.144.78.98, 32.195.192.78, 23.21.41.17, 3.224.138.163, 34.198.194.111, 100.52.56.189 in 0ms
[2026-04-06T19:11:00.526Z] Resolved to 44.199.105.94, 98.84.210.115, 54.144.78.98, 32.195.192.78, 23.21.41.17, 3.224.138.163, 34.198.194.111, 100.52.56.189 in 0ms
[2026-04-06T19:11:00.526Z] Result: true

HTTP/2: Success
Logs:
[2026-04-06T19:11:00.047Z] Start
[2026-04-06T19:11:00.189Z] Host: api2.cursor.sh
[2026-04-06T19:11:00.189Z] Protocol: h2
[2026-04-06T19:11:00.189Z] Result: true in 142ms

SSL: Success
Logs:
[2026-04-06T19:11:00.047Z] Start
[2026-04-06T19:11:00.220Z] URL: https://api2.cursor.sh/
[2026-04-06T19:11:00.220Z] Status: 200
[2026-04-06T19:11:00.220Z] IP: 44.199.105.94
[2026-04-06T19:11:00.220Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-04-06T19:11:00.220Z] Name: api2.cursor.sh
[2026-04-06T19:11:00.220Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-04-06T19:11:00.220Z] DNS Time: 5ms
[2026-04-06T19:11:00.220Z] Connect Time: 76ms
[2026-04-06T19:11:00.220Z] TLS Time: 55ms
[2026-04-06T19:11:00.220Z] Result: true in 173ms

API: Success
Logs:
[2026-04-06T19:11:00.048Z] Start
[2026-04-06T19:11:00.632Z] Result: true

Ping: Success
Logs:
[2026-04-06T19:11:00.048Z] Sending ping 1
[2026-04-06T19:11:00.643Z] Response: ‘ping’ in 595ms
[2026-04-06T19:11:00.643Z] Sending ping 2
[2026-04-06T19:11:00.706Z] Response: ‘ping’ in 63ms
[2026-04-06T19:11:00.706Z] Sending ping 3
[2026-04-06T19:11:00.754Z] Response: ‘ping’ in 48ms
[2026-04-06T19:11:00.754Z] Sending ping 4
[2026-04-06T19:11:01.065Z] Response: ‘ping’ in 311ms
[2026-04-06T19:11:01.065Z] Sending ping 5
[2026-04-06T19:11:01.111Z] Response: ‘ping’ in 46ms
[2026-04-06T19:11:01.111Z] Result: true

Chat: Success
Logs:
[2026-04-06T19:11:00.049Z] Starting stream
[2026-04-06T19:11:01.062Z] Response: ‘foo’ in 1012ms
[2026-04-06T19:11:02.211Z] Response: ‘foo’ in 1149ms
[2026-04-06T19:11:03.097Z] Response: ‘foo’ in 886ms
[2026-04-06T19:11:04.121Z] Response: ‘foo’ in 1024ms
[2026-04-06T19:11:05.160Z] Response: ‘foo’ in 1039ms
[2026-04-06T19:11:06.137Z] Result: true

Agent: Success
Logs:
[2026-04-06T19:11:00.049Z] Starting stream
[2026-04-06T19:11:00.050Z] Pushing first message
[2026-04-06T19:11:00.141Z] Response: ‘foo’ in 91ms
[2026-04-06T19:11:00.643Z] Pushing next message
[2026-04-06T19:11:00.712Z] Response: ‘foo’ in 571ms
[2026-04-06T19:11:01.222Z] Pushing next message
[2026-04-06T19:11:01.266Z] Response: ‘foo’ in 554ms
[2026-04-06T19:11:01.770Z] Pushing next message
[2026-04-06T19:11:01.824Z] Response: ‘foo’ in 558ms
[2026-04-06T19:11:02.334Z] Pushing next message
[2026-04-06T19:11:02.446Z] Response: ‘foo’ in 622ms
[2026-04-06T19:11:02.446Z] Result: true

Marketplace: Success
Logs:
[2026-04-06T19:11:00.044Z] Host: marketplace.cursorapi.com
[2026-04-06T19:11:00.364Z] Response in 320ms
[2026-04-06T19:11:00.364Z] Response: 200
[2026-04-06T19:11:00.364Z] Response Type: cors
[2026-04-06T19:11:00.364Z] Server: null
[2026-04-06T19:11:00.364Z] Result: OK in 320ms

Authentication: Success
Logs:
[2026-04-06T19:11:00.045Z] Host: prod.authentication.cursor.sh
[2026-04-06T19:11:00.277Z] Response: 200 in 232ms

Authentication UI: Success
Logs:
[2026-04-06T19:11:00.047Z] DNS lookup: authenticator.cursor.sh
[2026-04-06T19:11:00.338Z] Resolved authenticator.cursor.sh to 104.18.35.233 in 281ms

Cursor Tab: Success
Logs:
[2026-04-06T19:11:00.047Z] DNS lookup: api3.cursor.sh
[2026-04-06T19:11:00.141Z] Resolved api3.cursor.sh to 104.18.18.125 in 87ms

Agent Endpoint: Success
Logs:
[2026-04-06T19:11:00.047Z] DNS lookup: agent.api5.cursor.sh
[2026-04-06T19:11:00.300Z] Resolved agent.api5.cursor.sh to 100.30.166.181 in 236ms

Codebase Indexing: Success
Logs:
[2026-04-06T19:11:00.047Z] DNS lookup: repo42.cursor.sh
[2026-04-06T19:11:00.339Z] Resolved repo42.cursor.sh to 54.161.233.146 in 281ms

Downloads: Success
Logs:
[2026-04-06T19:11:00.047Z] Host: downloads.cursor.com
[2026-04-06T19:11:00.413Z] Response: 403 in 366ms

CDN: Success
Logs:
[2026-04-06T19:11:00.047Z] Host: cursor-cdn.com
[2026-04-06T19:11:00.428Z] Response: 404 in 381ms