Live

SMS Delivery Delays from Twilio to Entel Bolivia

0

Twilio reports SMS delivery delays to Entel network subscribers in Bolivia. The delay affects SMS in Latin America and the related carrier network. Twilio has identified the cause and is working to resolve the issue.

State

Identified

Started

1 h ago

2026-11-03 03:51 UTC

Ongoing for

1 h 1 min

Worst impact

Degraded

Timeline

4 updates
03:5104:0604:2104:3604:52
DegradedUpdate postedTimes in UTC

Investigating

15 min 24%

Identified

46 min 76%

Updates

Times in UTC

As posted by Twilio

Identified2026-11-03 04:15 UTC

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.

Investigating2026-11-03 04:12 UTC

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.

Identified2026-11-03 04:03 UTC

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.

Investigating2026-11-03 03:54 UTC

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

2
SMS, Latin AmericaCARRIER NETWORK - SMS, Latin America

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

66

Days with an incident

39

Median duration

6 h 32 min

This incident

85% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

33 days
median 6 h 32 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·MMS Delivery Receipt Delays from a Subset of Twilio Long Codes to GCI Communication United States

Twilio MMS delivery receipts are delayed from some Twilio Long Codes to GCI Communication subscribers in the United States. The affected components are MMS Long Code in North America, the carrier network, and Zipwhip messaging. Twilio has identified the cause and is working to resolve the issue. Message delivery may still succeed.

Degradedupdated 3 min ago

Twilio·SMS Delivery Delays from Twilio to Lycamobile United Kingdom

Twilio SMS delivery delays affect the SMS and carrier network components in Europe. Delivery goes to Lycamobile network subscribers in the United Kingdom. Twilio reports a recovery and monitors service stability.

Degradedupdated 1 h ago

Twilio·Voice Call Audio Delays

Twilio voice calls from network subscribers to Twilio Phone Numbers can have audio delays and high packet loss. The affected components are Voice and CARRIER NETWORK Voice in North America, Latin America, APAC, Europe, and the Middle East and Africa. Twilio reports a recovery and monitors service stability.

Degradedupdated 2 h ago

Twilio·RateQueue Host Down Did Not Recover

Twilio SMS message delivery is delayed. The issue affects SMS and Programmable Messaging SMS. Twilio identified the problem and applied a mitigation. No messages are lost. The incident started 40 minutes ago and is not resolved.

Degradedupdated 2 h ago

Twilio·Media Streams Audio Delays

Twilio Media Streams audio delays affected Media Streams US1 and Programmable Voice US1. Twilio reports that the incident is resolved. The outage lasted 70 minutes.

Resolvedresolved 2 h ago

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=twilio
Slack
/feed subscribe https://outages.cc/feed.xml?providers=twilio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane