SMS Delivery Delays from Twilio to Entel Bolivia
Twilio reports SMS delivery delays to Entel network subscribers in Bolivia. The delays affect SMS in Latin America and the related carrier network. Twilio identified the cause and work is in progress to resolve the issue.
State
Identified
Started
2 h ago
2026-11-03 03:51 UTC
Ongoing for
1 h 56 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
12 min 10%
Identified
1 h 44 min 90%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing SMS delivery delays from Twilio to Entel network subscribers in Bolivia. 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 Entel network subscribers in Bolivia. 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 Entel network subscribers in Bolivia. 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
67
Days with an incident
39
Median duration
6 h 53 min
This incident
72% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
Twilio SMS delivery is delayed from a subset of Twilio Short Codes and Long Codes to Brisanet subscribers in Brazil. This affects SMS in Latin America and the carrier network for SMS in Latin America. Twilio identified the cause and is working to resolve the issue.
Twilio·MMS Delivery Receipt Delays from a Subset of Twilio Long Codes to GCI Communication United States
Twilio MMS delivery receipts are delayed from a subset of Twilio Long Codes to GCI Communication subscribers in the United States. The affected components are MMS Long Code in North America. Twilio has identified the cause and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed.
Twilio·SMS Delivery Delays from Twilio to Lycamobile United Kingdom
Twilio reports SMS delivery delays to Lycamobile subscribers in the United Kingdom. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio observed a recovery and monitors service stability.
Twilio·Voice Call Audio Quality Degradation from Network Subscribers to Twilio Phone Numbers
Twilio reports degraded voice call audio for calls from network subscribers to Twilio phone numbers. The affected regions are North America, Latin America, APAC, Europe, and the Middle East and Africa. Twilio observed a recovery and now monitors service stability.
Twilio·RateQueue Host Down Did Not Recover
Twilio SMS messages have delays in the PROGRAMMABLE MESSAGING - SMS component. No messages are lost. Twilio identified and mitigated the issue and continues to investigate the root cause.
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