Cursor.com is down | cursor status says not?

[STF (Stefan)]

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

On down detector, or cursor.status I cannot see any reported issues, however I cannot access it, i even tried on different browsers.

Steps to Reproduce

Open https://cursor.com/ with no cache.
Maybe DNS its not fully propagated in Europe after an update?

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20 (user setup)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report. It seems like a local issue with accessing cursor.com rather than a global outage - status.cursor.com shows operational, and there are no mass complaints on downdetector.

In the meantime, try:

• Change DNS to Google (8.8.8.8) or Cloudflare (1.1.1.1) - often helps with DNS issues
• Clear DNS cache: sudo dscacheutil -flushcache
• Try using a VPN or mobile internet to check

To help troubleshoot:

1. What error message are you seeing (timeout, DNS error, connection refused)?
2. Is the Cursor IDE application itself working if already installed?
3. Result of the nslookup cursor.com command in the terminal?

If the issue persists after changing DNS, please share the results of the checks.

[STF (Stefan)]

nslookup works fine: cursor.com → 76.76.21.21
ping 76.76.21.21: 100% packet loss
tracert shows packets dying at hop 8-9 (amazon.mix-it.net)

Packets successfully reach Milan Internet Exchange (MIX-IT)
but are dropped when entering Amazon’s network at 217.29.66.74.

Probably its a Amazon/Vercel routing problem, Im going to try a VPN.