Cursor outage on May 5 — 1h 34m disruption
May 5, 04:29 PM → May 5, 06:03 PM · 1h 34m · high
On May 5, 2026, the Cursor service experienced an outage, which was detected via user reports. Users reported issues with slow or unresponsive service. The incident was resolved on May 5, 2026, at 18:03 UTC.
Impact
During the incident, users reported experiencing slow or unresponsive behavior with the Cursor service. A total of 20 user reports were received, with 15 reports occurring during the peak 15-minute period. All reported issues were categorized as slow or unresponsive service. No specific regional impact was recorded for this incident.
Top reported issues
- Slow / unresponsive20
Incident timeline
- May 5, 04:29 PM
PulseWatch detected elevated report volume (high severity)
- May 5, 04:30 PM
Peak of 4 reports in 15 minutes (baseline 1.3)
- May 5, 04:38 PM
Status updated: possible issue
- May 5, 04:43 PM
Status updated: possible issue
- May 5, 04:53 PM
Status updated: possible issue
- May 5, 05:08 PM
Status updated: possible issue
- May 5, 05:13 PM
Status updated: possible issue
- May 5, 05:23 PM
Status updated: possible issue
- May 5, 05:28 PM
Status updated: possible issue
- May 5, 05:38 PM
Status updated: possible issue
- May 5, 05:43 PM
Status updated: possible issue
- May 5, 06:03 PM
Report volume returned to baseline — incident resolved
Official updates
- May 5, 04:29 PM
Cursor status page acknowledged the incident.
View official source