Live  /  Cursor  /  Incident

Cursor: Investigating service degradation — Grok Bot

Cursor · cursor.comMinor incidentResolved2026-10-07 17:25 UTC
Public — what happened

Summary

Cursor reported a minor service degradation involving Grok Bot's computers in some regions, beginning at 15:59 UTC on October 7, 2026. The company said it was looking into the problem but did not share a cause or say which users were affected. Cursor marked the incident as resolved at 17:25 UTC the same day.

Affected

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.