SMS Delivery Delays from Twilio to Lycamobile United Kingdom
SendGrid reports SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. SendGrid reports a recovery in SMS delivery and monitors service stability.
State
Monitoring
Started
2 h ago
2026-11-03 03:07 UTC
Ongoing for
1 h 48 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
10 min 9%
Identified
30 min 28%
Monitoring
1 h 8 min 63%
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
66
Days with an incident
39
Median duration
6 h 32 min
This incident
73% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·MMS Delivery Receipt Delays from a Subset of Twilio Long Codes to GCI Communication United States
SendGrid reports MMS delivery receipt delays from a subset of Twilio long codes to GCI Communication subscribers in the United States. The delay affects MMS Long Code services in North America. SendGrid identified the cause and works to resolve the issue. Message delivery can succeed, but delivery receipts can arrive late.
SendGrid·SMS Delivery Delays from Twilio to Entel Bolivia
SendGrid reports SMS delivery delays from Twilio to Entel network subscribers in Bolivia. The SMS and carrier network components in Latin America are degraded. 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 voice routes to Twilio phone numbers. The affected regions are North America, Latin America, APAC, Europe, and the Middle East and Africa. SendGrid reports a recovery in these calls and now monitors service stability.
SendGrid·RateQueue Host Down Did Not Recover
SendGrid SMS and Programmable Messaging SMS messages have delays. No messages are lost. SendGrid identified and mitigated the issue, and continues to investigate the root cause.
SendGrid·Media Streams Audio Delays
SendGrid reports audio delays on Media Streams US1 and PROGRAMMABLE VOICE US1 - Media Streams US1. SendGrid reported the incident as investigating. The incident is now resolved and it lasted 70 minutes.
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.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 "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.cc/feed.xml?providers=sendgrid/feed subscribe https://outages.cc/feed.xml?providers=sendgridFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane