‹ Back to incident history

Degraded performance and errors across Cursor services

ResolvedMinor incidentCursor
Tuesday, October 13, 2026 08:22 – Tuesday, October 13, 2026 11:07 (2 hr 45 min)
Affected components
Grok Build and Cursor: Automations
Grok Build and Cursor: Cloud Agents
Grok Build and Cursor: CLI
Grok Build and Cursor: cursor.com
IDE
Grok Build and Cursor: iOS
Grok Bot
Origin
Grok Build and Cursor: Review Agents
Updates
ResolvedTuesday, October 13, 2026 11:07

This incident has been resolved.

InvestigatingTuesday, October 13, 2026 10:23

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.

InvestigatingTuesday, October 13, 2026 09:49

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.

InvestigatingTuesday, October 13, 2026 09:32

We are continuing to monitor recovery. Some users may still see intermittent errors.

InvestigatingTuesday, October 13, 2026 08:53

A fix has been implemented and services are recovering. Some users may still see intermittent errors while we monitor for full restoration.

InvestigatingTuesday, October 13, 2026 08:22

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.

Incident data from the Cursor official status page:Read the official incident

About this data

Where does the incident data for Cursor come from?

Data comes from the Cursor official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview