Chargebee: API Service Degradation
AWS us-east-1 outage, Oct 9, 2026 · 17 vendors, 18 incidents
Chargebee’s incident blames AWS as the cause. (hop 1, posted +11 h 1 min vs the first vendor naming AWS)
“…ervice Degradation We experienced a brief service interruption in the US region due to an AWS platform issue, which resulted in intermittent API failures for some merchants. All services have complete…”
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["Chargebee (this incident)<br/>posted +11 h 1 min"]:::me
later --- 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: API Endpoints - API (US)API (US)
Timeline of updates
- resolved
We experienced a brief service interruption in the US region due to an AWS platform issue, which resulted in intermittent API failures for some merchants. All services have completely recovered. We apologize for any disruption this may have caused.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).