Major impactResolvedAI/ML

Cursor outage: Investigating service degradation — Cloud Agents and Grok Bot

Cursor reported this major-impact incident on its official status page on Oct 6, 2026, 19:27 UTC. It was resolved after 2h 39m.

Right now Cursor is operational. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Oct 6, 2026, 19:27 UTC
started
Oct 6, 2026, 22:06 UTC
resolved
2h 39m
duration
Major
impact

Affected components

  • Cloud Agents
  • Grok Bot
  1. resolvedOct 6, 2026, 22:06 UTC

    This incident has been resolved.

  2. investigatingOct 6, 2026, 21:25 UTC

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

  3. investigatingOct 6, 2026, 21:23 UTC

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

  4. investigatingOct 6, 2026, 19:27 UTC

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

What APIStatus.watch saw

  • Oct 6, 2026, 18:58 UTCdegraded → operational
  • Oct 6, 2026, 19:28 UTCoperational → degraded
  • Oct 6, 2026, 22:08 UTCdegraded → operational
  • Oct 6, 2026, 22:53 UTCoperational → degraded

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Cursor have incidents?

Cursor reported 90 incidents in the last 90 days, 22 of them major or critical. A typical incident lasted 1h 15m. See Cursor's uptime and incident history