Minor impactResolvedAI/ML

Cursor incident: Investigating service degradation — Grok Bot

Cursor reported this minor-impact incident on its official status page on Sep 25, 2026, 05:17 UTC. It was resolved after 1h 34m.

Right now Cursor is operational. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Sep 25, 2026, 05:17 UTC
started
Sep 25, 2026, 06:51 UTC
resolved
1h 34m
duration
Minor
impact

Affected components

  • Grok Bot
  1. resolvedSep 25, 2026, 06:51 UTC

    The service degradation affecting Grok Bot has been resolved.

  2. monitoringSep 25, 2026, 05:52 UTC

    We have identified the cause and are deploying a fix. We are monitoring recovery as the fix rolls out. Some Grok Bot computers may remain temporarily unavailable or unable to be created or reset during this time.

  3. investigatingSep 25, 2026, 05:17 UTC

    We are investigating a service degradation affecting Grok Bot. Grok Bot computers may temporarily not be able to be created, reached, or reset.

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 25, 2026: Investigating service degradation — Grok Bot · APIStatus.watch