Live / Cursor / Incident
Cursor: Issues with source control integrations
Cursor · cursor.comMinor incidentResolved2026-11-02 10:24 UTC
Public — what happened
Summary
Cursor said it began looking into reports of problems with its connections to source control providers, affecting both Cursor and Grok Bot, at 09:09 UTC on 2026-11-02. The company rated the incident as minor and did not say what caused it. At 10:24 UTC Cursor reported that the issue was resolved.
Affected
IDE, Grok Bot
Timeline
- Started — 2026-11-02 09:09 UTC
- Investigating — 2026-11-02 09:09 UTC
- Resolved — 2026-11-02 10:24 UTC · 1h 15m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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.