Live  /  Cursor  /  Incident

Cursor: Investigating service degradation — Cloud Agents and Grok Bot

Cursor · cursor.comMajor incidentResolved2026-10-06 22:06 UTC
Public — what happened

Summary

Cursor reported a major service degradation beginning at 19:27 UTC on October 6, 2026, which it said impacted some Cloud Agents and Grok Bot features. The company said Grok Bot was working again by 21:25 UTC, while it kept looking into the remaining problems with some Cloud Agents. Cursor marked the incident resolved at 22:06 UTC and did not state a cause in its updates.

Affected

Cloud Agents, Grok Bot

As listed on Cursor’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Cursor against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Cursor: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Cursor report →

More from Cursor

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Cursor status & history page.

Related: Cursor status & history. SquidGrid is not affiliated with Cursor.