Outage recap · Anysphere

Cursor outage — September 17, 2026

On September 17, 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

major
Started
Sep 17, 8:30 AM EDT
Resolved
Sep 17, 10:34 AM EDT
Duration
2h 4m

Anysphere's updates (2)

  1. investigating · Sep 17, 8:30 AM EDT

    We are investigating a service degradation affecting Grok Bot. Users may experience degraded performance or bots that don't respond.

  2. resolved · Sep 17, 10:34 AM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 24 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 257 ms, against 224 ms over the 24 hours before. Anysphere posted the incident at Sep 17, 8:30 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 — Cloud Agents and Automations

minor
Started
Sep 17, 11:20 AM EDT
Resolved
Sep 17, 4:04 PM EDT
Duration
4h 43m

Anysphere's updates (7)

  1. investigating · Sep 17, 11:20 AM EDT

    We are investigating a service degradation affecting Cloud Agents and Automations

  2. investigating · Sep 17, 11:50 AM EDT

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

  3. investigating · Sep 17, 11:58 AM EDT

    We are continuing to investigate this issue.

  4. investigating · Sep 17, 1:31 PM EDT

    We are continuing to investigate this issue. Cloud Agents, Automations, and Review Agents (resulting from Cloud Agents) are affected. Bugbot is not affected.

  5. investigating · Sep 17, 2:02 PM EDT

    Affected services are back to normal operation. Our team continues to monitor everything closely.

  6. investigating · Sep 17, 2:12 PM EDT

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

  7. resolved · Sep 17, 4:04 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 56 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 233 ms, against 229 ms over the 24 hours before. Anysphere posted the incident at Sep 17, 11:20 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 ↗

AIDownCheck is not affiliated with Anysphere. This recap summarizes incidents published on Anysphere's official status page.