Cursor outage, 31 October 2026

Multiple services degraded

Started
Resolved
31 Oct 2026, 06:47 UTC (after 44 min)
Impact
Minor
Affected
Automations, Cloud Agents, cursor.com, Grok Bot

Is this still happening?

No. Cursor marked this incident resolved on 31 Oct 2026, 06:47 UTC, 44 min after it began.

Right now: Cursor reports all systems operational. (as of 31 Oct, 07:50 UTC) Live Cursor status

Last update from Cursor

This incident has been resolved.

31 Oct 2026, 06:47 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 17 min

    Degraded performance - Origin and Cloud Agents

  4. , resolved after 1 h 58 min

    Multiple services degraded

  5. , resolved after 58 min

    Elevated errors affecting Opus 5.5

Other recent Cursor incidents

  1. Auto Review Degradation

  2. Cloud Agent Degradation

  3. Investigating Service Degradation with VS Code Extensions

  4. Delayed responses in Grok Bot

  5. Elevated errors affecting repository integrations

  6. Payment System Sync Issues

  7. Degraded agent personalization and codebase sync

  8. Elevated errors for Claude Sonnet 5.5

All recorded Cursor incidents