Minor impactResolvedAI/ML

Cursor incident: Investigating — Cloud Agent Dockerfile Builds

Cursor reported this minor-impact incident on its official status page on Sep 23, 2026, 17:14 UTC. It was resolved after 1h 29m.

Right now Cursor is operational. Live Cursor status →

🔔 Get alerted when Cursor has issuesFree · email alerts · no credit card
Sep 23, 2026, 17:14 UTC
started
Sep 23, 2026, 18:43 UTC
resolved
1h 29m
duration
Minor
impact

Affected components

  • Cloud Agents

Timeline

updates from Cursor's status page ↗
  1. resolvedSep 23, 2026, 18:43 UTC

    This incident has been resolved.

  2. monitoringSep 23, 2026, 18:39 UTC

    A fix has been implemented and we are monitoring for service restoration.

  3. identifiedSep 23, 2026, 17:15 UTC

    The root cause has been identified and a fix is being implemented.

  4. investigatingSep 23, 2026, 17:14 UTC

    Customers using Cloud Agents with Dockerfile-based builds may be unable to create new builds. Existing Cloud Agents continue to run on their current image; only new Dockerfile builds are affected.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Cursor's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Cursor have incidents?

Cursor reported 50 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 8m. See Cursor's uptime and incident history

← Previous: Investigating service degradation — Automations and Cloud Agents w/ Grok 4.7 (Sep 22, 2026)Next: Investigating service degradation - Grok 4.7 (Sep 23, 2026) →
Cursor incident on Sep 23, 2026: Investigating — Cloud Agent Dockerfile Builds · APIStatus.watch