SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Puerto Rico
SendGrid reports SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. This affects SMS, Latin America and the related carrier network. SendGrid has identified the cause and works to resolve the issue.
State
Identified
Started
1 h ago
2026-11-02 21:21 UTC
Ongoing for
1 h 29 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 3 min 70%
Identified
26 min 30%
Updates
Times in UTCAs posted by SendGrid
Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 1 hour or as soon as more information becomes available.
Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. Our team is actively investigating this issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 1 hour or as soon as more information becomes available.
Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. Our team has identified the cause, and is working to resolve the issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 1 hour or as soon as more information becomes available.
Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. Our team is actively investigating this issue. Message delivery may succeed, but delivery receipts may be delayed. 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
59
Days with an incident
38
Median duration
6 h 53 min
This incident
78% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·Voice Call One-Way Audio from Brazil to a Subset of Twilio Numbers
On October 31, 2026, from 5AM to 8AM PT, customers may have experienced an issue with some inbound calls to Twilio Brazil numbers having no audio, and some calls also dropping. The impact was linked to a carrier fiber cut and a fallback route that could not handle the traffic load. The issue has been resolved and Voice is operating normally.
SendGrid·Some Customers May Have Incorrect Balances Reflected on Their Account
SendGrid reports incorrect balances on some customer accounts. The issue affects Billing and TWILIO PLATFORM - Billing. SendGrid is investigating the issue.
SendGrid·SMS Delivery Delays and Failures from Twilio Alphanumeric Sender Type to T-Mobile Austria
SendGrid reported SMS delivery delays and failures from Twilio Alphanumeric Sender Type to T-Mobile network subscribers in Austria. The affected components were SMS, Europe and CARRIER NETWORK - SMS, Europe. SendGrid reported the incident as resolved. The incident lasted about 5 hours and 13 minutes.
SendGrid·SMS Delivery Delays from a Subset of Twilio Long Codes to T-Mobile and O2 Czech Republic
SendGrid reported SMS delivery delays from a subset of Twilio Long Codes to T-Mobile and O2 subscribers in the Czech Republic. The affected components were SMS, Europe and CARRIER NETWORK - SMS, Europe. SendGrid resolved the incident after 174 minutes.
SendGrid·Silent Network Authentication (SNA) Missing Redirects on XL Axiata in Indonesia
SendGrid reported that Silent Network Authentication did not work on XL Axiata in Indonesia. Device verification timed out during API transactions. SendGrid reported the incident as resolved after 13 hours and 27 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.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