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 — Automations, Cloud Agents, and IDEAug 11, 2026 · ongoing · investigating
- MCP authentication failures in Automations and Cloud AgentsAug 7, 2026 · ongoing · identified
- Degraded Performance for Grok 4.5Aug 6, 2026 · ongoing · monitoring
- Incorrect Usage Amount on DashboardJul 8, 2026 · ongoing · investigating
- Degraded Performance for Anthropic ModelsJul 7, 2026 · ongoing · investigating
- Investigating service degradationJul 6, 2026 · ongoing · investigating
- Elevated errors across Anthropic modelsJun 23, 2026 · ongoing · monitoring
- Investigating service degradation — AutomationsJun 22, 2026 → Jun 22, 2026 · resolved
- Degraded Performance for Composer 2.5Jun 17, 2026 → Jun 17, 2026 · resolved
- Investigating service degradation — Composer 2.5Jun 17, 2026 → Jun 17, 2026 · resolved
- Elevated errors across many models on AnthropicJun 16, 2026 → Jun 16, 2026 · resolved
- Investigating service degradation of the Auto modelJun 16, 2026 → Jun 16, 2026 · resolved
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.