Is Cursor down? October 26 codebase indexing and saved rules issue resolved after 3 hours 17 minutes
The incident report on status.x.ai showed degraded codebase indexing and saved rules and memories in Cursor from 22:02 UTC on October 26, 2026, until it was resolved at 01:19 UTC on October 27, about 3 hours 17 minutes. The first update said chat, agents and Tab were otherwise available.
SessionWatcher editorial · Published · Updated · Source announcement: 2026-10-26
What was degraded in Cursor
On October 26, 2026, the incident report on status.x.ai described an issue affecting codebase indexing and saved rules and memories in Cursor. During the incident, codebase indexes might not update, and agents might respond without a user's saved rules or memories. The first update said chat, agents and Tab were otherwise available.
The affected components listed are Automations, Cloud Agents, the CLI and the Cursor IDE (Desktop). The report rates the impact as minor.
Sources: Degraded codebase indexing and agent personalization
Timeline: about 3 hours 17 minutes
The first update, posted at 22:02 UTC on October 26, said the issue was under investigation and that the team was working with its infrastructure provider. At 23:24 UTC the report said the cause had been identified and a fix was rolling out. The incident was marked resolved at 01:19 UTC on October 27, about 3 hours 17 minutes after the first update. The status page does not say what the cause was.
Sources: Degraded codebase indexing and agent personalization
Usage and billing
The status page does not mention any effect on usage limits, credits or billing from this incident.
Sources: Degraded codebase indexing and agent personalization
AI assisted reporting, checked against the linked official sources. Source pages checked 2026-10-28. Editorial process and corrections.