Cursor outage: Investigating service degradation — Grok Bot

Affected components

• Grok Bot

1. resolvedSep 18, 2026, 23:02 UTC

   This incident has been resolved.

2. monitoringSep 18, 2026, 19:53 UTC

   A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.

3. identifiedSep 18, 2026, 19:01 UTC

   The root cause has been identified and a fix is being rolled out. Some users may see Grok Bot respond slowly or not respond at all. We will provide another update shortly.

4. investigatingSep 18, 2026, 17:19 UTC

   We are investigating a service degradation affecting Grok Bot.

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.

• Inngest: Degraded Function ExecutionMajor · Sep 18, 2026, 16:31 UTC
• Vercel: Elevated Errors Triggering DeploymentsMajor · Sep 18, 2026, 20:32 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Notion: Some connected content results unavailable in Notion AIMinor · Sep 17, 2026, 14:07 UTC
• Snyk: Snyk Daily Recurring Tests DelayedMinor · Sep 18, 2026, 06:40 UTC
• Resend: Degraded performanceMinor · Sep 18, 2026, 18:26 UTC
• Vercel: Deployment stuck in initializing stateMinor · Sep 18, 2026, 21:36 UTC

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