Live / Cursor / Incident
Cursor: Degraded agent personalization and codebase sync
Cursor · cursor.comMinor incidentResolved2026-10-27 01:19 UTC
Public — what happened
Summary
Cursor said it began investigating a problem at 22:02 UTC on 2026-10-26 that affected codebase indexing and saved rules and memories. During this time, code indexes might not refresh and agents could answer without a user's saved rules or memories, while chat, agents and Tab otherwise kept working. Cursor said it was working with its infrastructure provider, and at 23:24 UTC it said it had identified the cause and was rolling out a fix. It reported the issue resolved at 01:19 UTC on 2026-10-27.
Affected
Automations, Cloud Agents, CLI, IDE
Timeline
- Started — 2026-10-26 22:02 UTC
- Investigating — 2026-10-26 22:02 UTC (2 updates)
- Resolved — 2026-10-27 01:19 UTC · 3h 17m 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 45, 2026, our weekly internet health report.