User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
cursor.com · AI
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests cursor.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 197 ms · 3 min ago.
No status feed
Cursor does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 168 ms | 0 |
| 11:45 | 0 | 0.0 | 284 ms | 0 |
| 12:00 | 0 | 0.0 | 216 ms | 0 |
| 12:15 | 0 | 0.0 | 172 ms | 0 |
| 12:30 | 0 | 0.0 | 141 ms | 0 |
| 12:45 | 0 | 0.0 | 144 ms | 0 |
| 13:00 | 0 | 0.0 | 207 ms | 0 |
| 13:15 | 0 | 0.0 | 194 ms | 0 |
| 13:30 | 0 | 0.0 | 363 ms | 0 |
| 13:45 | 0 | 0.0 | 247 ms | 0 |
| 14:00 | 0 | 0.0 | 207 ms | 0 |
| 14:15 | 0 | 0.0 | 226 ms | 0 |
| 14:30 | 0 | 0.0 | 193 ms | 0 |
| 14:45 | 0 | 0.0 | 275 ms | 0 |
| 15:00 | 0 | 0.0 | 293 ms | 0 |
| 15:15 | 0 | 0.0 | 179 ms | 0 |
| 15:30 | 0 | 0.0 | 151 ms | 0 |
| 15:45 | 0 | 0.0 | 138 ms | 0 |
| 16:00 | 0 | 0.0 | 204 ms | 0 |
| 16:15 | 0 | 0.0 | 175 ms | 0 |
| 16:30 | 0 | 0.0 | 232 ms | 0 |
| 16:45 | 0 | 0.0 | 184 ms | 0 |
| 17:00 | 0 | 0.0 | 197 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status badge · JSON
No outages on record for Cursor yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Cursor goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Checks are succeeding and user reports are near the baseline.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.