Minor impactResolvedAI/ML

Cursor incident: Degraded agent personalization and codebase sync

Cursor reported this minor-impact incident on its official status page on Oct 26, 2026, 22:02 UTC. It was resolved after 3h 17m.

Right now Cursor is operational. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Oct 26, 2026, 22:02 UTC
started
Oct 27, 2026, 01:19 UTC
resolved
3h 17m
duration
Minor
impact

Affected components

  • Automations
  • CLI
  • Cloud Agents
  • IDE
  1. resolvedOct 27, 2026, 01:19 UTC

    This has been resolved.

  2. investigatingOct 26, 2026, 23:24 UTC

    We've identified the cause and are rolling out a fix.

  3. investigatingOct 26, 2026, 22:02 UTC

    We're investigating an issue affecting codebase indexing and saved rules and memories. Codebase indexes may not update, and agents may respond without your saved rules or memories. Chat, agents, and Tab are otherwise available. We're working with our infrastructure provider and will share updates as we learn more.

What APIStatus.watch saw

  • Oct 26, 2026, 21:34 UTCoperational → unknown
  • Oct 26, 2026, 21:59 UTCunknown → operational
  • Oct 26, 2026, 22:04 UTCoperational → degraded
  • Oct 27, 2026, 01:24 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Cursor have incidents?

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