Cursor incident: Investigating service degradation — Grok Bot

Affected components

• Grok Bot

1. resolvedAug 27, 2026, 15:05 UTC

   This incident has been resolved.

2. monitoringAug 27, 2026, 14:51 UTC

   A fix has been implemented and we are monitoring for service restoration.

3. investigatingAug 27, 2026, 14:23 UTC

   We are investigating a service degradation affecting Grok Bot.

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.

• Smartsheet: Unexpected HTTP response code affecting login, sheet access, Control Center, Dynamic View and other premium appsCritical · Aug 27, 2026, 13:33 UTC
• Sentry: sentry.io is not availableMajor · Aug 27, 2026, 09:24 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Supabase: pgBouncer issues on some older projectsMinor · Aug 26, 2026, 19:49 UTC
• GitHub: Disruption with GitHub BillingMinor · Aug 26, 2026, 23:37 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