Major impactOngoingAI/ML

Cursor outage: Multiple services degraded

Cursor reported this major-impact incident on its official status page on Oct 28, 2026, 21:15 UTC. It has not been marked resolved yet.

Right now Cursor is degraded. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Oct 28, 2026, 21:15 UTC
started
—
resolved
ongoing
duration
Major
impact

Affected components

  • Automations
  • BugBot
  • Cloud Agents
  • Grok Bot
  • Origin

Timeline

updates from Cursor's status page ↗
  1. investigatingOct 28, 2026, 22:06 UTC

    A fix has been implemented and services are starting to recover. We will share another update shortly.

  2. investigatingOct 28, 2026, 21:39 UTC

    We are investigating service degradation for multiple services. Users may see failures across Automations, Bugbot, Cloud Agents, Grok Bot, and Origin. We are working on a fix and will update shortly.

  3. investigatingOct 28, 2026, 21:15 UTC

    We are investigating service degradation for multiple services. Users may see failures across Cloud Agents, Grok Bot, and Origin. Apologies for the trouble.

What APIStatus.watch saw

  • Oct 28, 2026, 21:19 UTCoperational → degraded

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Cursor have incidents?

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

← Previous: Delayed responses in Grok Bot (Oct 27, 2026)