Cursor incident: Investigating Grok service degradation

Affected components

• Automations
• CLI
• Cloud Agents
• IDE

1. resolvedSep 14, 2026, 09:07 UTC

   This incident has been resolved.

2. monitoringSep 14, 2026, 08:15 UTC

   We are monitoring Grok 4.6 for service restoration.

3. investigatingSep 14, 2026, 08:14 UTC

   We are investigating a service degradation affecting Grok 4.6.

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.

• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• Elasticsearch: Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch outputMajor · Sep 9, 2026, 20:44 UTC
• Anthropic: Degraded functionality for Claude Cowork on WindowsMajor · Sep 10, 2026, 15:54 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Twilio: SMS Delivery Failures from a Subset of Twilio Long Codes to Bouygues Telecom FranceMinor · Sep 12, 2026, 22:08 UTC
• Twilio: SMS Delivery Delays from a Subset of Twilio Short Codes to Vivo BrazilMinor · Sep 14, 2026, 08:34 UTC

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