Cursor outage: Grok Bot routines not triggering

1. resolvedOct 13, 2026, 20:29 UTC

   Between 10:52 AM and 1:29 PM PT on October 13, many Grok Bot routines started by webhooks, Slack, git, email and Linear events didn't run. Webhook callers may have seen an HTTP 400 "Automation run rate limit exceeded" error, and other triggers failed without an error. Your own usage didn't cause this. Routines are running normally again. Events sent during this window weren't processed and won't be retried automatically, so please resend anything important.

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.

• Shippo: Elevated error rate on Canada post Shipment APIMajor · Oct 13, 2026, 08:58 UTC
• Grafana Cloud: IRM Unable to Send SMS to Thailand NumbersMinor · Oct 5, 2026, 16:17 UTC
• LiveKit: Investigating reports of elevated RoomService API errorsMinor · Oct 6, 2026, 00:10 UTC
• Shopify: Some merchants encountering error messages when trying to login to their adminsMinor · Oct 8, 2026, 14:49 UTC
• OVHcloud: [EU-WEST-PAR][Storage] - Object Storage S3 incident notificationMinor · Oct 8, 2026, 15:14 UTC
• Twilio: SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Mobile ChinaMinor · Oct 9, 2026, 06:42 UTC
• Cloudflare: Elevated Errors in China Network ColosMinor · Oct 10, 2026, 04:13 UTC
• Twilio: Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to ThailandMinor · Oct 12, 2026, 11:53 UTC
• Supabase: Realtime latencyMinor · Oct 12, 2026, 22:59 UTC
• Snyk: GitLab Cloud Integration DegradedMinor · Oct 13, 2026, 07:32 UTC

How often does Cursor have incidents?

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