Cursor outage, 3 November 2026

3 "Slow clones from GH due to Github degradation"

Started
Resolved
3 Nov 2026, 22:53 UTC (after 1 h 12 min)
Impact
Not stated
Affected
Bugbot, Cloud Agents

Is this still happening?

No. Cursor marked this incident resolved on 3 Nov 2026, 22:53 UTC, 1 h 12 min after it began.

Right now: Cursor reports all systems operational. (as of 3 Nov, 23:12 UTC) Live Cursor status

Last update from Cursor

GitHub has mitigated the Git operations incident, and Cloud Agent startup and Bugbot run times have returned to normal.

3 Nov 2026, 22: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 17 min

    Degraded performance - Origin and Cloud Agents

  2. , resolved after 1 h 58 min

    Multiple services degraded

  3. , resolved after 46 min

    Elevated errors affecting repository integrations

  4. , resolved after 7 h 41 min

    Cloud Agent Degradation

  5. , resolved

    Investigating service degradation

Other recent Cursor incidents

  1. Issues with source control integrations

  2. Service Degradation - Billing and Usage Dashboard

  3. Multiple services degraded

  4. Auto Review Degradation

  5. Investigating Service Degradation with VS Code Extensions

  6. Delayed responses in Grok Bot

  7. Payment System Sync Issues

  8. Degraded agent personalization and codebase sync

All recorded Cursor incidents