Outage recap · Anysphere

Cursor outage — September 21, 2026

On September 21, 2026, Cursor had 2 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.

Investigating service degradation

minor
Started
Sep 21, 2:39 AM EDT
Resolved
Sep 21, 3:00 AM EDT
Duration
22 min

Anysphere's updates (2)

  1. investigating · Sep 21, 2:39 AM EDT

    We are investigating degraded performance for requests that use Grok 4.6. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok 4.6 is used. Other models are unaffected.

  2. resolved · Sep 21, 3:00 AM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 5 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 242 ms, against 218 ms over the 24 hours before. Anysphere posted the incident at Sep 21, 2:39 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

minor
Started
Sep 21, 9:07 PM EDT
Resolved
Sep 21, 9:42 PM EDT
Duration
36 min

Anysphere's updates (2)

  1. investigating · Sep 21, 9:07 PM EDT

    We are investigating degraded performance for requests that use Grok models. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok models are used. Other models are unaffected.

  2. resolved · Sep 21, 9:42 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 7 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 283 ms, against 209 ms over the 24 hours before. Anysphere posted the incident at Sep 21, 9:07 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.