Cursor outage history

We hold 150 Cursor incidents from Anysphere's status page, the newest from Nov 12, 2026. 60 of the 120 listed carry Anysphere's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 6d 9h since the last recorded problem.
Operational · 24h
100%
0 incidents · no downtime
288 checks
Operational · 7d
99.11%
1 incident · ≈1h 30m degraded
2015 checks
Operational · 30d
95.53%
25 incidents · ≈1d 8h degraded
8638 checks
Operational · since Jun 22, 2026
93.91%
100 incidents · ≈9d 2h degraded
43123 checks

% of our checks that found Cursor fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow
Past incidents

How Cursor fails

Since Jul 6, 2026, Anysphere's status page has marked 13 Cursor components as impaired, across 7,329 of our five-minute readings. Cloud Agents accounts for the most: 1,812 readings (about 151 hours) on 53 days, 110 of them marked as an outage rather than degraded, most recently on Nov 9, 2026. Next is IDE, with 1,496 readings on 51 days. We hold 150 Cursor incidents from Anysphere's status page, the earliest from Apr 2, 2026. Of the 106 that Anysphere closed with an end time, the median lasted 1 h 1 min.

ComponentOutageDegradedMaint.DaysLast
Cloud Agents1101702—53Nov 9, 2026
IDE1051391—51Nov 9, 2026
Automations1061332—44Nov 9, 2026
CLI61977—39Nov 9, 2026
Grok Bot61737—31Nov 12, 2026
Review Agents64161—12Oct 29, 2026
cursor.com33183—18Nov 12, 2026
Origin2888—5Oct 29, 2026

Incidents by month: Jun 2026: 10 · Jul 2026: 3 · Aug 2026: 24 · Sep 2026: 30 · Oct 2026: 33 · Nov 2026: 9

Counts are five-minute readings of Anysphere's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Every recorded incident

November 2026 · 9

October 2026 · 33

September 2026 · 30

August 2026 · 24

July 2026 · 3

And 30 older incidents, from before 2026-05-20. Each has its own dated page.

What cascades to Cursor

Cursor is built on 4 providers. When one of these has an incident, Cursor can degrade too.

Incidents and their updates are Anysphere's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Anysphere.