Outage recap · Anysphere

Cursor outage — September 29, 2026

On September 29, 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 — Cloud Agents and Grok Bot

minor
Started
Sep 29, 10:25 AM EDT
Resolved
Sep 29, 2:05 PM EDT
Duration
3h 40m

Anysphere's updates (4)

  1. investigating · Sep 29, 10:25 AM EDT

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

  2. investigating · Sep 29, 11:26 AM EDT

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

  3. investigating · Sep 29, 1:54 PM EDT

    Fixes are being implemented and we are monitoring for service restoration.

  4. resolved · Sep 29, 2:05 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 45 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 196 ms, against 196 ms over the 24 hours before. Anysphere posted the incident at Sep 29, 10:25 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 - xAI models

major
Started
Sep 29, 3:43 PM EDT
Resolved
Sep 29, 4:18 PM EDT
Duration
35 min

Anysphere's updates (3)

  1. investigating · Sep 29, 3:43 PM EDT

    We are investigating a service degradation affecting xAI models. Some Agent requests may fail.

  2. investigating · Sep 29, 4:01 PM EDT

    We have identified the cause of degraded performance affecting xAI models and are working to restore full capacity. Users may see errors, slow responses, or rate limiting on these models, and some Cloud Agent tasks may fail. We will post another update shortly.

  3. resolved · Sep 29, 4:18 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 189 ms, against 196 ms over the 24 hours before. Anysphere posted the incident at Sep 29, 3:43 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.