Cursor incident: Investigating service degradation

Affected components

• Automations
• CLI
• Cloud Agents
• IDE

1. resolvedAug 18, 2026, 08:50 UTC

   This incident has been resolved.

2. monitoringAug 18, 2026, 08:08 UTC

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

3. investigatingAug 18, 2026, 07: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: 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
• GitHub: Intermittent failures in runner group and runner-related permissions pagesMinor · Aug 18, 2026, 07:40 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