Cursorstatus history & uptime
How reliable has Cursorbeen? We record a status check every few minutes and keep the history — uptime, recent incidents, and the upstream providers whose outages cascade here. We never invent numbers; where we're still collecting, we say so.
Uptime & history
Tracking since Jun 22, 2026% 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.
- Investigating service degradation - xAI modelsSep 29, 2026 · ongoing · identified
- Investigating service degradation — Cloud AgentsSep 29, 2026 · ongoing · monitoring
- Investigating service degradation — Grok BotSep 28, 2026 · ongoing · investigating
- Investigating service degradation — Grok BotSep 25, 2026 · ongoing · monitoring
- Investigating service degradation — Grok BotSep 25, 2026 · ongoing · monitoring
- Investigating service degradation - Grok 4.7Sep 23, 2026 · ongoing · monitoring
- Investigating — Cloud Agent Dockerfile BuildsSep 23, 2026 · ongoing · identified
- Investigating service degradation — Automations and Cloud Agents w/ Grok 4.7Sep 22, 2026 · ongoing · identified
- Investigating service degradationSep 21, 2026 · ongoing · investigating
- Investigating service degradationSep 21, 2026 · ongoing · investigating
- Sign-in and dashboard errors for some usersSep 18, 2026 · ongoing · monitoring
- Investigating service degradation — Grok BotSep 18, 2026 · ongoing · monitoring
What cascades to Cursor
Cursor is built on 4 providers. When one of these has an incident, Cursor often degrades too — frequently before its own status page admits it.
History is recorded from Cursor's official status plus our own independent checks. AIDownCheck is independent and not affiliated with Anysphere.