Changes / Cursor / Investigating service degradation — Grok Bot
Cursor: Major incident: Investigating service degradation — Grok Bot
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 diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: Investigating service degradation — Grok Bot
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-09-18 17:19 UTC
Before: not present
After: 2026-09-18 23:02 UTC
Before: not present
After: Grok Bot
Before: not present
After: We are investigating a service degradation affecting Grok Bot.
Before: not present
After: 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.
Before: not present
After: A fix has been implemented and we are monitoring for service restoration. Grok Bot should be responding normally again.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Investigating service degradation — Grok Bot (this change) 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. | Major incident |