Current answer
Cursor experienced a minor incident: Degraded performance and errors across Cursor services. ServiceAlert observed recovery on Oct 13, 2026.
Looking for an update now? Check the current status, or follow Cursor for future changes.
Incident Lifecycle
Affected Components
Automations
Review Agents
CLI
Cloud Agents
cursor.com
IDE
Origin
Grok Bot
Incident Timeline
Monitoring
All Cursor services have recovered and are operating normally, except Cloud Agents. Some Cloud Agents may still be slow to start or fail to run, and we're actively working to restore full service. We'll share another update as soon as we have more information.
Oct 13, 2026 at 2:23 AM UTC
Monitoring
Grok Bot has recovered and is operating normally. We are continuing to monitor recovery across the IDE, Cloud Agents, and other affected services, and some users may still see intermittent errors.
Oct 13, 2026 at 1:49 AM UTC
Monitoring
We are continuing to monitor recovery. Some users may still see intermittent errors.
Oct 13, 2026 at 1:32 AM UTC
Monitoring
A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.
Oct 13, 2026 at 12:53 AM UTC
Investigating
We are investigating a widespread issue affecting Cursor. Users may see errors or failed requests across the IDE, Cloud Agents, Automations, Grok Bot, and Origin. Our team is actively working to restore service.
Oct 13, 2026 at 12:22 AM UTC
Was your business affected by this Cursor outage?
Follow Cursor and route available status alerts to email or a team channel.