Is Cursor down?
No, Cursor is up right now
Both signals agree: the official status feed and our own check.
Request to cursor.com, 3 min ago. 288 of 288 checks in the last 24 hours succeeded, median 110 ms.
Is Cursor working for you?
One click, no account. It helps others see whether the problem is widespread.
Response time, last 24 hours
measured from our server in GermanyWorks for everyone else? Fix it on your side
- Check whether it is only this device. Open the service on your phone using mobile data instead of Wi-Fi. If it works there, the problem is your home network or this computer, not the service.
- Test from the command line. Check name resolution and the route, to see where the connection stops.
nslookup cursor.com tracert cursor.com - Check your tokens and rate limits. An expired token or a rate limit returns errors that look like an outage. Read the exact HTTP status code and message before assuming the service is down.
- Restart the router and the device. Unplug the router for 30 seconds, plug it back in, wait until it is online again, then restart the computer. This clears stuck connections and gives you a fresh route to the service.
- Flush the DNS cache. Windows may still remember an old address for the service. Open Command Prompt as administrator and run the command below, then try again.
ipconfig /flushdns - Turn off VPN and proxy for a moment. VPN exit servers are often rate-limited or blocked. Disconnect the VPN, and in Settings > Network & internet > Proxy make sure no manual proxy is set.
- Change the DNS server. If the name still does not resolve, switch DNS in Settings > Network & internet > your connection > DNS server assignment to a public resolver such as 1.1.1.1 or 8.8.8.8.
Recent incidents
from the official feed, read 26 min agoThis incident has been resolved. Grok models in Cursor are working normally again.
Between 10:52 AM and 1:29 PM PT on October 13, many Grok Bot routines started by webhooks, Slack, git, email and Linear events didn't run. Webhook callers may have seen an HTTP 400 "Automation run rate limit exceeded" error, and other triggers failed without an error. Your own usage didn't cause this. Routines are run…
This incident has been resolved. New Cloud Agents and Grok Bot sessions are starting normally again.
Questions and experiences
Ask about this page: members and our editors answer. Reading is open; writing needs a free account.
…