Outage recap · Anysphere

Cursor outage — September 18, 2026

On September 18, 2026, Cursor had 3 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 18, 7:37 AM EDT
Resolved
Sep 18, 10:33 AM EDT
Duration
2h 56m

Anysphere's updates (2)

  1. investigating · Sep 18, 7:37 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 18, 10:33 AM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 35 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 251 ms, against 231 ms over the 24 hours before. Anysphere posted the incident at Sep 18, 7:37 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 18, 1:19 PM EDT
Resolved
Sep 18, 7:02 PM EDT
Duration
5h 43m

Anysphere's updates (4)

  1. investigating · Sep 18, 1:19 PM EDT

    We are investigating a service degradation affecting Grok Bot.

  2. investigating · Sep 18, 3:01 PM EDT

    The root cause has been identified and a fix is being rolled out. Some users may see Grok Bot respond slowly or not respond at all. We will provide another update shortly.

  3. investigating · Sep 18, 3:53 PM EDT

    A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.

  4. resolved · Sep 18, 7:02 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Cursor 69 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 236 ms, against 232 ms over the 24 hours before. Anysphere posted the incident at Sep 18, 1:19 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 ↗

Sign-in and dashboard errors for some users

minor
Started
Sep 18, 7:02 PM EDT
Resolved
Sep 18, 7:13 PM EDT
Duration
11 min

Anysphere's updates (3)

  1. investigating · Sep 18, 7:02 PM EDT

    We are investigating an issue affecting sign-in. Signing in, signing out, and loading the dashboard may hang or fail. If you are already signed in, your session should continue to work normally. We will provide another update shortly.

  2. investigating · Sep 18, 7:07 PM EDT

    Sign-in is recovering. The issue came from our authentication provider, who has identified the cause and is seeing recovery on their side. We are monitoring to confirm everything is back to normal.

  3. resolved · Sep 18, 7:13 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 206 ms, against 231 ms over the 24 hours before. Anysphere posted the incident at Sep 18, 7:02 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.