Cursor incident: Investigating service degradation — Automations and Cloud Agents w/ Grok 4.7

Affected components

• Automations
• Cloud Agents

1. resolvedSep 22, 2026, 13:45 UTC

   This incident has been resolved.

2. identifiedSep 22, 2026, 13:08 UTC

   The root cause has been identified and a fix is being implemented.

3. investigatingSep 22, 2026, 13:02 UTC

   We are aware of an issue where Grok 4.7 fails to be selected as a model for Cloud Agents. We are investigating the issue.

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 Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Twilio: SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Mobile Puerto RicoMinor · Sep 20, 2026, 17:47 UTC
• Twilio: Voice Call Post Dial Delay from Twilio Phone Numbers to Jazz PakistanMinor · Sep 21, 2026, 06:10 UTC
• Linode: Emerging Service Issue - Cloud Manager and APIMinor · Sep 21, 2026, 17:13 UTC
• Zoom: Service Degradation Affecting Apple Login for Zoom Sign-in.Minor · Sep 21, 2026, 18:17 UTC
• Akamai: Increased latency during upstream provider maintenance in Singapore, Hong Kong, and JapanMinor · Sep 22, 2026, 00:30 UTC
• ClickHouse Cloud: We are investigating an issue with CH servers in Azure germanywestcentral regionMinor · Sep 22, 2026, 13:19 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