Minor impactResolvedAI/ML

Cursor incident: Opus 5.5 is Experiencing 429s

Cursor reported this minor-impact incident on its official status page on Oct 8, 2026, 13:54 UTC. It was resolved after 1h 37m.

Right now Cursor is operational. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Oct 8, 2026, 13:54 UTC
started
Oct 8, 2026, 15:31 UTC
resolved
1h 37m
duration
Minor
impact

Affected components

  • Automations
  • CLI
  • Cloud Agents
  • Grok Bot
  • IDE
  • Review Agents
  1. resolvedOct 8, 2026, 15:31 UTC

    This incident has been resolved.

  2. monitoringOct 8, 2026, 14:08 UTC

    A fix has been implemented and we are monitoring for service restoration.

  3. investigatingOct 8, 2026, 13:54 UTC

    We are investigating a service degradation with Opus 5.5 being used across all product components.

What APIStatus.watch saw

  • Oct 8, 2026, 13:59 UTCoperational → degraded
  • Oct 8, 2026, 15:33 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Cursor have incidents?

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