Voice Call Silent and One-Way Audio between a Subset of Twilio Phone Numbers and Multiple Networks in Colombia
Twilio reports silent and one-way audio on voice calls between a subset of Twilio phone numbers and subscribers on multiple networks in Colombia. The issue affects Voice in Latin America and the carrier network for Voice in Latin America. Twilio has identified the cause and is working to resolve the issue.
State
Identified
Started
Ongoing for
38 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
30 min 80%
Resolved
6 min 16%
Identified
2 min 4%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing silent and one-way audio between a subset of Twilio Phone Numbers and network subscribers on multiple networks in Colombia. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.
Twilio customers may be experiencing voice call silent and one-way audio between a subset of Twilio Phone Numbers and network subscribers on multiple networks in Colombia. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.
Twilio customers may be experiencing voice call silent and one-way audio between a subset of Twilio Phone Numbers and network subscribers on multiple networks in Colombia. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
80
Days with an incident
42
Median duration
7 h 17 min
This incident
91% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Puerto Rico
Twilio SMS delivery receipts are delayed from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. This affects SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio has identified the cause and is working to resolve the issue. Message delivery may succeed.
Twilio·SMS Delivery Failures from Twilio to Lycamobile France
SMS delivery failures occur from Twilio to Lycamobile network subscribers in France. This affects SMS in Europe and the CARRIER NETWORK for SMS in Europe. Twilio reports a recovery in SMS delivery and monitors service stability.
Twilio·Voice Call Failures from a Subset of Twilio Mobile Numbers to Argentina
Twilio reports voice call failures from a subset of Twilio Mobile Numbers to Telefonica network subscribers in Argentina. The affected components are Voice, Latin America and CARRIER NETWORK - Voice, Latin America. Twilio has identified the cause and is working to resolve the issue.
Twilio·Voice Call Post Dial Delay from a Subset of Twilio Canada Phone Numbers to Rogers Wireless and Fido Canada
Twilio voice calls from some Twilio Canada phone numbers to Rogers Wireless and Fido subscribers in Canada had post dial delay. The affected components were Voice, North America and CARRIER NETWORK - Voice, North America. Twilio reports that the incident is resolved. It lasted about 5 hours and 13 minutes.
Twilio·Search Delays on Enterprise Knowledge
Twilio reported slower search and content ingestion on Enterprise Knowledge, including its use with Conversation Intelligence. Twilio later stated that search latency is resolved and that Enterprise Knowledge operates normally. The incident lasted about 4 hours and 33 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