Cursor outage on 6 October 2026
Major outageAn email when it goes down, and when it’s back.
“Investigating service degradation — Security Reviewer Agents”
On 6 October, Cursor had a major outage affecting its Security Reviewer agents from 17:49 to 18:59 UTC, lasting 1 hour 10 minutes. Cursor's status page described a service degradation affecting the Review Agents component and marked the incident resolved at 18:56 UTC, three minutes before the outage ended. Discord, Discogs, Greenhouse and Sentry also reported problems during the same period.
Cursor’s own incident page ↗- When
- 17:49–18:59 UTC
- How long
- 1 h 10 min
- Incident open on its page
- 17:49–18:56 UTC
- Components affected
- 1
- Cursor, 30 days before
- 1 other outage
What broke when
From Cursor’s own status page: when it moved each component into trouble, and back.
At the same time
Started in the hour before or during it
And 87 lesser-known services. Problems at the same time are a clue, never proof that one caused another.
Timeline
Times in UTC
- Investigating
- Review Agents: partial outage
- Resolved
- Review Agents: back to normal
Where this comes from
Stackpulse reads Cursor’s official status page at status.cursor.com every minute. The times above are when it reported the problem; the summary is written from its updates and checked against them.
Stackpulse isn’t affiliated with Cursor. Names and logos belong to their owners.