- Level
- confirmed
- Worst impact
- Degraded
- Components
- Voice REST API US1
- Down Index
- 17of 100
What to do
Check whether you use Twilio Voice REST API US1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 55m it lasted.
Anything that failed between 2026-09-01 16:48 UTC and 2026-09-01 17:42 UTC may need a replay.Subscribe to Twilio's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Twilio 4
- investigating
Our monitoring systems have detected a potential issue with Voice E2E Test failures. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
Our engineers have identified the issue Voice E2E Test failures and are working to deploy a fix. We expect to provide another update in1 hour or as soon as more information becomes available.
provider
- resolved
Voice E2E Test failures has been resolved and is operating normally at this time.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-7c82338ff5
Is Twilio still down?
No, this incident was resolved 2026-09-01 17:42 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
55m, from 2026-09-01 16:48 UTC to 2026-09-01 17:42 UTC, by the times Twilio posted.
What was affected?
Twilio named Voice REST API US1.
What caused it?
Twilio hasn't published a root cause. If it does, it shows here.
Where does this come from?
Twilio's official status page, https://status.twilio.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.