Cursor incident: Investigating service degradation — Grok Bot

Affected components

• Grok Bot

1. resolvedOct 14, 2026, 21:04 UTC

   This incident has been resolved.

2. identifiedOct 14, 2026, 20:08 UTC

   We've identified the issue impacting Grok Bot for some users and are working on a fix.

3. investigatingOct 14, 2026, 15:46 UTC

   We are investigating a service degradation affecting Grok Bot and preventing some users from reaching their computers

What APIStatus.watch saw

• Oct 14, 2026, 15:49 UTCoperational → degraded
• Oct 14, 2026, 21:09 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Render: Builds, deploys, and queued deploys are not starting in all regionsMajor · Oct 14, 2026, 19:32 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
• Grafana Cloud: Phone call notifications to numbers in Russia and Kazakhstan are blockedMinor · Oct 13, 2026, 09:23 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