Voice Call Failures from a Subset of Twilio Phone Numbers to Argentina
Voice calls from a subset of Twilio Phone Numbers to network subscribers in Argentina failed. The Voice, Latin America and CARRIER NETWORK - Voice, Latin America components had degraded service. Twilio reports that the incident is resolved. The incident lasted about 7 hours and 38 minutes.
State
Resolved
Started
Lasted
7 h 38 min
Worst impact
Degraded
Timeline
6 updatesInvestigating
21 min 5%
Identified
6 h 54 min 90%
Monitoring
23 min 5%
Updates
Times in UTCAs posted by Twilio
The incident has been resolved and voice calls from a subset of Twilio Phone Numbers to network subscribers in Argentina are operating normally.
We have observed a recovery in voice calls from a subset of Twilio Phone Numbers to network subscribers in Argentina and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing voice call failures from a subset of Twilio Phone Numbers to network subscribers in Argentina. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available.
Twilio customers may be experiencing voice call failures from a subset of Twilio Phone Numbers to network subscribers in Argentina. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing voice call failures from Twilio Phone Numbers to network subscribers in Argentina. 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 failures from a subset of Twilio Phone Numbers to network subscribers in Argentina. 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
170
Days with an incident
56
Median duration
5 h 47 min
This incident
1.3× the median
Other Twilio incidents
All incidentsTwilio·On Call Engineers are Investigating
Twilio reported a problem with User Account Roles on the Twilio Platform in the Other component. Twilio investigated the issue and then reported it resolved. The incident lasted about 18 minutes.
Twilio·SMS Delivery Delays from Twilio to ISP Telecom United States
SMS delivery delays affected Twilio messages to ISP Telecom network subscribers in the United States. The affected components were SMS Long Code, SMS Short Code, and SMS Toll-Free in North America, including the carrier network. Twilio reports that the incident is resolved and that SMS delivery operates normally. The incident lasted about 9 hours and 37 minutes.
Twilio·SMS Delivery Failures from a Subset of Twilio Phone Numbers to Zong Pakistan
SMS delivery failures affected a subset of Twilio phone numbers to Zong network subscribers in Pakistan. The incident is resolved and lasted 8 hours and 3 minutes.
Twilio·Text to Speech Timeouts
Twilio reports timeouts when users generate speech from text through ElevenLabs Text to Speech in the US1 region, including Speech Recognition (Gather Speech) US1. Twilio later identified the issue, monitored recovery, and marked the incident resolved. The outage lasted about 4 hours and 34 minutes.
Twilio·Voice Call Silent and One-Way Audio from Colombia to a Subset of Twilio Phone Numbers
Voice calls from network subscribers in Colombia to a subset of Twilio Phone Numbers have silent or one-way audio. The issue affects Voice, Latin America and the carrier network for Voice, Latin America. Twilio reports a recovery and monitors service stability.
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