Cursor: Investigating service degradation — Cloud Agents
Part of an outage event
AWS us-east-1 outage, Oct 9, 2026 · 17 vendors, 18 incidents
Cursor’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted −1 h 2 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS us-east-1<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Convex, Temporal Cloud, JFrog, PlanetScale +1"]:::blames
root --> h1
later["Later<br/>1 vendor, 1 blamed AWS<br/>Chargebee"]:::blames
root --> later
me["Cursor (this incident)<br/>posted −1 h 2 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: Cloud Agents
Timeline of updates
- investigating
We are investigating a service degradation affecting Cloud Agents.
- resolved
This incident has been resolved.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).