Cursor incident: Grok 4.6 availability issues

Affected components

• IDE

1. resolvedAug 17, 2026, 22:57 UTC

   This incident has been resolved. Grok 4.6 requests, including API traffic, have returned to normal.

2. monitoringAug 17, 2026, 22:18 UTC

   Grok 4.6 is operating normally again. We’re monitoring to ensure continued stability.

3. investigatingAug 17, 2026, 21:50 UTC

   Customers may encounter errors when using Grok 4.6. We’re investigating and will share updates as we learn more.

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: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Akamai: Connection drops and increased latency in MiamiMinor · Aug 13, 2026, 19:31 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• HashiCorp Vault: Delayed HCP Terraform RunsMinor · Aug 15, 2026, 17:08 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Tailscale: Coordination service performance issuesMinor · Aug 17, 2026, 20:27 UTC
• Expo: iOS Submissions hanging on App Store Connect build uploadsMinor · Aug 17, 2026, 21:12 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