Live

SMS Delivery Delays from Twilio to Virgin Mobile Colombia

0

Twilio reports SMS delivery delays to Virgin Mobile subscribers in Colombia. The delay affects the SMS and carrier network components in Latin America. Twilio has identified the cause and is working to resolve the issue.

State

Identified

Started

Ongoing for

2 h 17 min

Worst impact

Degraded

Timeline

3 updates
13:2914:0314:3715:1115:45
DegradedUpdate postedTimes in UTC

Investigating

4 min 3%

Identified

2 h 12 min 97%

Updates

Times in UTC

As posted by Twilio

Identified

Twilio customers may be experiencing SMS delivery delays from Twilio to Virgin Mobile network subscribers in Colombia. 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.

Identified

Twilio customers may be experiencing SMS delivery delays from Twilio to Virgin Mobile network subscribers in Colombia. 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.

Investigating

Twilio customers may be experiencing SMS delivery delays from Twilio to Virgin Mobile network subscribers in Colombia. 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

120

Days with an incident

48

Median duration

7 h 17 min

This incident

69% shorter than the median

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

33 days
median 7 h 17 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·SMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Networks in France

Twilio reports SMS delivery delays from a subset of Twilio Long Codes to network subscribers on multiple networks in France. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio has identified the cause and is working to resolve the issue.

Degraded

Twilio·SMS Delivery Delays from Twilio to Telenor Pakistan

SMS delivery delays affect Twilio messages to Telenor network subscribers in Pakistan. The affected components are SMS, APAC and CARRIER NETWORK - SMS, APAC. Twilio reports a recovery and monitors service stability.

Degraded

Twilio·MMS Delivery Failures from Twilio to GCI United States

Twilio MMS delivery to GCI network subscribers in the United States failed. The affected components were MMS Long Code, MMS Short Code, and MMS Toll-Free in North America, and their carrier network links. Twilio reports that the incident is resolved. It lasted about 4 minutes.

Resolved

Twilio·SMS Delivery Failures from Twilio Long Codes to AT&T United States

Twilio SMS delivery failures affected Long Code messages to AT&T subscribers in the United States. The components affected were SMS Long Code, North America and CARRIER NETWORK - SMS Long Code, North America. Twilio reports that the incident is resolved. It lasted about 4 hours.

Resolved

Twilio·SMS Delivery Failures from Twilio to Orange Sierra Leone

SMS delivery failures affect Twilio messages to Orange network subscribers in Sierra Leone. The affected components are SMS, Middle East and Africa and the carrier network for SMS, Middle East and Africa. Twilio has identified the cause and is working to resolve the issue.

Degraded

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane