Cursor outage on May 4 — 1h 13m disruption
May 4, 11:49 PM → May 5, 01:03 AM · 1h 13m · high
On May 4, 2026, Cursor experienced a service disruption that was detected through user reports. The incident was classified as high severity. Service was fully restored on May 5, 2026, at 01:03 UTC.
Impact
During the incident, users reported issues primarily categorized as 'Slow / unresponsive' and 'Website down'. A total of 24 user reports were received, with a peak of 10 reports within a 15-minute period. While no specific top impacted regions were recorded, these reports indicated a widespread impact on service availability and performance for affected users.
Top reported issues
- Slow / unresponsive12
- Website down12
Incident timeline
- May 4, 11:49 PM
PulseWatch detected elevated report volume (high severity)
- May 4, 11:53 PM
Status updated: possible issue
- May 4, 11:58 PM
Status updated: possible issue
- May 5, 12:00 AM
Peak of 8 reports in 15 minutes (baseline 1.3)
- May 5, 12:03 AM
Status updated: possible issue
- May 5, 12:08 AM
Status updated: major issue
- May 5, 12:13 AM
Status updated: major issue
- May 5, 12:18 AM
Status updated: possible issue
- May 5, 12:23 AM
Status updated: major issue
- May 5, 12:28 AM
Status updated: major issue
- May 5, 12:33 AM
Status updated: possible issue
- May 5, 12:38 AM
Status updated: major issue
- May 5, 12:43 AM
Status updated: major issue
- May 5, 01:03 AM
Report volume returned to baseline — incident resolved
Official updates
- May 4, 11:49 PM
Cursor status page acknowledged the incident.
View official source