Klaviyo: AWS incident affecting components of Klaviyo application
AWS us-east-1 outage, Dec 22, 2021 · 40 vendors, 40 incidents
Klaviyo’s incident blames AWS as the cause. (hop 1, posted +44 min vs the first vendor naming AWS)
“…AWS incident affecting components of Klaviyo application Open incidents for downstream providers are now resolved. Upon assessing impact, fewer than 1% of event-triggered marketing flow messages were…”
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/>8 vendors, 6 blamed AWS<br/>Firebolt, Bitbucket, HubSpot, CircleCI +4"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor<br/>Confluent"]:::names
root --> h4
me["Klaviyo (this incident)<br/>posted +44 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
Open incidents for downstream providers are now resolved. Upon assessing impact, fewer than 1% of event-triggered marketing flow messages were impacted during this window, and no transactional flow messages were lost. This incident is now resolved.
From Klaviyo’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.klaviyo.com (opens in new tab).