Minor impactResolvedAI/ML

Cursor incident: Investigating service degradation — Grok Bot

Cursor reported this minor-impact incident on its official status page on Oct 19, 2026, 16:15 UTC. It was resolved after 1h 7m.

Right now Cursor is operational. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Oct 19, 2026, 16:15 UTC
started
Oct 19, 2026, 17:21 UTC
resolved
1h 7m
duration
Minor
impact

Affected components

  • Grok Bot
  1. resolvedOct 19, 2026, 17:21 UTC

    This incident has been resolved.

  2. monitoringOct 19, 2026, 17:10 UTC

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

  3. investigatingOct 19, 2026, 16:52 UTC

    We are continuing to investigate this issue. We will provide updates as more information becomes available.

  4. investigatingOct 19, 2026, 16:15 UTC

    We are investigating a service degradation affecting Grok Bot where routines may be delayed.

What APIStatus.watch saw

  • Oct 19, 2026, 16:20 UTCoperational → degraded
  • Oct 19, 2026, 17:25 UTCdegraded → operational
  • Oct 19, 2026, 18:15 UTCoperational → degraded

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