Cursor outage, 26 October 2026

Degraded codebase indexing and agent personalization

Started
Status
Ongoing: Investigating
Impact
Minor
Affected
Automations, Cloud Agents, CLI, IDE

Is this still happening?

Yes. Cursor still lists it as investigating; last update 26 Oct 2026, 22:02 UTC.

Right now: Cursor reports degraded performance on some systems. (as of 26 Oct, 23:09 UTC) Live Cursor status

Last update from Cursor

We're investigating an issue affecting codebase indexing and saved rules and memories. Codebase indexes may not update, and agents may respond without your saved rules or memories. Chat, agents, and Tab are otherwise available. We're working with our infrastructure provider and will share updates as we learn more.

26 Oct 2026, 22:02 UTC

Read the full incident on the official Cursor status page

Similar Cursor incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 1 h 23 min

    Elevated errors for Claude Sonnet 5.5

  2. , resolved after 41 min

    Investigating service outage - Grok models unavailable

  3. , resolved after 2 h 45 min

    Degraded performance and errors across Cursor services

  4. , resolved after 58 min

    Elevated errors affecting Opus 5.5

  5. , resolved after 1 h 36 min

    Opus 5.5 is Experiencing 429s

Other recent Cursor incidents

  1. Degraded Model Performance

  2. Elevated errors for Bitbucket Cloud integrations

  3. Investigating service degradation

  4. Investigating service degradation

  5. Investigating service degradation - Grok Bot

  6. Investigating service degradation - Grok Bot

  7. Investigating service degradation

  8. Elevated errors affecting Grok models

All recorded Cursor incidents