Cursor outage, 29 October 2026

Auto Review Degradation

Started
Resolved
30 Oct 2026, 01:20 UTC (after 1 h 35 min)
Impact
Minor
Affected
Grok Bot

Is this still happening?

No. Cursor marked this incident resolved on 30 Oct 2026, 01:20 UTC, 1 h 35 min after it began.

Right now: Cursor reports degraded performance on some systems. (as of 30 Oct, 01:41 UTC) Live Cursor status

Last update from Cursor

This has been resolved

30 Oct 2026, 01:20 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 36 min

    Investigating service degradation - Grok Bot and Review Agents

  2. , resolved after 1 h 54 min

    Investigating service degradation

  3. , resolved after 19 min

    Investigating service degradation - Grok Bot

  4. , resolved after 1 h 6 min

    Investigating service degradation - Grok Bot

  5. , resolved after 5 h 18 min

    Investigating service degradation - Grok Bot

Other recent Cursor incidents

  1. Cloud Agent Degradation

  2. Investigating Service Degradation with VS Code Extensions

  3. Degraded performance - Origin and Cloud Agents

  4. Multiple services degraded

  5. Delayed responses in Grok Bot

  6. Elevated errors affecting repository integrations

  7. Payment System Sync Issues

  8. Degraded agent personalization and codebase sync

All recorded Cursor incidents