# Twilio: Function invocations failing in US East Coast region due to an AWS DNS outage
- Impact (vendor’s label): none
- Status: resolved
- Started: 2020-07-28 08:30 UTC · Resolved: 2020-07-28 08:30 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.twilio.com/incidents/nbv007w548wy](https://status.twilio.com/incidents/nbv007w548wy)
- [Company: Twilio](https://rewindex.com/company/twilio.md)
## Part of an outage event
- [AWS outage, Jul 28, 2020: 18 vendors, 18 incidents](https://rewindex.com/events/2020-07-28-aws)
- This incident blames AWS as the cause. (hop 1, posted +0 min vs the first vendor naming AWS)
- Evidence: “…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…”
```mermaid
flowchart LR
root["AWS
own incident not archived"]:::inferred
h1["Within an hour
3 vendors, 3 blamed AWS
Honeycomb, Twilio, Chargebee"]:::blames
root --> h1
h4["1 to 4 hours later
2 vendors, 1 blamed AWS
Stream (GetStream), Elastic Cloud"]:::blames
root --> h4
me["Twilio (this incident)
posted +0 min"]:::me
h1 --- me
```
_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._
## Timeline of updates
- **resolved** 2020-07-28 08:30 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._
---
Canonical: https://rewindex.com/company/twilio/incidents/nbv007w548wy · Markdown: https://rewindex.com/company/twilio/incidents/nbv007w548wy.md · JSON: https://rewindex.com/api/v1/companies/twilio/incidents/nbv007w548wy · Generated 2026-10-20T00:09:57.908Z