Skip to content
Back to CursorIncident Postmortem
Cursor logo

Cursor

Tracked by PulseWatch

Auto-drafted postmortem

Cursor outage on September 18 — 6h 52m disruption

Sep 18, 05:56 PM → Sep 19, 12:48 AM · 6h 52m · high

A high-severity incident affecting the Cursor service was detected by automated monitoring systems, including the vendor's status page. The disruption began on September 18, 2026, at 17:56 UTC. The incident was resolved on September 19, 2026, at 00:48 UTC.

Duration
6h 52m
tracked by PulseWatch

Impact

The Cursor service experienced a high-severity disruption for approximately 6 hours and 52 minutes. This incident was detected through automated signals, including the vendor's own status page and synthetic probes. No user-reported data, including specific issue types or affected regions, was collected for this incident.

Incident timeline

  1. Sep 18, 05:56 PM

    PulseWatch detected the incident from automated vendor and probe signals (high severity)

  2. Sep 18, 05:56 PM

    Status updated: possible issue

  3. Sep 19, 12:48 AM

    Signals cleared — incident resolved

Official updates

  1. Sep 18, 05:56 PM

    Cursor status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash