SMS Delivery Delays from Twilio to Altan Redes Mexico
Twilio reports SMS delivery delays to Altan Redes network subscribers in Mexico. The delays affect SMS in Latin America and the carrier network for SMS in Latin America. Twilio has seen a recovery in SMS delivery and monitors service stability.
State
Monitoring
Started
Ongoing for
8 h 44 min
Worst impact
Degraded
Timeline
6 updatesInvestigating
13 min 3%
Identified
5 h 9 min 59%
Monitoring
3 h 22 min 38%
Updates
Times in UTCAs posted by Twilio
We have observed a recovery in SMS delivery from Twilio to Altan Redes network subscribers in Mexico and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.
We have observed a recovery in SMS delivery from Twilio to Altan Redes network subscribers in Mexico 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 SMS delivery delays from Twilio to Altan Redes network subscribers in Mexico. 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 SMS delivery delays from Twilio to Altan Redes network subscribers in Mexico. 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 SMS delivery delays from Twilio to Altan Redes network subscribers in Mexico. 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 SMS delivery delays from Twilio to Altan Redes network subscribers in Mexico. 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
137
Days with an incident
51
Median duration
6 h 32 min
This incident
1.3× the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from Twilio to Orange Mali
SMS delivery delays affected Twilio customers who send messages to Orange network subscribers in Mali. Twilio reported the incident as resolved and said SMS delivery operates normally again. The incident lasted about 4 hours and 23 minutes.
Twilio·SMS Delivery Delays from Twilio to MTN Nigeria
Twilio reports SMS delivery delays to MTN network subscribers in Nigeria. The affected components are SMS, Middle East & Africa and CARRIER NETWORK - SMS, Middle East & Africa. Twilio has identified the cause and sees a recovery in SMS delivery. Twilio monitors service stability.
Twilio·SMS Delivery Delays from a Subset of Twilio Phone Numbers to Telenor Pakistan
SMS delivery delays affected a subset of Twilio phone numbers that send to Telenor network subscribers in Pakistan. The SMS APAC and carrier network SMS APAC components were degraded. Twilio reports that the incident is resolved, and the outage lasted 9 hours and 5 minutes.
Twilio·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 has identified the cause and is working to resolve the issue.
Twilio·Voice Call Failures from Twilio Phone Numbers to Multiple Networks in Colombia, Mexico, Chile, and Costa Rica
Twilio voice calls from a subset of Twilio Phone Numbers to network subscribers failed in Colombia, Mexico, Chile, and Costa Rica. Twilio identified the cause and monitored service stability. The incident is resolved and the outage lasted 21 hours and 36 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