Cursor outage, 19 October 2026

Investigating service degradation - Grok Bot

Started
Resolved
19 Oct 2026, 17:21 UTC (after 1 h 6 min)
Impact
Minor
Affected
Grok Bot

Is this still happening?

No. Cursor marked this incident resolved on 19 Oct 2026, 17:21 UTC, 1 h 6 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.

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

    Investigating service degradation - Grok Bot

  2. , resolved after 5 h 18 min

    Investigating service degradation - Grok Bot

  3. , resolved after 31 min

    Investigating service degradation - Cloud Agents and Grok Bot

  4. , resolved after 1 h 25 min

    Investigating service degradation - Grok Bot

  5. , resolved after 2 h 39 min

    Investigating service degradation - Cloud Agents and Grok Bot

Other recent Cursor incidents

  1. Investigating service outage - Grok models unavailable

  2. Elevated errors for Bitbucket Cloud integrations

  3. Investigating service degradation

  4. Investigating service degradation

  5. Investigating service degradation

  6. Elevated errors affecting Grok models

  7. Grok Bot routines not triggering

  8. Degraded performance and errors across Cursor services

All recorded Cursor incidents