Voice Call One-Way Audio from Brazil to a Subset of Twilio Numbers
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.
The latest update from Twilio.
State
Resolved
Started
2 h ago
2026-11-02 20:55 UTC
Lasted
1 min
until 2026-11-02 20:55 UTC
Worst impact
Notice
Timeline
1 updateResolved
1 min 100%
Updates
Times in UTCAs posted by Twilio
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.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
59
Days with an incident
38
Median duration
6 h 53 min
This incident
100% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Puerto Rico
SMS delivery receipts are delayed from some Twilio Short Codes to Liberty network subscribers in Puerto Rico. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio identified the cause and is working to resolve the issue.
Twilio·Some Customers May Have Incorrect Balances Reflected on Their Account
Twilio reports that some customer accounts show incorrect balances. The Billing component and the Twilio Platform Billing component are affected. Twilio is investigating the issue and states that work to deploy a fix is in progress.
Twilio·SMS Delivery Delays and Failures from Twilio Alphanumeric Sender Type to T-Mobile Austria
Twilio SMS delivery delays and failures affected Alphanumeric Sender Type messages to T-Mobile subscribers in Austria. The SMS and Carrier Network SMS components in Europe were degraded. Twilio reports that the incident is resolved. The outage lasted about 5 hours and 13 minutes.
Twilio·SMS Delivery Delays from a Subset of Twilio Long Codes to T-Mobile and O2 Czech Republic
Twilio SMS delivery delays affected a subset of Twilio Long Codes to T-Mobile and O2 network subscribers in the Czech Republic. Twilio reports the incident resolved. It lasted about 2 hours and 54 minutes.
Twilio·Silent Network Authentication (SNA) Missing Redirects on XL Axiata in Indonesia
Twilio reported device verification timeouts on Silent Network Authentication (SNA) for the XL Axiata network in Indonesia. The incident affected the Verify Silent Network Auth component. Twilio resolved the incident after 13 hours and 27 minutes.
Follow Twilio
Your coding agent knows when Twilio is down, and tells you when a failure is theirs, not yours. You can also get Twilio incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "twilio" and tell me if Twilio has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=twilio/feed subscribe https://outages.live/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane