Outage recap · Anysphere

Cursor outage — September 3, 2026

On September 3, 2026, Cursor had 5 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 — Automations, Cloud Agents, Grok Bot, Review Agents

minor
Started
Sep 3, 9:41 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Cursor 24 times in the two hours after Anysphere's start time (it published no end time), 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 245 ms, against 228 ms over the 24 hours before. Anysphere's feed showed the incident by Sep 3, 9:46 AM EDT (we read it every five minutes).

Updates are Anysphere's own words from its status page (status: resolved); we never add an inferred cause.

Elevated errors for Anthropic Models

major
Started
Sep 3, 10:17 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Cursor 24 times in the two hours after Anysphere's start time (it published no end time), 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 245 ms, against 224 ms over the 24 hours before. Anysphere's feed showed the incident by Sep 3, 10:20 AM EDT (we read it every five minutes).

Updates are Anysphere's own words from its status page (status: resolved); we never add an inferred cause.

Elevated errors for OpenAI Models

minor
Started
Sep 3, 11:17 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Cursor 24 times in the two hours after Anysphere's start time (it published no end time), 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 230 ms, against 227 ms over the 24 hours before. Anysphere's feed showed the incident by Sep 3, 11:20 AM EDT (we read it every five minutes).

Updates are Anysphere's own words from its status page (status: resolved); we never add an inferred cause.

Degraded performance of Grok 4.6

minor
Started
Sep 3, 1:42 PM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Cursor 24 times in the two hours after Anysphere's start time (it published no end time), 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 252 ms, against 231 ms over the 24 hours before. Anysphere's feed showed the incident by Sep 3, 1:45 PM EDT (we read it every five minutes).

Updates are Anysphere's own words from its status page (status: resolved); we never add an inferred cause.

Degraded performance for Grok Bot routine triggers

major
Started
Sep 3, 7:42 PM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Cursor 24 times in the two hours after Anysphere's start time (it published no end time), 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 245 ms over the 24 hours before. Anysphere's feed showed the incident by Sep 3, 7:50 PM EDT (we read it every five minutes).

Updates are Anysphere's own words from its status page (status: resolved); we never add an inferred cause.

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