Cursor incident: Investigating service degradation

Affected components

• Automations
• CLI
• Cloud Agents
• IDE

1. resolvedAug 21, 2026, 10:07 UTC

   This incident has been resolved.

2. monitoringAug 21, 2026, 09:59 UTC

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

3. investigatingAug 21, 2026, 09:20 UTC

   We are investigating a service degradation affecting some non-fast Grok-4.6 sessions. Users may experience failures in sessions with attached images.

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.

• 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
• Confluence: Marketplace App Macros Not Rendering in ConfluenceMinor · Aug 21, 2026, 07:16 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