Resolved · lasted 8 h

Cursor outage on October 26

Reports for Cursor jumped to 633 an hour and stayed high for 8 h.

Started
5:00 PM
October 26, 2026 · UTC
Back to normal
1:00 AM
8 h later
Peak
633/hr
127× normal
Cursor’s incident
3 h 17 min
Degraded agent personalization and codebase sync

Reports during the outage

3:00 PM2:50 AM UTC

What Cursor said

status.cursor.com
Resolved10/26/2026, 10:02 PM – 10/27/2026, 1:19 AM · 3 h 17 min

Degraded agent personalization and codebase sync

  1. Resolved · 1:19 AM

    This has been resolved.

  2. Investigating · 11:24 PM

    We've identified the cause and are rolling out a fix.

  3. Investigating · 10:02 PM

    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.

Cursor posted its first update 5 h 03 min after reports started rising.

Is Cursor down right now?

Live status, today’s reports and other past outages.

Cursor status now →