Is Cursor down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

No - as of the most recent check, cursor.com is responding normally to HostTracker's monitoring network, and has been up for 21d 7h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, cursor.com is responding normally to HostTracker's monitoring network, and has been up for 21d 7h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, cursor.com is responding normally to HostTracker's monitoring network, and has been up for 21d 7h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

Very likely, and it's a distinctive pattern for Cursor specifically. Because Cursor is a full code editor with AI features layered on top rather than an AI tool with an editor attached, the base editing experience - opening, editing and saving files - keeps working even when the AI backend is down. So a silent AI layer with a perfectly normal editor around it is exactly what a backend incident looks like from the user's side, not evidence that the problem is local to your setup.

Not always. Cursor's AI features are served through its own backend at api2.cursor.sh, which in turn calls out to the model providers behind chat and completions, so a failure can sit in either layer. If a specific model or feature is failing while others in Cursor work fine, the fault is more likely upstream; if everything AI-related stops at once across different models, that points at Cursor's own infrastructure. This page checks cursor.com's reachability, a useful signal either way.

Heavy simultaneous demand for chat and inline completions can queue requests at Cursor's backend during peak hours, producing longer waits or occasional timeouts without the service being fully unreachable. This is ordinary load behaviour rather than a fault and tends to ease outside busy periods. Persistent failures that don't improve, or a complete lack of response over an extended stretch, are more likely a genuine incident worth checking against a live status result.