Cursor outage: Delayed responses in Grok Bot

Affected components

• Grok Bot

1. resolvedOct 27, 2026, 20:43 UTC

   This issue has been resolved. For a short period, some Grok Bot responses were delayed. Responses are back to normal and we're sorry for the disruption.

2. investigatingOct 27, 2026, 20:33 UTC

   We're investigating an issue causing delayed responses in Grok Bot. We'll share an update as soon as we have more information.

What APIStatus.watch saw

• Oct 27, 2026, 20:34 UTCoperational → degraded
• Oct 27, 2026, 20:44 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Sanity: API & API CDN timeouts for small subset of customersMajor · Oct 27, 2026, 14:33 UTC
• Akamai: Edge Delivery issues between Indonesia and SingaporeMinor · Oct 25, 2026, 13:44 UTC
• Linode: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)Minor · Oct 25, 2026, 13:54 UTC
• Twilio: Voice Call Failures from Twilio Phone Numbers to Digi.Mobil RomaniaMinor · Oct 26, 2026, 13:09 UTC
• Twilio: MMS Delivery Delays and Failures from a Subset of Twilio Long Codes to Cellcom United StatesMinor · Oct 26, 2026, 20:29 UTC
• Twilio: SMS Delivery Delays from a Subset of Twilio Short Codes to Docomo Pacific United StatesMinor · Oct 26, 2026, 20:57 UTC
• Twilio: SMS Delivery Failures between a Subset of Twilio Phone Numbers and Multiple Networks in BrazilMinor · Oct 26, 2026, 23:55 UTC
• OVHcloud: [EU-WEST-PAR-A][Storage] - Volume Ceph incident notificationMinor · Oct 27, 2026, 07:30 UTC
• Twilio: Voice Call Failures From Twilio Phone Numbers to GermanyMinor · Oct 27, 2026, 09:00 UTC
• Tailscale: Funnel hostnames not resolving in public DNSMinor · Oct 27, 2026, 14:16 UTC

How often does Cursor have incidents?

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