Outage recap · Anysphere

Cursor outage — September 25, 2026

On September 25, 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 — Grok Bot

minor
Started
Sep 25, 1:17 AM EDT
Resolved
Sep 25, 2:51 AM EDT
Duration
1h 34m

Anysphere's updates (3)

  1. investigating · Sep 25, 1:17 AM EDT

    We are investigating a service degradation affecting Grok Bot. Grok Bot computers may temporarily not be able to be created, reached, or reset.

  2. investigating · Sep 25, 1:52 AM EDT

    We have identified the cause and are deploying a fix. We are monitoring recovery as the fix rolls out. Some Grok Bot computers may remain temporarily unavailable or unable to be created or reset during this time.

  3. resolved · Sep 25, 2:51 AM EDT

    The service degradation affecting Grok Bot has been resolved.

What our checks recorded

We checked Cursor 19 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 206 ms, against 213 ms over the 24 hours before. Anysphere posted the incident at Sep 25, 1:17 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 — Grok Bot

minor
Started
Sep 25, 7:47 PM EDT
Resolved
Sep 25, 8:32 PM EDT
Duration
45 min

Anysphere's updates (3)

  1. investigating · Sep 25, 7:47 PM EDT

    We are investigating a service degradation affecting Grok Bot.

  2. investigating · Sep 25, 8:22 PM EDT

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

  3. resolved · Sep 25, 8:32 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 9 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 206 ms, against 225 ms over the 24 hours before. Anysphere posted the incident at Sep 25, 7:47 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.