Cursor logo

Is Cursor Down?

SaaSLive status, outages, and incident history

No. Cursor is up right now.

Every monitored Cursor system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 16m agoLive · 60s while moving

Know the moment Cursor breaks

Cursor is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Cursor status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Cursor Component Status

The main Cursor systems on this page. All 8 are operational right now.

8operational
Automations
Operational
CLI
Operational
Cloud Agents
Operational

5 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking cursor.com, Grok Bot, IDE, Origin, Review Agents.

See all of them free

Component statuses may change independently during partial outages.

Recent Cursor Outages & Incidents

Incident history from the official Cursor status page, including resolution updates.

Investigating service degradation — Grok BotResolved Sep 25, 2026 · 1h 34mResolved

The service degradation affecting Grok Bot has been resolved. --- [2026-09-25T05:52:23.688Z] (monitoring) We have identified the cause and are deploying a fix. We are monitoring recovery as the fix rolls out. Some Grok Bot computers may remain temporarily unavailable or unable to be created or reset during this time. --- [2026-09-25T05:17:29.591Z] (investigating) We are investigating a service degradation affecting Grok Bot. Grok Bot computers may temporarily not be able to be created, reached, or reset.

Investigating service degradation - Grok 4.7Resolved Sep 23, 2026 · 8 minResolved

This incident has been resolved. --- [2026-09-23T20:31:44.964Z] (monitoring) A fix has been implemented and we are monitoring for service restoration. --- [2026-09-23T20:28:02.185Z] (investigating) We are investigating degraded performance for requests that use Grok 4.7.

Investigating — Cloud Agent Dockerfile BuildsResolved Sep 23, 2026 · 1h 29mResolved

This incident has been resolved. --- [2026-09-23T18:39:34.642Z] (monitoring) A fix has been implemented and we are monitoring for service restoration. --- [2026-09-23T17:15:30.022Z] (identified) The root cause has been identified and a fix is being implemented. --- [2026-09-23T17:14:16.610Z] (investigating) Customers using Cloud Agents with Dockerfile-based builds may be unable to create new builds. Existing Cloud Agents continue to run on their current image; only new Dockerfile builds are affected.

Cursor Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Cursor incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 899.95% average · 27 days with incidentsSep 25

Live Cursor Outage Reports

Problems reported by engineers using Cursor. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Cursor problems reported yet.

Something wrong with Cursor on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Cursor

Is Cursor down? Cursor reports live availability for 6 components at status.cursor.com, among them Automations, Bugbot and CLI. Track Cursor outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Cursor uptime at 99.37%. Response times, incident history, and SLA tracking for Cursor are available on the PulsAPI dashboard.

Cursor Status FAQ

Is Cursor down right now?

The verdict at the top of this page comes from the latest poll of the official Cursor status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Cursor is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Cursor recovers.

How do I check Cursor uptime history?

PulsAPI tracks Cursor uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.37%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Cursor changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Cursor outages?

PulsAPI reads the official Cursor status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Cursor components?

Yes. PulsAPI monitors 8 individual Cursor components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Cursor goes down?

Yes. Create a free account and subscribe to Cursor: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Cursor to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Cursor problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Cursor?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Cursor plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Cursor with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services