Live / Cursor / Incident
Cursor: 3 "Slow clones from GH due to Github degradation"
Cursor · cursor.comResolved2026-11-03 22:53 UTC
Public — what happened
Summary
Cursor said that on 2026-11-03 starting at 21:40 UTC, Cloud Agent startups and Bugbot runs were slower than usual. The company attributed the slowdown to a GitHub incident affecting Git operations, and said GitHub had found the problem and was rolling out a mitigation. At 22:53 UTC Cursor reported that GitHub had mitigated the incident and that Cloud Agent startup and Bugbot run times were back to normal.
Affected
Review Agents, Cloud Agents
Timeline
- Started — 2026-11-03 21:40 UTC
- Investigating — 2026-11-03 21:40 UTC
- Resolved — 2026-11-03 22:53 UTC · 1h 12m 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.