Chargebee: AWS DNS Resolver Issue
AWS outage, Jul 28, 2020 · 18 vendors, 18 incidents
Chargebee’s incident blames AWS as the cause. (hop 1, posted +30 min vs the first vendor naming AWS)
“…AWS DNS Resolver Issue This incident has been resolved. Jobs that had failed due to this incident have been rescheduled. Based on our logs, very few api calls were affected during the incident.…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>3 vendors, 3 blamed AWS<br/>Honeycomb, Twilio, Chargebee"]:::blames
root --> h1
h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Stream (GetStream), Elastic Cloud"]:::blames
root --> h4
me["Chargebee (this incident)<br/>posted +30 min"]:::me
h1 --- 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
This incident has been resolved. Jobs that had failed due to this incident have been rescheduled. Based on our logs, very few api calls were affected during the incident.
From Chargebee’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.chargebee.com (opens in new tab).