Cursor outage, 28 October 2026

Multiple services degraded

Started
Resolved
28 Oct 2026, 23:13 UTC (after 1 h 58 min)
Impact
Major
Affected
Automations, BugBot, Cloud Agents, Grok Bot, Origin

Is this still happening?

No. Cursor marked this incident resolved on 28 Oct 2026, 23:13 UTC, 1 h 58 min after it began.

Right now: Cursor reports all systems operational. (as of 28 Oct, 23:46 UTC) Live Cursor status

Last update from Cursor

This incident has been resolved. All services have returned to normal operation.

28 Oct 2026, 23:13 UTC

Read the full incident on the official Cursor status page

Similar Cursor incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 46 min

    Elevated errors affecting repository integrations

  2. , resolved after 2 h 45 min

    Degraded performance and errors across Cursor services

  3. , resolved after 41 min

    Investigating service outage - Grok models unavailable

  4. , resolved after 58 min

    Elevated errors affecting Opus 5.5

  5. , resolved after 1 h 36 min

    Opus 5.5 is Experiencing 429s

Other recent Cursor incidents

  1. Delayed responses in Grok Bot

  2. Payment System Sync Issues

  3. Degraded agent personalization and codebase sync

  4. Elevated errors for Claude Sonnet 5.5

  5. Degraded Model Performance

  6. Elevated errors for Bitbucket Cloud integrations

  7. Investigating service degradation

  8. Investigating service degradation

All recorded Cursor incidents