Cursor outage: Investigating service degradation — Grok Bot

Affected components

• Grok Bot

1. resolvedSep 16, 2026, 20:57 UTC

   This incident has been resolved.

2. identifiedSep 16, 2026, 19:51 UTC

   The root cause has been identified and a fix is being implemented.

3. investigatingSep 16, 2026, 14:27 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
• 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
• GitHub: Degradation with Gemini 3.8 FlashMajor · Sep 16, 2026, 07:20 UTC
• MongoDB Atlas: Support Portal OutageMajor · Sep 16, 2026, 09:06 UTC
• Smartsheet: Salesforce connector is experiencing intermittent issuesMajor · Sep 16, 2026, 10:36 UTC
• Elasticsearch: Elastic Support Portal unavailableMajor · Sep 16, 2026, 13:17 UTC
• Discord: Google Pay OutageMajor · Sep 16, 2026, 16:15 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• ClickHouse Cloud: ClickPipes failing on Kinesis in AWS us-east-1Minor · Sep 15, 2026, 18:57 UTC
• Telnyx: SMS Delivery — Encoding Issues on Outbound Messages to T-MobileMinor · Sep 15, 2026, 21:57 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