Outage recap · Anysphere

Cursor outage — October 26, 2026

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

Elevated errors for Claude Sonnet 5.5

minor
Started
Oct 26, 10:02 AM EDT
Resolved
Oct 26, 11:25 AM EDT
Duration
1h 24m

Anysphere's updates (3)

  1. investigating · Oct 26, 10:02 AM EDT

    We are investigating elevated errors affecting requests to Sonnet 5.5. Some users may see failed or rate-limited responses when using this model.

  2. investigating · Oct 26, 10:36 AM EDT

    We are seeing improvement for Claude Sonnet 5.5 requests. We are continuing to monitor the situation. Some users may still see occasional errors when using this model.

  3. resolved · Oct 26, 11:25 AM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 17 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 241 ms, against 210 ms over the 24 hours before. Anysphere posted the incident at Oct 26, 10:02 AM EDT.

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

Degraded agent personalization and codebase sync

minor
Started
Oct 26, 6:02 PM EDT
Resolved
Oct 26, 9:19 PM EDT
Duration
3h 17m

Anysphere's updates (3)

  1. investigating · Oct 26, 6:02 PM EDT

    We're investigating an issue affecting codebase indexing and saved rules and memories. Codebase indexes may not update, and agents may respond without your saved rules or memories. Chat, agents, and Tab are otherwise available. We're working with our infrastructure provider and will share updates as we learn more.

  2. investigating · Oct 26, 7:24 PM EDT

    We've identified the cause and are rolling out a fix.

  3. resolved · Oct 26, 9:19 PM EDT

    This has been resolved.

What our checks recorded

We checked Cursor 39 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 181 ms, against 211 ms over the 24 hours before. Anysphere posted the incident at Oct 26, 6:02 PM EDT.

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

Payment System Sync Issues

minor
Started
Oct 26, 8:19 PM EDT
Resolved
Oct 26, 8:24 PM EDT
Duration
5 min

Anysphere's updates (2)

  1. investigating · Oct 26, 8:19 PM EDT

    Users may encounter unexpected blocks with payments. Our team are actively investigating this.

  2. resolved · Oct 26, 8:24 PM EDT

    This has been resolved.

What our checks recorded

We checked Cursor 1 time 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 244 ms, against 208 ms over the 24 hours before. Anysphere posted the incident at Oct 26, 8:19 PM EDT.

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.