Cursor incident: Grok Bot connector delays

Affected components

• Grok Bot

1. resolvedAug 18, 2026, 20:15 UTC

   This incident has been resolved. Affected Grok Bot sessions have been restored, and connectors are operating normally.

2. monitoringAug 18, 2026, 20:03 UTC

   A fix has been implemented and affected Grok Bot sessions have been restored. We are monitoring for full recovery.

3. investigatingAug 18, 2026, 19:29 UTC

   We are continuing to investigate an issue causing some Grok Bot connectors to hang. We are working to restore normal operation.

4. investigatingAug 18, 2026, 18:46 UTC

   We’re investigating an issue causing Grok Bot connectors to hang. We’ll share updates as we learn more.

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.

• Netlify: Elevated HTTP 500 errors serving sites and the Netlify UICritical · Aug 18, 2026, 20:00 UTC
• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Akamai: Connection drops and increased latency in MiamiMinor · Aug 13, 2026, 19:31 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Anthropic: Degraded performance for multiple modelsMinor · Aug 18, 2026, 16:20 UTC
• Expo: iOS Submissions hanging on App Store Connect build uploadsMinor · Aug 18, 2026, 16:25 UTC
• Resend: Contact webhook events are delayed in deliveryMinor · Aug 18, 2026, 19:53 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