SMS Delivery Delays from Twilio to Lycamobile United Kingdom
SendGrid reports SMS delivery delays from Twilio to Lycamobile subscribers in the United Kingdom. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. SendGrid reports a recovery in delivery and monitors service stability.
State
Monitoring
Started
2 h ago
2026-11-03 03:07 UTC
Ongoing for
1 h 32 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
16 min 18%
Identified
24 min 26%
Monitoring
51 min 56%
Updates
Times in UTCAs posted by SendGrid
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
2SendGrid in the last 90 days
Full historyIncidents in 90 days
65
Days with an incident
39
Median duration
6 h 32 min
This incident
77% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·SMS Delivery Delays from Twilio to Entel Bolivia
SendGrid reports SMS delivery delays to Entel network subscribers in Bolivia. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. SendGrid identified the cause and is working to resolve the issue.
SendGrid·Voice Call Audio Delays
SendGrid reports voice call audio delays and high packet loss on calls from network subscribers to Twilio Phone Numbers. The affected regions are North America, Latin America, APAC, Europe, and Middle East & Africa. SendGrid observed a recovery and now monitors service stability.
SendGrid·RateQueue Host Down Did Not Recover
SendGrid SMS message delivery has delays. The issue affects SMS and Programmable Messaging - SMS. SendGrid states that the cause is identified and mitigated, and no messages are lost.
SendGrid·Media Streams Audio Delays
SendGrid reports that audio delays affect Media Streams US1 and PROGRAMMABLE VOICE US1 - Media Streams US1. SendGrid resolved this incident. The incident lasted 67 minutes.
SendGrid·SMS Delivery Delays and Failures from Twilio to Claro Puerto Rico
SendGrid reports SMS delivery delays and failures from Twilio to Claro network subscribers in Puerto Rico. The SMS Latin America components and the carrier network for SMS Latin America are affected. SendGrid identified the cause and works to resolve the issue.
Follow SendGrid
Your coding agent knows when SendGrid is down, and tells you when a failure is theirs, not yours. You can also get SendGrid 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 "sendgrid" and tell me if SendGrid 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=sendgrid/feed subscribe https://outages.live/feed.xml?providers=sendgridFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane