It stopped working; it just keeps thinking

esses são os erros

Cursor Network Diagnostic Results

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

SSL: Error: No response after 60s
Logs:
[2026-10-19T21:59:05.432Z] Start
[2026-10-19T22:00:05.424Z] Result: no response after 60s

Ping: Error: No response after 60s
Logs:
[2026-10-19T21:59:05.433Z] Sending ping 1
[2026-10-19T22:00:05.424Z] Result: no response after 60s

Chat: Error: [aborted] read ECONNRESET
Logs:
[2026-10-19T21:59:05.433Z] Starting streamSSE
[2026-10-19T21:59:45.754Z] Error: ConnectError: [aborted] read ECONNRESET

Agent: Error: No response after 60s
Logs:
[2026-10-19T21:59:05.433Z] Starting stream
[2026-10-19T21:59:05.436Z] Pushing first message
[2026-10-19T21:59:10.114Z] Response: ‘foo’ in 4678ms
[2026-10-19T21:59:10.616Z] Pushing next message
[2026-10-19T21:59:27.943Z] Response: ‘foo’ in 17829ms
[2026-10-19T21:59:28.443Z] Pushing next message
[2026-10-19T22:00:05.424Z] Result: no response after 60s

Hi,

Thanks for posting on the Cursor forum!

To help ensure most of our users can participate in discussions, this forum is currently English only.

If you’d like, you can edit your post to translate it into English. Once it meets our guidelines, it will be automatically relisted.

Thanks for understanding!

Note: This is an automated detection system and sometimes makes mistakes. If your post is already in English, feel free to ignore this message, or just make a small edit and it will be reviewed again.

these are the errors

Cursor Network Diagnostic Results

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

SSL: Error: No response after 60s
Logs:
[2026-10-19T21:59:05.432Z] Start
[2026-10-19T22:00:05.424Z] Result: no response after 60s

Ping: Error: No response after 60s
Logs:
[2026-10-19T21:59:05.433Z] Sending ping 1
[2026-10-19T22:00:05.424Z] Result: no response after 60s

Chat: Error: [aborted] read ECONNRESET
Logs:
[2026-10-19T21:59:05.433Z] Starting streamSSE
[2026-10-19T21:59:45.754Z] Error: ConnectError: [aborted] read ECONNRESET

Agent: Error: No response after 60s
Logs:
[2026-10-19T21:59:05.433Z] Starting stream
[2026-10-19T21:59:05.436Z] Pushing first message
[2026-10-19T21:59:10.114Z] Response: ‘foo’ in 4678ms
[2026-10-19T21:59:10.616Z] Pushing next message
[2026-10-19T21:59:27.943Z] Response: ‘foo’ in 17829ms
[2026-10-19T21:59:28.443Z] Pushing next message
[2026-10-19T22:00:05.424Z] Result: no response after 60s

Hey @Adriel_F, thanks for sharing the diagnostics.

Your results show the connection from your network to Cursor’s servers is timing out: DNS works, but the secure connection never finishes within 60 seconds and the responses that do get through take 5 to 18 seconds. Cursor itself is working normally for other users right now, including in Brazil, so this points to something on the network path between your computer and Cursor (internet provider, router, VPN, or a firewall/antivirus that inspects HTTPS).

Could you try these, in order:

  1. Restart your router/modem, then fully quit and reopen Cursor.
  2. If you use a VPN, proxy, or an antivirus with “HTTPS scanning” / “web protection”, turn it off temporarily.
  3. In Cursor Settings → Network, set HTTP Compatibility Mode to HTTP/2 (your diagnostics show it on HTTP/1.1 in that window), then restart Cursor.
  4. Connect your computer to a different network, for example your phone’s mobile hotspot.
  5. Open Cursor Settings → Network and click Run Diagnostic again.

Please reply with the new diagnostic results and tell me whether Cursor works on the other network. If it works on the hotspot but not at home, the problem is with your internet provider’s connection, and it’s worth contacting them with these results.