Cursor incident: Degraded performance of Grok 4.6

Affected components

• CLI
• Cloud Agents
• Grok Bot
• IDE

1. resolvedAug 25, 2026, 17:36 UTC

   This incident has been resolved.

2. monitoringAug 25, 2026, 16:20 UTC

   We are seeing signs of improvement and will continue to monitor for service restoration.

3. identifiedAug 25, 2026, 15:29 UTC

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

4. investigatingAug 25, 2026, 14:54 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.

• DigitalOcean: Cloud Control Panel and APICritical · Aug 24, 2026, 17:14 UTC
• Pinecone: [SERVERLESS][GCP][us-central1] 5xx errors on some read and write requestsMajor · Aug 25, 2026, 15:50 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 UTC
• Akamai: Media Services Live 4 (MSL4) IssuesMinor · Aug 25, 2026, 16:52 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