Voice Call Failures from a Subset of Twilio Phone Numbers to Multiple Networks in Colombia, Mexico, Chile, and Costa Rica
Twilio voice calls fail from a subset of Twilio phone numbers to network subscribers in Colombia, Mexico, Chile, and Costa Rica. Twilio has identified the cause and is working to resolve the issue. This affects Voice, Latin America and the related carrier network.
State
Identified
Started
Ongoing for
55 min
Worst impact
Degraded
Timeline
1 updateIdentified
55 min 100%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing voice call failures from a subset of Twilio Phone Numbers to network subscribers in Colombia, Mexico, Chile, and Costa Rica. 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.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
133
Days with an incident
49
Median duration
6 h 18 min
This incident
86% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from Twilio to Brisanet Brazil
Twilio reports SMS delivery delays to Brisanet network subscribers in Brazil. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio is investigating the issue.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Multiple Networks in India
SMS delivery delays affect a subset of Twilio Short Codes to subscribers on multiple networks in India. The SMS and carrier network components in APAC are degraded. Twilio reports a recovery and monitors service stability.
Twilio·Silent Network Authentication (SNA) Failure Increase and Gateway API (Lookup API) Failure Increase in United Kingdom
Twilio reported failures in Silent Network Authentication (SNA) and in Lookup API transactions in the United Kingdom. Twilio identified the cause and monitored recovery. Twilio resolved the incident after 5 hours and 11 minutes.
Twilio·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in India
Twilio SMS delivery receipts were delayed from a subset of Twilio Short Codes to subscribers on multiple networks in India. The incident affected SMS in APAC and the related carrier network. Twilio reports that the incident is resolved and lasted 48 minutes.
Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Multiple Networks in India
Twilio SMS delivery from a subset of Twilio Short Codes to multiple networks in India had delays. The SMS and carrier network components in APAC were affected. Twilio resolved the incident after 3 hours and 12 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