Minor impactResolvedAI/ML

Cursor incident: Elevated errors affecting Grok models

Cursor reported this minor-impact incident on its official status page on Oct 15, 2026, 22:25 UTC. It was resolved after 6h 56m.

Right now Cursor is operational. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Oct 15, 2026, 22:25 UTC
started
Oct 16, 2026, 05:20 UTC
resolved
6h 56m
duration
Minor
impact

Affected components

  • CLI
  • Cloud Agents
  • IDE
  1. resolvedOct 16, 2026, 05:20 UTC

    This incident has been resolved. Grok models in Cursor are working normally again.

  2. monitoringOct 15, 2026, 22:58 UTC

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

  3. investigatingOct 15, 2026, 22:25 UTC

    We are investigating elevated errors affecting Grok models in Cursor. Some requests may fail with a capacity error. Retrying the request or switching to another model may help.

What APIStatus.watch saw

  • Oct 15, 2026, 22:30 UTCoperational → degraded
  • Oct 16, 2026, 05: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 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