Voice Call Audio Quality Degradation from a Subset of Twilio Mobile Numbers to Claro Colombia
Twilio voice call audio quality was degraded from some Twilio Mobile Numbers to Claro network subscribers in Colombia. Voice in Latin America was affected. Twilio reports that the incident is resolved. It lasted about 36 minutes.
State
Resolved
Started
Lasted
36 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
36 min 100%
Updates
Times in UTCAs posted by Twilio
The incident has been resolved and voice calls from a subset of Twilio Mobile Numbers to network subscribers in Colombia are operating normally.
Twilio customers may be experiencing voice call audio quality degradation from a subset of Twilio Mobile Numbers to Claro network subscribers 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
85
Days with an incident
42
Median duration
7 h 14 min
This incident
92% shorter than the median
Other Twilio incidents
All incidentsTwilio·Voice Call Failures from a Subset of Twilio Phone Numbers to Chile
Twilio reports voice call failures from a subset of Twilio phone numbers to network subscribers in Chile. The issue affects Voice in Latin America and the related carrier network. Twilio is investigating the issue.
Twilio·Notification Delivery Logs Unavailable in Console
Twilio notification delivery logs were unavailable in Console for Conversations and Programmable Messaging Conversations. Twilio mitigated the issue and monitored system performance. The incident is resolved and lasted 8 minutes.
Twilio·Notification Logs Unavailable in Console
Twilio notification delivery logs did not populate new data in the Console. The Notify component was affected. Twilio resolved the issue and logs returned to normal. The outage lasted about 1 hour and 35 minutes.
Twilio·SMS Delivery Delays between Twilio and T-Mobile in Czech Republic
Twilio SMS delivery delays affected messages to T-Mobile network subscribers in the Czech Republic. The service also affected the carrier network SMS component in Europe. Twilio resolved the incident, and the outage lasted about 9 hours.
Twilio·Voice Call Silent and One-Way Audio Between a Subset of Twilio Phone Numbers and Multiple Networks in Colombia
Voice calls have silent or one-way audio between some 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.
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