Live  /  Cursor  /  Incident

Cursor: Degraded Performance - Grok Bot

Cursor · cursor.comMinor incidentResolved2026-11-05 01:49 UTC
Public — what happened

Summary

Cursor reported a minor incident called degraded performance involving its Grok Bot, saying it began investigating errors with the bot at 00:34 UTC on 2026-11-05. At 01:49 UTC the company said it had identified the issue and resolved it. Cursor did not say who was affected or describe what caused the errors.

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 46, 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.