Cursor incident: Degraded performance of Grok 4.6

Affected components

• CLI
• Cloud Agents
• Grok Bot
• IDE

1. resolvedSep 3, 2026, 19:21 UTC

   This incident has been resolved.

2. monitoringSep 3, 2026, 18:57 UTC

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

3. investigatingSep 3, 2026, 17:42 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
• OVHcloud: [GLOBAL][Databases] - MongoDB incident notificationMajor · Sep 3, 2026, 10:18 UTC
• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC
• Telnyx: Intermittent delays for some outbound messagesMinor · Sep 2, 2026, 21:33 UTC
• Notion: Promotional offers may not apply correctly to subscriptionsMinor · Sep 3, 2026, 11:32 UTC
• OVHcloud: [GRA1/GRA11][Storage] - Block storage incident notificationMinor · Sep 3, 2026, 15:39 UTC
• Datadog: Delayed CICD Optimization, Code Coverage, Code Security, and DORA dataMinor · Sep 3, 2026, 17:20 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