Skip to content
Back to CursorIncident Postmortem
Cursor logo

Cursor

Tracked by PulseWatch

Auto-drafted postmortem

Cursor outage on September 17 — 2h 22m disruption

Sep 17, 01:25 PM → Sep 17, 03:48 PM · 2h 22m · high

On September 17, 2026, the Cursor service experienced a high-severity disruption. The incident began at 13:25 UTC and was resolved at 15:48 UTC on the same day.

Duration
2h 22m
tracked by PulseWatch

Impact

The Cursor service experienced a high-severity disruption lasting 2 hours and 22 minutes. During this period, users may have encountered issues with the service's functionality. This incident was detected through automated monitoring signals, including the vendor's status page. No user-reported data was collected for this incident.

Incident timeline

  1. Sep 17, 01:25 PM

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

  2. Sep 17, 01:25 PM

    Status updated: possible issue

  3. Sep 17, 03:48 PM

    Signals cleared — incident resolved

Official updates

  1. Sep 17, 01:25 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