Cursor outage, 21 October 2026

Elevated errors for Bitbucket Cloud integrations

Started
Resolved
21 Oct 2026, 17:53 UTC (after 13 min)
Impact
Minor
Affected
Review Agents, Cloud Agents

Is this still happening?

No. Cursor marked this incident resolved on 21 Oct 2026, 17:53 UTC, 13 min after it began.

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

Last update from Cursor

Atlassian has reported the issue as resolved and they are continuing to monitor for service restoration.

21 Oct 2026, 17:53 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 1 h 36 min

    Opus 5.5 is Experiencing 429s

  3. , resolved after 6 h 55 min

    Elevated errors affecting Grok models

  4. , resolved after 31 min

    Investigating service degradation - Cloud Agents and Grok Bot

  5. , resolved after 12 min

    Investigating service degradation - Cloud Agents

Other recent Cursor incidents

  1. Investigating service outage - Grok models unavailable

  2. Investigating service degradation

  3. Investigating service degradation

  4. Investigating service degradation - Grok Bot

  5. Investigating service degradation - Grok Bot

  6. Investigating service degradation

  7. Investigating service degradation - Grok Bot

  8. Grok Bot routines not triggering

All recorded Cursor incidents