Is Cursor down right now?
Live status for cursor.com isn't set up in this environment yet - check any URL manually instead.
Checking cursor.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
About Cursor outages
Written by the HostTracker monitoring team · updated from live probe data.
Cursor is an AI-powered code editor built on top of familiar editing tools, with its AI features - chat, inline edits, autocomplete - running through its own backend at api2.cursor.sh rather than purely on the model it happens to be using for a given request. That layering means an outage can originate in more than one place: Cursor's own request-handling infrastructure, or the specific upstream model provider it's routing a request to at that moment. The editor itself keeps working as a text editor even when the AI layer is unreachable, which can mask a real incident - files open and save normally while chat and inline suggestions quietly stop responding, so the AI features failing isn't always obvious from the interface alone.
Common causes of Cursor downtime
Incidents at the upstream model providers Cursor routes requests to, which can degrade AI features without any problem in Cursor's own infrastructure
Request queueing at peak hours, when heavy demand for chat and inline completions produces slow responses or timeouts rather than a clean failure
Authentication problems that block sign-in to a Cursor account while the editor itself continues to function as a plain code editor
Extension and editor updates that temporarily break the connection between the client and its backend until the update completes
Not sure whether it's Cursor or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Other services we track
HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests cursor.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than Cursor being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
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.
Run the live check at the top of this page - it tests cursor.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Cursor is reachable for everyone or only failing for you.
Run the live check at the top of this page - it tests cursor.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Cursor is reachable for everyone or only failing for you.
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.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.