SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Puerto Rico
Twilio reports delays for SMS delivery receipts from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. This affects SMS in Latin America and the Carrier Network for SMS in Latin America. Message delivery can succeed, but delivery receipts can arrive late. Twilio has identified the cause and continues to work on a fix.
State
Identified
Started
Ongoing for
2 h 10 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
3 min 3%
Identified
2 h 6 min 97%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 2 hours or as soon as more information becomes available.
Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 1 hour or as soon as more information becomes available.
Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. Our team is actively investigating this issue. Message delivery may succeed, but delivery receipts may be delayed. 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
80
Days with an incident
42
Median duration
7 h 17 min
This incident
70% shorter than the median
Other Twilio incidents
All incidentsTwilio·Voice Call Silent and One-Way Audio between a Subset of Twilio Phone Numbers and Multiple Networks in Colombia
Twilio Voice calls have silent audio and one-way audio between some Twilio Phone Numbers and network subscribers in Colombia. The affected components are Voice, Latin America and CARRIER NETWORK - Voice, Latin America. Twilio reports that it identified the cause and is working to resolve the issue.
Twilio·SMS Delivery Failures from Twilio to Lycamobile France
Twilio SMS delivery to Lycamobile subscribers in France fails. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio reports recovery and monitors service stability.
Twilio·Voice Call Failures from a Subset of Twilio Mobile Numbers to Argentina
Twilio voice calls from some Twilio Mobile Numbers to Telefonica network subscribers in Argentina do not connect. Voice in Latin America and the carrier network for that region are degraded. Twilio identified the cause and works to resolve the issue.
Twilio·Voice Call Post Dial Delay from a Subset of Twilio Canada Phone Numbers to Rogers Wireless and Fido Canada
Twilio voice calls from a subset of Twilio Canada phone numbers to Rogers Wireless and Fido subscribers in Canada had post dial delay. This incident affected Voice in North America. Twilio reports that the incident is resolved and calls operate normally. The incident lasted about 5 hours and 13 minutes.
Twilio·Search Delays on Enterprise Knowledge
Twilio reported slow search and content ingestion on Enterprise Knowledge, including use with Conversation Intelligence. Twilio reports that the incident is resolved. The incident lasted about 4 hours and 33 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.cc/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.cc/feed.xml?providers=twilio/feed subscribe https://outages.cc/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane