- Level
- confirmed
- Worst impact
- Degraded
- Components
- Voice, Latin America
- Regions
- latam
- Down Index
- 12of 100
What to do
Check whether you use Twilio Voice, Latin America in latam. 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 0m it lasted.
Anything that failed between 2026-11-02 20:55 UTC and 2026-11-02 20:55 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 1
- resolved
On October 31, 2026, from 5AM to 8AM PT, customers may have experienced an issue with some inbound calls to Twilio Brazil numbers having no audio, and some calls also dropping. The impact was linked to a carrier fiber cut and a fallback route that could not handle the traffic load. The issue has been resolved and Voice is operating normally.
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-fda53e7938
Is Twilio still down?
No, this incident was resolved 2026-11-02 20:55 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
0m, from 2026-11-02 20:55 UTC to 2026-11-02 20:55 UTC, by the times Twilio posted.
What was affected?
Twilio named Voice, Latin America in latam.
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.