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.
State
Monitoring
Started
2 h ago
2026-11-03 03:07 UTC
Ongoing for
1 h 46 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
10 min 10%
Identified
30 min 28%
Monitoring
1 h 6 min 62%
Updates
Times in UTCAs posted by Twilio
We have observed a recovery in SMS delivery from Twilio to Lycamobile network subscribers in the United Kingdom 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 Lycamobile network subscribers in the United Kingdom. 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 Lycamobile network subscribers in the United Kingdom. Our team is actively investigating this 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 Lycamobile network subscribers in the United Kingdom. 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 Lycamobile network subscribers in the United Kingdom. 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
66
Days with an incident
39
Median duration
6 h 32 min
This incident
73% shorter than the median
Other Twilio incidents
All incidentsTwilio·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.
Twilio·SMS Delivery Delays from Twilio to Entel Bolivia
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.
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.
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.
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.
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