Cursor incident: Investigating service degradation

Affected components

• Automations
• CLI
• Cloud Agents
• IDE
• cursor.com

1. resolvedAug 17, 2026, 13:40 UTC

   This incident has been resolved.

2. monitoringAug 17, 2026, 10:11 UTC

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

3. investigatingAug 17, 2026, 09:32 UTC

   We are investigating a service degradation for requests that use Grok 4.6 (non-fast). Users may experience slowness and high error rates. Other models are unaffected.

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.

• GitHub: Incident with GitHub.comCritical · Aug 17, 2026, 13:40 UTC
• Elasticsearch: Increased error rates for microsoft-multilingual-e5-largeMajor · Aug 13, 2026, 08:32 UTC
• 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
• Contentful: Experience API experiencing issues on upsert operationsMinor · Aug 17, 2026, 09:05 UTC
• LaunchDarkly: Flag Updates via Polling API delayedMinor · Aug 17, 2026, 10:36 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