Outage recap · Anysphere

Cursor outage — November 3, 2026

On November 3, 2026, Cursor had a reported incident on Anysphere's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

3 "Slow clones from GH due to Github degradation"

none
Started
Nov 3, 4:40 PM EST
Resolved
Nov 3, 5:53 PM EST
Duration
1h 12m

Anysphere's updates (2)

  1. investigating · Nov 3, 4:40 PM EST

    We're seeing slower Cloud Agent startups and Bugbot runs caused by an ongoing GitHub incident affecting Git operations. GitHub has identified the issue and is rolling out a mitigation. We're monitoring and will update as their fix takes effect. You can track GitHub's status at githubstatus.com.

  2. resolved · Nov 3, 5:53 PM EST

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

What our checks recorded

We checked Cursor 14 times from Anysphere's start time to its resolution, once every five minutes. Every one of them reached Cursor's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 500 ms, against 478 ms over the 24 hours before. Anysphere posted the incident at Nov 3, 4:40 PM EST.

Updates are Anysphere's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with Anysphere. This recap summarizes incidents published on Anysphere's official status page.