Chargebee: Increased error rates
AWS outage, Jun 13, 2023 · 56 vendors, 56 incidents
Chargebee’s incident blames AWS as the cause. (hop 1, posted +1 h 37 min vs the first vendor naming AWS)
“…7 PM PDT, Our cloud provider experienced increased error rates and latencies for multiple AWS Services in the US-EAST-1 Region. The issue has been resolved and all AWS Services are operating normally.…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>13 vendors, 13 blamed AWS<br/>Pipedream, Wiz, Temporal Cloud +10"]:::blames
root --> h1
h4["1 to 4 hours later<br/>7 vendors, 6 blamed AWS<br/>CockroachDB, Vanta, Asana +4"]:::blames
root --> h4
me["Chargebee (this incident)<br/>posted +1 h 37 min"]:::me
h4 --- 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.
Timeline of updates
- resolved
Between 11:49 AM PDT and 3:37 PM PDT, Our cloud provider experienced increased error rates and latencies for multiple AWS Services in the US-EAST-1 Region. The issue has been resolved and all AWS Services are operating normally.
From Chargebee’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.chargebee.com (opens in new tab).