Cursor outage, 27 October 2026

Elevated errors affecting repository integrations

Started
Resolved
27 Oct 2026, 08:18 UTC (after 46 min)
Impact
Not stated
Affected
Automations, BugBot, Cloud Agents, Origin, Review Agents

Is this still happening?

No. Cursor marked this incident resolved on 27 Oct 2026, 08:18 UTC, 46 min after it began.

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

Last update from Cursor

This incident has been resolved. Affected services returned to normal operation at approximately 08:02 UTC.

27 Oct 2026, 08:18 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 2 h 45 min

    Degraded performance and errors across Cursor services

  2. , resolved after 13 min

    Elevated errors for Bitbucket Cloud integrations

  3. , resolved after 1 h 36 min

    Opus 5.5 is Experiencing 429s

  4. , resolved after 1 h 23 min

    Elevated errors for Claude Sonnet 5.5

  5. , resolved after 58 min

    Elevated errors affecting Opus 5.5

Other recent Cursor incidents

  1. Payment System Sync Issues

  2. Degraded agent personalization and codebase sync

  3. Degraded Model Performance

  4. Investigating service outage - Grok models unavailable

  5. Investigating service degradation

  6. Investigating service degradation

  7. Investigating service degradation - Grok Bot

  8. Investigating service degradation - Grok Bot

All recorded Cursor incidents