Minor impactResolvedAI/ML

Cursor incident: Investigating service degradation

Cursor reported this minor-impact incident on its official status page on Sep 15, 2026, 21:26 UTC. It was resolved after 33 min.

Right now Cursor is operational. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Sep 15, 2026, 21:26 UTC
started
Sep 15, 2026, 22:00 UTC
resolved
33 min
duration
Minor
impact

Affected components

  • Automations
  • CLI
  • Cloud Agents
  • Grok Bot
  • IDE
  • Origin
  • Review Agents
  1. resolvedSep 15, 2026, 22:00 UTC

    This incident has been resolved at 6pm Eastern.

  2. monitoringSep 15, 2026, 21:41 UTC

    A fix has been implemented and we are monitoring for service restoration. Only Grok 4.6 (non-fast) is affected in Cursor.

  3. monitoringSep 15, 2026, 21:38 UTC

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

  4. investigatingSep 15, 2026, 21:26 UTC

    We are investigating a service degradation. Affected agent surfaces: Composer and xAI.

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 88 incidents in the last 90 days, 23 of them major or critical. A typical incident lasted 1h 12m. See Cursor's uptime and incident history

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