Outage recap · Anysphere

Cursor outage — September 16, 2026

On September 16, 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 16, 4:03 AM EDT
Resolved
Sep 16, 4:42 AM EDT
Duration
40 min

Anysphere's updates (3)

  1. investigating · Sep 16, 4:03 AM EDT

    We are investigating elevated error rates affecting xAI models in the Cursor IDE and CLI. Some Agent requests may fail.

  2. investigating · Sep 16, 4:09 AM EDT

    A fix has been implemented. We are monitoring recovery and will provide another update once the incident is fully resolved.

  3. resolved · Sep 16, 4:42 AM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 8 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 207 ms, against 205 ms over the 24 hours before. Anysphere posted the incident at Sep 16, 4:03 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

major
Started
Sep 16, 10:27 AM EDT
Resolved
Sep 16, 4:57 PM EDT
Duration
6h 30m

Anysphere's updates (3)

  1. investigating · Sep 16, 10:27 AM EDT

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

  2. investigating · Sep 16, 3:51 PM EDT

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

  3. resolved · Sep 16, 4:57 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 78 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 209 ms, against 209 ms over the 24 hours before. Anysphere posted the incident at Sep 16, 10:27 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.