Twilio: Network Latencies Causing Multiple Service Disruptions
AWS outage, Nov 25, 2020 · 28 vendors, 29 incidents
Twilio’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted −1 h 34 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>1 vendor, 1 blamed AWS<br/>Pipedream"]:::blames
root --> h1
h4["1 to 4 hours later<br/>4 vendors, 4 blamed AWS<br/>HubSpot, Xero, Lattice, Heap"]:::blames
root --> h4
later["Later<br/>2 vendors, 2 blamed AWS<br/>Confluent, Pipedream"]:::blames
root --> later
me["Twilio (this incident)<br/>posted −1 h 34 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.
Timeline of updates
- resolved
The issue has been resolved. We have mitigated the impact from the service disruption with the exception of Flex Insights. Customers may notice missing Flex Insights events for the next 12 hours from Wednesday Nov 25 11:00 UTC 2020 - Thursday Nov 26 15:00 UTC 2020. These events will be repopulated over the next 12 hours with no missing data.
From Twilio’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.twilio.com (opens in new tab).