Cursor incident: Degraded performance of Grok models

Affected components

• Automations
• CLI
• Cloud Agents
• IDE

1. resolvedAug 25, 2026, 21:28 UTC

   This incident has been resolved.

2. monitoringAug 25, 2026, 20:50 UTC

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

3. investigatingAug 25, 2026, 20:34 UTC

   We are investigating a service degradation affecting Grok models.

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.

• OVHcloud: [GLOBAL][Identity, Security & Operations] - User Management Incident NotificationMajor · Aug 25, 2026, 18:21 UTC
• OVHcloud: [GLOBAL][Data & Analytics] - Cloud Database Incident NotificationMajor · Aug 25, 2026, 21:25 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
• Smartsheet: Intermittent Cell Link and Cross Sheet Reference delays/failuresMinor · Aug 25, 2026, 20:45 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