Cursor change history

A major outage prevented many Grok Bot routines triggered by webhooks, Slack, git, email and Linear events from running; missed events won't be retried automatically. Service recovered, but recorded timestamps conflict: started 2026-10-13 21:13 UTC, resolved 2026-10-13 20:29 UTC; duration unknown.

Cursor reported a major service degradation affecting Cloud Agents, with Grok Bot also listed as an affected component. It started at 2026-10-06 22:48 UTC and was resolved at 2026-10-06 23:04 UTC, lasting 16 min; no cause or fix was stated.

Cursor reported a major service degradation affecting some Cloud Agents and Grok Bot features, starting at 2026-10-06 19:27 UTC and resolved at 2026-10-06 22:06 UTC, lasting 2 h 39 min. Grok Bot was restored at 10-06 21:25 UTC while Cloud Agents degradation remained under investigation; no cause or fix was stated.

Cursor reported a major service degradation affecting Security Reviewer agents (Review Agents), starting 2026-10-06 17:49 UTC and resolved at 2026-10-06 18:56 UTC after 1 h 7 min. No cause or fix was stated.

Cursor reported a major xAI model degradation affecting CLI, Cloud Agents, Grok Bot, and IDE: users could see errors, slow responses, rate limiting, and failed Agent requests or Cloud Agent tasks. It started at 2026-09-29 19:43 UTC and was resolved at 2026-09-29 20:18 UTC; the reported duration was 34 min.

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.

Cursor reported a major Grok Bot service degradation starting 2026-09-18 11:37 UTC, with degraded performance or bots not responding. The incident lasted 2 h 56 min and was resolved at 2026-09-18 14:33 UTC; no cause or fix was stated.

Grok Bot experienced a major service degradation starting 2026-09-17 12:30 UTC, with degraded performance or bots not responding. The incident was resolved at 2026-09-17 14:34 UTC after 2 h 3 min; no cause or fix was stated.

Cursor reported a major Grok Bot degradation: users could experience degraded performance or bots that did not respond. It started at 2026-09-16 14:27 UTC and was resolved at 2026-09-16 20:57 UTC, lasting 6 h 29 min. Cursor said it identified the root cause and was implementing a fix, but provided no specifics.

Cursor reported a major Grok Bot outage from 2026-09-07 20:32 UTC to 2026-09-07 21:37 UTC, lasting 1 h 5 min. Some users could not reach their Grok Bot computers, and Recover or Reset could fail; data was not affected. A fix was implemented, and the incident was resolved.

Cursor reported major degradation affecting Grok Bot routine triggers: some trigger fires could be dropped. The incident started at 2026-09-03 23:42 UTC and was resolved at 2026-09-04 00:42 UTC, lasting 59 min. The vendor said it identified the root cause and was implementing a fix, but provided no specifics.

Cursor reported a major incident affecting Automations, CLI, Cloud Agents, and IDE from 2026-09-03 14:17 UTC to 2026-09-03 16:31 UTC (2 h 14 min). An upstream Anthropic issue caused elevated errors or failed Agent turns for Fable 5.1, Fable 5, Opus 5, Opus 4.8, and Opus 4.6 requests; service was restored.

Cursor reported a critical service degradation affecting All Grok Models, Automations, Cloud Agents, Grok Bot and Review Agents; IDE was also listed as an affected component. It lasted 3 h 26 min, from 2026-09-03 13:41 UTC to 2026-09-03 17:07 UTC. Cursor reported identifying the cause and working on mitigation, but disclosed no cause or fix details.

Cursor reported a major service degradation in which Automations, Cloud Agents, and Review Agents failed to start. The incident began at 2026-09-02 14:50 UTC and was resolved at 2026-09-02 16:10 UTC, lasting 1 h 20 min; no cause or fix was stated.

Cursor reported a critical sign-in service degradation affecting cursor.com and IDE from 2026-08-27 19:31 UTC to 2026-08-27 19:38 UTC, lasting 7 min. A fix was implemented at 19:35 UTC, and Cursor confirmed sign-in had returned to normal at resolution.