AI STATUS BOARD

Cursor outage report · Tuesday 6 October 2026

Cursor went
down twice
in one day.

Anysphere reported “Investigating service degradation — Cloud Agents and Grok Bot” and “Investigating service degradation — Cloud Agents”. 2 h 56 min in total, all resolved.

Is Cursor down right now?

In numbers

RESOLVED 23:04 UTC
Down in total
2 h 56 min
Outages
2
Longest
2 h 39 min
Updates from Anysphere
9
Parts hit
  • Cloud Agents
  • Grok Bot

The day, hour by hour

UTC
00:0006:0012:0018:0024:00

What Anysphere said, as it happened

22:48 → 23:04 UTC · Investigating service degradation — Cloud Agents

17 min
  1. 23:04resolved

    This incident has been resolved.

  2. 22:53investigating

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

  3. 22:53investigating

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

  4. 22:52investigating

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

  5. 22:48investigating

    We are investigating a service degradation affecting Cloud Agents.

Anysphere's incident page

19:27 → 22:06 UTC · Investigating service degradation — Cloud Agents and Grok Bot

2 h 39 min
  1. 22:06resolved

    This incident has been resolved.

  2. 21:25investigating

    Grok Bot has been restored. We are continuing to investigate a service degradation affecting some Cloud Agents.

  3. 21:23investigating

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

  4. 19:27investigating

    We are investigating a service degradation affecting some Cloud Agents and Grok Bot features.

Anysphere's incident page

Quoted from Anysphere's status page. Times in UTC.

Was it just Cursor?

No. Replit also had problems at the same time.

  • Replit00:22 (18 Sep) → 14:52 (7 Oct)GitHub connector may not be working for users

Other problems that day:

  • GitHub Copilot23:47 (5 Oct) → 01:32Disruption with some GitHub services
  • Bolt08:37 → 09:56Supabase Managemenet API Errors
  • Claude, Claude API12:24 → 12:43Elevated errors for Claude Opus 5.5
  • Replit17:44 → 02:22 (8 Oct)Connectors platform latency
  • Replit21:26 → 22:30Connection errors affecting some customers

Cursor's record

Incidents, last 90 days
33
Typical length
58 min

This day's longest outage ran 2 times the typical length.

All Cursor outages

Hear first next time

A notification the moment Cursor breaks, and when it's back.

Questions about this outage

Why was Cursor down on 6 October 2026?

Anysphere described it as “Investigating service degradation — Cloud Agents and Grok Bot” and “Investigating service degradation — Cloud Agents”. Its updates are quoted on this page; if it posts a cause later, it shows up there.

Which parts of Cursor were affected?

Anysphere listed: Cloud Agents, Grok Bot.

How long was Cursor down?

2 h 56 min in total, across 2 outages: 2 h 39 min from 19:27 UTC, 17 min from 22:48 UTC.

Were other AI tools down at the same time?

Yes: Replit reported problems during it.

How do I know next time Cursor goes down?

Turn on alerts on AI Status Board. You get a notification the moment Cursor breaks and again when it is back.