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 some voice calls between a subset of Twilio phone numbers and multiple networks in Colombia. This affects the Voice, Latin America and CARRIER NETWORK - Voice, Latin America components. Twilio is investigating the issue.
State
Investigating
Started
Ongoing for
52 min
Worst impact
Degraded
Timeline
1 updateInvestigating
52 min 100%
Updates
Times in UTCAs posted by Twilio
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
121
Days with an incident
48
Median duration
7 h 14 min
This incident
88% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Networks in France
SMS delivery delays affect a subset of Twilio Long Codes that send to multiple networks in France. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio reports a recovery and monitors service stability.
Twilio·SMS Delivery Delays from Twilio to Virgin Mobile Colombia
Twilio reports SMS delivery delays to Virgin Mobile subscribers in Colombia. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio has observed a recovery and is monitoring service stability.
Twilio·SMS Delivery Delays from Twilio to Telenor Pakistan
Twilio SMS delivery to Telenor network subscribers in Pakistan was delayed from 12:27 to 17:34 UTC on 12 November 2026. Twilio identified the cause, then saw a recovery. Twilio reports the incident as resolved, and the delay lasted about five hours.
Twilio·MMS Delivery Failures from Twilio to GCI United States
Twilio MMS delivery to GCI network subscribers in the United States failed. The affected components were MMS Long Code, MMS Short Code, and MMS Toll-Free in North America, and their carrier network links. Twilio reports that the incident is resolved. It lasted about 4 minutes.
Twilio·SMS Delivery Failures from Twilio Long Codes to AT&T United States
Twilio SMS delivery failures affected Long Code messages to AT&T subscribers in the United States. The components affected were SMS Long Code, North America and CARRIER NETWORK - SMS Long Code, North America. Twilio reports that the incident is resolved. It lasted about 4 hours.
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