Cursor outage, 27 October 2026

Delayed responses in Grok Bot

Started
Resolved
27 Oct 2026, 20:43 UTC (after 10 min)
Impact
Major
Affected
Grok Bot

Is this still happening?

No. Cursor marked this incident resolved on 27 Oct 2026, 20:43 UTC, 10 min after it began.

Right now: Cursor reports all systems operational. (as of 27 Oct, 21:45 UTC) Live Cursor status

Last update from Cursor

This issue has been resolved. For a short period, some Grok Bot responses were delayed. Responses are back to normal and we're sorry for the disruption.

27 Oct 2026, 20:43 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 1 h 6 min

    Investigating service degradation - Grok Bot

  3. , resolved after 5 h 18 min

    Investigating service degradation - Grok Bot

  4. , resolved after 31 min

    Investigating service degradation - Cloud Agents and Grok Bot

  5. , resolved after 1 h 25 min

    Investigating service degradation - Grok Bot

Other recent Cursor incidents

  1. Elevated errors affecting repository integrations

  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. Investigating service outage - Grok models unavailable

  7. Elevated errors for Bitbucket Cloud integrations

  8. Investigating service degradation

All recorded Cursor incidents