Cursor outage, 6 November 2026

Computer use in Grok Bot fails for users in a few regions.

Started
Resolved
6 Nov 2026, 12:03 UTC (after 14 min)
Impact
Minor
Affected
Grok Bot

Is this still happening?

No. Cursor marked this incident resolved on 6 Nov 2026, 12:03 UTC, 14 min after it began.

Right now: Cursor reports all systems operational. (as of 13 Nov, 20:59 UTC) Live Cursor status

At a glance

Our summary from the Cursor incidents we have recorded since 18 Sept 2026 - how we count.

Last update from Cursor

The issue is resolved and computer use in Grok Bot is working normally again for all users.

6 Nov 2026, 12:03 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 1 h 17 min

    Grok Bot is currently degraded

  2. , resolved after 1 h 14 min

    Degraded Performance - Grok Bot

  3. , resolved after 10 min

    Delayed responses in Grok Bot

  4. , resolved after 19 min

    Investigating service degradation - Grok Bot

  5. , resolved after 1 h 6 min

    Investigating service degradation - Grok Bot

Other recent Cursor incidents

  1. Elevated errors for some requests

  2. Elevated errors for OpenAI model requests

  3. composer-2.5 degraded

  4. 3 "Slow clones from GH due to Github degradation"

  5. Issues with source control integrations

  6. Service Degradation - Billing and Usage Dashboard

  7. Multiple services degraded

  8. Auto Review Degradation

All recorded Cursor incidents

Something wrong on this page?

A person reads every report. We fix our own mistakes - wording, mapping, a moved status page; the status itself always comes from Cursor's official page. How we handle corrections.

Thanks - your report is on its way to us. We read every one.