Twilio: Function invocations failing in US East Coast region due to an AWS DNS outage
AWS outage, Jul 28, 2020 · 18 vendors, 18 incidents
Twilio’s incident blames AWS as the cause. (hop 1, posted +0 min vs the first vendor naming AWS)
“…Function invocations failing in US East Coast region due to an AWS DNS outage Twilio Functions was degraded for 131 minutes between [28 July 2020 1:25 AM PDT and 3:36 AM PDT]. During this period of ti…”
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["Twilio (this incident)<br/>posted +0 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
Twilio Functions was degraded for 131 minutes between [28 July 2020 1:25 AM PDT and 3:36 AM PDT]. During this period of time customers may have experienced issues with Function invocation. The issue has now been resolved.
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).