Cursor outage: Investigating service degradation

1. resolvedJul 31, 2026, 21:10 UTC

   This incident has been resolved. All services have returned to normal operation.

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.

• Twilio: Voice Call Post Dial Delay and Failures from Twilio Phone Numbers to Claro GuatemalaMinor · Jul 27, 2026, 01:15 UTC
• Twilio: Voice Call Failures from Twilio Phone Numbers to Core Communications United StatesMinor · Jul 28, 2026, 03:13 UTC
• Twilio: SMS Delivery Delays and Failures from Twilio to Metfone CambodiaMinor · Jul 29, 2026, 00:06 UTC
• Twilio: SMS Delivery Receipt Delays from Twilio to Liberty Mobile Puerto RicoMinor · Jul 29, 2026, 19:53 UTC
• Twilio: SMS Delivery Delays and Failures from Twilio to Unitel AngolaMinor · Jul 29, 2026, 22:49 UTC
• Twilio: SMS Delivery Delays from Twilio to Africell AngolaMinor · Jul 30, 2026, 22:31 UTC
• Twilio: Voice Call Failures and Post Dial Delay from Twilio Phone Numbers to BrazilMinor · Jul 30, 2026, 23:22 UTC
• LaunchDarkly: Investigating - Known ImpactMinor · Jul 31, 2026, 17:44 UTC
• Supabase: Management API Performance DegradationMinor · Jul 31, 2026, 18:36 UTC

How often does Cursor have incidents?

Cursor reported 88 incidents in the last 90 days, 23 of them major or critical. A typical incident lasted 1h 12m. See Cursor's uptime and incident history