Is the Cursor.status actually correct?

Support Help
1

Although status.cursor.com says everything is ok at the moment, cursor.com and the dashboard won’t open! On the Cursor desktop, the agents are disconnected. It’s not a problem with my network, can someone explain what to do? Is it a problem with Cursor? Can someone please give me some feedback?

4

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.

8

I’m having the same problem logging into Cursor. I can’t access the dashboard, and my Cursor IDE won’t open any chats, telling me I’m not authorized. I’ve tried logging out and logging back in, but I still can’t access the dashboard to authorize it. However, the Cursor Status page still shows everything is normal.

9

Hey, we didn’t see any incident on our side at that time. Our synthetic monitors and backend logs looked normal, and we didn’t get other reports of a widespread outage in that window. This is most likely a local network issue like DNS, ISP, VPN, firewall, or a regional edge problem.

If it’s still happening now, try these one by one:

  1. Open cursor.com from a different network like a mobile hotspot or via VPN. If it works there, the issue is likely ISP or DNS.
  2. Change DNS to 1.1.1.1 or 8.8.8.8, then flush your DNS cache.
  3. In Cursor: Cursor Settings > Network > Run Diagnostics to see which endpoints are blocked.
  4. Sign out and log back in using Cmd/Ctrl+Shift+P > Sign Out. Also try turning off VPN or proxy while logging in.
  5. Check your corporate firewall or antivirus. Tools like Zscaler often block our domains.

@Francis_Alison if you’re seeing the same thing, please try the same steps and share your Run Diagnostics results plus your region and ISP. That’ll help us quickly confirm if this is local or regional.