Outage recap · Anysphere

Cursor outage — October 27, 2026

On October 27, 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.

Elevated errors affecting repository integrations

none
Started
Oct 27, 3:33 AM EDT
Resolved
Oct 27, 4:18 AM EDT
Duration
46 min

Anysphere's updates (2)

  1. investigating · Oct 27, 3:33 AM EDT

    We are investigating elevated errors affecting some repository integrations. Features that rely on repository access, including review agents and cloud agents, may fail or be delayed. We are working to restore normal service.

  2. resolved · Oct 27, 4:18 AM EDT

    This incident has been resolved. Affected services returned to normal operation at approximately 08:02 UTC.

What our checks recorded

We checked Cursor 9 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 203 ms, against 197 ms over the 24 hours before. Anysphere posted the incident at Oct 27, 3:33 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 ↗

Delayed responses in Grok Bot

major
Started
Oct 27, 4:33 PM EDT
Resolved
Oct 27, 4:43 PM EDT
Duration
10 min

Anysphere's updates (2)

  1. investigating · Oct 27, 4:33 PM EDT

    We're investigating an issue causing delayed responses in Grok Bot. We'll share an update as soon as we have more information.

  2. resolved · Oct 27, 4:43 PM EDT

    This issue has been resolved. For a short period, some Grok Bot responses were delayed. Responses are back to normal and we're sorry for the disruption.

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 321 ms, against 190 ms over the 24 hours before. Anysphere posted the incident at Oct 27, 4:33 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.