Cursor outage: Investigating service degradation — Grok Bot

Affected components

• Grok Bot

1. resolvedSep 17, 2026, 14:34 UTC

   This incident has been resolved.

2. investigatingSep 17, 2026, 12:30 UTC

   We are investigating a service degradation affecting Grok Bot. Users may experience degraded performance or bots that don't respond.

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.

• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• Pinecone: [Serverless][AWS][us-west-2] 5xx errors on the readpathMajor · Sep 17, 2026, 05:37 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Telnyx: SMS Delivery — Encoding Issues on Outbound Messages to T-MobileMinor · Sep 15, 2026, 21:57 UTC
• Notion: Duplicate characters when editing with a Korean keyboard on iOSMinor · Sep 16, 2026, 23:58 UTC
• Replicate: Replicate Pruna issueMinor · Sep 17, 2026, 01:09 UTC
• Notion: Some connected content results unavailable in Notion AIMinor · Sep 17, 2026, 14:07 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