Cursor incident: Service degradation for Opus 4.6 and Opus 4.7

1. resolvedMay 15, 2026, 01:43 UTC

   This incident has been resolved.

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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• New Relic: UI and Data Irregularities - US RegionMajor · May 15, 2026, 00:06 UTC
• Anthropic: Elevated error rates on requests to some modelsMajor · May 15, 2026, 00:18 UTC
• DigitalOcean: Anthropic reported outage that's impacting access to their Serverless Inference modelsMajor · May 15, 2026, 01:21 UTC
• Twilio: SMS Delivery Failures from a Subset of Twilio Short Codes to Google Voice United StatesMinor · May 4, 2026, 20:40 UTC
• Shippo: Royal Mail InterSoft Tracking Degradation (Third-Party Issue)Minor · May 4, 2026, 20:48 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Twilio: SMS Delivery Delays from Twilio to Multiple Networks in Brunei DarussalamMinor · May 14, 2026, 15:10 UTC
• Twilio: SMS Delivery Failures between Twilio Phone Numbers and AT&T in MexicoMinor · May 14, 2026, 20:50 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