Outage recap · Anysphere

Cursor outage — September 23, 2026

On September 23, 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 — Cloud Agent Dockerfile Builds

minor
Started
Sep 23, 1:14 PM EDT
Resolved
Sep 23, 2:43 PM EDT
Duration
1h 29m

Anysphere's updates (4)

  1. investigating · Sep 23, 1:14 PM EDT

    Customers using Cloud Agents with Dockerfile-based builds may be unable to create new builds. Existing Cloud Agents continue to run on their current image; only new Dockerfile builds are affected.

  2. investigating · Sep 23, 1:15 PM EDT

    The root cause has been identified and a fix is being implemented.

  3. investigating · Sep 23, 2:39 PM EDT

    A fix has been implemented and we are monitoring for service restoration.

  4. resolved · Sep 23, 2:43 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 18 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 224 ms, against 211 ms over the 24 hours before. Anysphere posted the incident at Sep 23, 1:14 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 - Grok 4.7

minor
Started
Sep 23, 4:28 PM EDT
Resolved
Sep 23, 4:36 PM EDT
Duration
9 min

Anysphere's updates (3)

  1. investigating · Sep 23, 4:28 PM EDT

    We are investigating degraded performance for requests that use Grok 4.7.

  2. investigating · Sep 23, 4:31 PM EDT

    A fix has been implemented and we are monitoring for service restoration.

  3. resolved · Sep 23, 4:36 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 2 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 215 ms, against 210 ms over the 24 hours before. Anysphere posted the incident at Sep 23, 4:28 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.