Outage recap · Anysphere

Cursor outage — October 6, 2026

On October 6, 2026, Cursor had 4 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 affecting Anthropic models

minor
Started
Oct 6, 8:40 AM EDT
Resolved
Oct 6, 12:00 PM EDT
Duration
3h 20m

Anysphere's updates (2)

  1. investigating · Oct 6, 8:40 AM EDT

    We are investigating a service degradation affecting Opus 5.5. More information: https://status.claude.com/incidents/ch27pb90bn85

  2. resolved · Oct 6, 12:00 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 40 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 167 ms, against 201 ms over the 24 hours before. Anysphere posted the incident at Oct 6, 8:40 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 ↗

Investigating service degradation — Security Reviewer Agents

major
Started
Oct 6, 1:49 PM EDT
Resolved
Oct 6, 2:56 PM EDT
Duration
1h 7m

Anysphere's updates (2)

  1. investigating · Oct 6, 1:49 PM EDT

    We are investigating a service degradation affecting Security Reviewer agents.

  2. resolved · Oct 6, 2:56 PM EDT

    This incident has been resolved.

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 266 ms, against 193 ms over the 24 hours before. Anysphere posted the incident at Oct 6, 1:49 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 ↗

Investigating service degradation — Cloud Agents and Grok Bot

major
Started
Oct 6, 3:27 PM EDT
Resolved
Oct 6, 6:06 PM EDT
Duration
2h 39m

Anysphere's updates (4)

  1. investigating · Oct 6, 3:27 PM EDT

    We are investigating a service degradation affecting some Cloud Agents and Grok Bot features.

  2. investigating · Oct 6, 5:23 PM EDT

    We are currently investigating this issue. We will provide updates as more information becomes available.

  3. investigating · Oct 6, 5:25 PM EDT

    Grok Bot has been restored. We are continuing to investigate a service degradation affecting some Cloud Agents.

  4. resolved · Oct 6, 6:06 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 32 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 192 ms, against 193 ms over the 24 hours before. Anysphere posted the incident at Oct 6, 3:27 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 ↗

Investigating service degradation — Cloud Agents

major
Started
Oct 6, 6:48 PM EDT
Resolved
Oct 6, 7:04 PM EDT
Duration
17 min

Anysphere's updates (5)

  1. investigating · Oct 6, 6:48 PM EDT

    We are investigating a service degradation affecting Cloud Agents.

  2. investigating · Oct 6, 6:52 PM EDT

    We are currently investigating this issue. We will provide updates as more information becomes available.

  3. investigating · Oct 6, 6:53 PM EDT

    We are currently investigating this issue. We will provide updates as more information becomes available.

  4. investigating · Oct 6, 6:53 PM EDT

    We are currently investigating this issue. We will provide updates as more information becomes available.

  5. resolved · Oct 6, 7:04 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 3 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 134 ms, against 193 ms over the 24 hours before. Anysphere posted the incident at Oct 6, 6:48 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.