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
Operational · 24h
100%
287 checks
Operational · 7d
98.14%
1561 checks

% of our checks that found Cursorfully operational. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow
Past incidents
  • Elevated errors across Anthropic models
    Jun 23, 2026 · ongoing · monitoring
  • Investigating service degradation — Automations
    Jun 22, 2026 → Jun 22, 2026 · resolved
  • Degraded Performance for Composer 2.5
    Jun 17, 2026 → Jun 17, 2026 · resolved
  • Investigating service degradation — Composer 2.5
    Jun 17, 2026 → Jun 17, 2026 · resolved
  • Elevated errors across many models on Anthropic
    Jun 16, 2026 → Jun 16, 2026 · resolved
  • Investigating service degradation of the Auto model
    Jun 16, 2026 → Jun 16, 2026 · resolved
  • Investigating service outage
    Jun 10, 2026 → Jun 10, 2026 · resolved
  • Investigating service degradation — Cloud Agents
    Jun 10, 2026 → Jun 10, 2026 · resolved
  • Investigating service degradation — Cloud Agents
    Jun 8, 2026 → Jun 8, 2026 · resolved
  • Degraded Performance for Agent Sessions
    Jun 2, 2026 → Jun 2, 2026 · resolved
  • Cloud Agents degradation
    May 30, 2026 → May 30, 2026 · resolved
  • Composer 2.5 Fast degradation
    May 27, 2026 → May 27, 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.

Anthropic →OpenAI →Google →xAI →
← Cursor live status

History is recorded from Cursor's official status plus our own independent checks. AIDownCheck is independent and not affiliated with Anysphere.