Network diangostics error

Network diagnostics error
Cursor Network Diagnostic Results

FAILED (7): DNS, HTTP/2, SSL, Authentication UI, Cursor Tab, Agent Endpoint, Codebase Indexing

DNS: Error: No response
Logs:
[2026-03-03T10:06:37.687Z] Error: Error: No response
[2026-03-03T10:06:37.691Z] Error: Error: No response
[2026-03-03T10:06:37.691Z] Error: Error: No response
[2026-03-03T10:06:37.691Z] Error: Error: No response
[2026-03-03T10:06:37.691Z] Error: Error: No response
[2026-03-03T10:06:37.691Z] Error: Error: No response
[2026-03-03T10:06:37.691Z] Error: Error: No response
[2026-03-03T10:06:37.691Z] Error: Error: No response
[2026-03-03T10:06:37.691Z] Result: Error: No response

HTTP/2: Error: No response
Logs:
[2026-03-03T10:06:37.686Z] Start

SSL: Error: No provider

API: Not run

Ping: Not run

Chat: Not run

Agent: Not run

Marketplace: Success
Logs:
[2026-03-03T10:06:37.676Z] Host:***
[2026-03-03T10:06:40.148Z] Response in 2472ms
[2026-03-03T10:06:40.148Z] Response: 200
[2026-03-03T10:06:40.148Z] Response Type: cors
[2026-03-03T10:06:40.148Z] Server: null
[2026-03-03T10:06:40.148Z] Result: OK in 2472ms

Authentication: Success
Logs:
[2026-03-03T10:06:37.677Z] Host: ***
[2026-03-03T10:06:40.468Z] Response: 200 in 2791ms

Authentication UI: Error: No response from DNS lookup
Logs:
[2026-03-03T10:06:37.687Z] DNS lookup: ***
[2026-03-03T10:06:37.688Z] Error: No response

Cursor Tab: Error: No response from DNS lookup
Logs:
[2026-03-03T10:06:37.687Z] DNS lookup: ***
[2026-03-03T10:06:37.689Z] Error: No response

Agent Endpoint: Error: No response from DNS lookup
Logs:
[2026-03-03T10:06:37.687Z] DNS lookup: ***
[2026-03-03T10:06:37.689Z] Error: No response

Codebase Indexing: Error: No response from DNS lookup
Logs:
[2026-03-03T10:06:37.687Z] DNS lookup: ***
[2026-03-03T10:06:37.690Z] Error: No response

Downloads: Success
Logs:
[2026-03-03T10:06:37.685Z] Host: ***
[2026-03-03T10:06:39.523Z] Response: 403 in 1838ms

CDN: Success
Logs:
[2026-03-03T10:06:37.686Z] Host: ***
[2026-03-03T10:06:38.332Z] Response: 404 in 646ms

Version 2.5.26
Windows 10

Hey, the diagnostics show an interesting pattern. Some domains resolve fine (marketplace, authentication, downloads, CDN), but others fail DNS lookups. This usually points to a local DNS or network issue.

Also, you’re on version 2.5.26, which is outdated. A similar issue was recently fixed just by updating: Network diagnostics issue.

Here’s what to try:

  1. Update Cursor
    Download the latest version from cursor.com/download.

  2. Flush DNS
    Run this in Command Prompt (as admin):

    ipconfig /flushdns
    
  3. Disable HTTP/2
    Cursor Settings > search “HTTP/2” > enable “Disable HTTP/2”

  4. Check for blockers
    Do you have a VPN, antivirus, or firewall running? These are the most common cause of partial DNS failures like this.

If the update alone doesn’t fix it, can you run these in Command Prompt and share the output?

nslookup authenticator.cursor.sh
nslookup api3.cursor.sh
nslookup prod.authentication.cursor.sh

This will tell us which domains your machine can’t resolve.