Cursor outage, 21 October 2026

Investigating service degradation

Started
Resolved
21 Oct 2026, 17:40 UTC (after 1 h 54 min)
Impact
Minor
Affected
cursor.com, Grok Bot

Is this still happening?

No. Cursor marked this incident resolved on 21 Oct 2026, 17:40 UTC, 1 h 54 min after it began.

Right now: Cursor reports all systems operational. (as of 26 Oct, 03:47 UTC) Live Cursor status

Last update from Cursor

This incident has been resolved.

21 Oct 2026, 17:40 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 41 min

    Investigating service outage - Grok models unavailable

  2. , resolved after 2 h 45 min

    Degraded performance and errors across Cursor services

  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 27 min

    Investigating service degradation

Other recent Cursor incidents

  1. Elevated errors for Bitbucket Cloud integrations

  2. Investigating service degradation

  3. Elevated errors affecting Grok models

  4. Investigating service degradation - Grok Bot

  5. Grok Bot routines not triggering

  6. Investigating service degradation - Cloud Agents and Grok Bot

  7. Investigating service degradation - Cloud Agents

  8. Elevated errors affecting Opus 5.5

All recorded Cursor incidents