Investigating service degradation — Automations and Cloud Agents
major- Started
- Sep 2, 10:50 AM EDT
- Resolved
- —
- Duration
- end time not published
What our checks recorded
We checked Cursor 24 times in the two hours after Anysphere's start time (it published no end time), once every five minutes. Every one of them reached Cursor's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 213 ms, against 226 ms over the 24 hours before. Anysphere's feed showed the incident by Sep 2, 11:03 AM EDT (we read it every five minutes).
Updates are Anysphere's own words from its status page (status: resolved); we never add an inferred cause.