AI Incidents
Back to incident register
Source reviewedOperational incidentMedium

Cursor reported a critical degradation across Grok models and agent services

Cursor documented a critical service degradation affecting all Grok models, Automations, Cloud Agents, Grok Bot and Review Agents on September 3. The provider identified a cause, applied mitigation work and resolved the incident after about three and a half hours.

First observed
Sep 3, 2026, 3:41:00 PM
Disclosed
Sep 3, 2026, 3:41:00 PM
Status
Resolved
Confidence
99%
Organization
Cursor
Last reviewed
Sep 4, 2026

Observed

Facts supported by sources

  • Cursor classified a service degradation as critical and listed all Grok models, Automations, Cloud Agents, Grok Bot and Review Agents as affected.
  • Cursor opened the incident at 13:41 UTC, said it had identified the cause at 15:33 UTC and marked the incident resolved at 17:07 UTC on September 3.

Assessment

Interpretation, not observation

  • Cursor did not disclose the root cause or quantify the number of affected users in the public status record.
  • Concurrent upstream provider outages may be related, but the source does not establish a common cause.

Impact

Impact

Failed or unavailable model and agent workflows across multiple Cursor automation and review surfaces.

Response

Response

Cursor identified the cause, worked on a mitigation and then reported service restored.

Methodology: Facts, interpretations, and uncertainty are kept separate. Confidence describes the strength of the evidence, not a probability estimate.