SMS Delivery Delays and Failures from Twilio Alphanumeric Sender Type to T-Mobile Austria
SendGrid reports SMS delivery delays and failures for messages from Twilio Alphanumeric Sender Type to T-Mobile subscribers in Austria. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. SendGrid has identified the cause and work is in progress to fix it.
State
Identified
Started
2 h ago
2026-11-02 15:32 UTC
Ongoing for
1 h 37 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
10 min 11%
Identified
1 h 27 min 89%
Updates
Times in UTCAs posted by SendGrid
Twilio customers may be experiencing SMS delivery delays and failures from Twilio Alphanumeric Sender Type to T-Mobile network subscribers in Austria. 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.
Twilio customers may be experiencing SMS delivery delays and failures from Twilio Alphanumeric Sender Type to T-Mobile network subscribers in Austria. 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 and failures from Twilio Alphanumeric Sender IDs to T-Mobile network subscribers in Austria. 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
57
Days with an incident
38
Median duration
7 h 14 min
This incident
78% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·Some Customers May Have Incorrect Balances Reflected on Their Account
SendGrid reports incorrect balances on customer accounts that use Billing. The issue affects the SendGrid Billing component and the Twilio platform Billing component. SendGrid is investigating the issue as of 2 November 2026.
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 Verify Silent Network Auth does not work for the CARRIER NETWORK on XL Axiata in Indonesia. Device verification can time out during API transactions. SendGrid identified the problem and continues to work on it. API transactions can use SMS OTP as a secondary method.
SendGrid·Voice Call Failures From a Subset of Twilio Philippines Phone Numbers to Multiple Networks in Philippines
Voice calls fail from some SendGrid Philippines phone numbers to subscribers on many networks in the Philippines. The Voice, APAC and carrier network components are degraded. SendGrid identified the cause and continues work to resolve the issue.
SendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes to Google Voice United States
SendGrid reports SMS delivery delays from a subset of short codes to Google Voice subscribers in the United States. The affected components are SMS Short Code and CARRIER NETWORK - SMS Short Code in North America. SendGrid resolved the incident after 6 hours and 32 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