Cursor: Investigating service degradation — Grok Bot

Impact: majorStatus: resolvedStarted 2026-09-18 17:19 UTCResolved 2026-09-18 23:02 UTC (5.7 h)4 updatesSource: stspg.io

Summary

Cursor reported a major Grok Bot degradation: some users received slow responses or no response. The incident ran from 2026-09-18 17:19 UTC to 2026-09-18 23:02 UTC, lasting 5 h 43 min. A fix was implemented by 19:53 UTC, when Cursor said Grok Bot should be responding normally again.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Grok Bot

Timeline of updates

investigating2026-09-18 17:19 UTC
We are investigating a service degradation affecting Grok Bot.
identified2026-09-18 19:01 UTC
The root cause has been identified and a fix is being rolled out. Some users may see Grok Bot respond slowly or not respond at all. We will provide another update shortly.
monitoring2026-09-18 19:53 UTC
A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.
resolved2026-09-18 23:02 UTC
This incident has been resolved.

Rewindex changes for this incident

Major incident: Investigating service degradation — Grok Bot 2026-09-18 17:19 UTC

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Cursor profile · Recent Cursor incidents · Markdown · JSON