Minor impactResolvedAI/ML

Cursor incident: Investigating service degradation

Cursor reported this minor-impact incident on its official status page on Sep 22, 2026, 01:07 UTC. It was resolved after 36 min.

Right now Cursor is operational. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Sep 22, 2026, 01:07 UTC
started
Sep 22, 2026, 01:42 UTC
resolved
36 min
duration
Minor
impact

Affected components

  • Automations
  • CLI
  • Cloud Agents
  • IDE
  1. resolvedSep 22, 2026, 01:42 UTC

    This incident has been resolved.

  2. investigatingSep 22, 2026, 01:07 UTC

    We are investigating degraded performance for requests that use Grok models. Users may see failed or retried requests in Automations, Cloud Agents, the CLI, and the IDE when Grok models are used. Other models are unaffected.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Cursor's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Cursor have incidents?

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

Cursor incident on Sep 22, 2026: Investigating service degradation · APIStatus.watch