United States SMS and MMS Carrier Maintenance - T-Mobile
The T-Mobile network in the United States is conducting a planned maintenance from 03 November 2026 at 20:00 PST until 04 November 2026 at 05:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to T-Mobile United States handsets when sending via long codes and short codes. We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.
The latest update from SendGrid.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by SendGrid
The T-Mobile network in the United States is conducting a planned maintenance from 03 November 2026 at 20:00 PST until 04 November 2026 at 05:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to T-Mobile United States handsets when sending via long codes and short codes. We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.
Affected components
8SendGrid in the last 90 days
Full historyIncidents in 90 days
67
Days with an incident
39
Median duration
7 h 14 min
This incident
Not comparable
Other SendGrid incidents
All incidentsSendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
SendGrid reports SMS delivery delays from a subset of Twilio Short Codes and Long Codes to Brisanet subscribers in Brazil. The SMS, Latin America and CARRIER NETWORK - SMS, Latin America components are degraded. SendGrid identified the cause and continues to work on a fix.
SendGrid·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 affected components are MMS Long Code, North America, CARRIER NETWORK - MMS Long Code, North America, and ZIPWHIP MESSAGING - MMS Long Code, North America. SendGrid has identified the cause and works to resolve the issue.
SendGrid·SMS Delivery Delays from Twilio to Entel Bolivia
SendGrid reports SMS delivery delays from Twilio to Entel network subscribers in Bolivia. The delays affect SMS in Latin America and the related carrier network. The incident is resolved and lasted about 9 hours and 37 minutes.
SendGrid·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 issue affected SMS in Europe and the carrier network for SMS in Europe. SendGrid reports that the incident is resolved. The incident lasted about 160 minutes.
SendGrid·Voice Call Audio Quality Degradation for Outbound Calls from Twilio to US Network Subscribers
SendGrid reports voice call audio delays and high packet loss for calls from network subscribers to Twilio phone numbers. The affected regions are North America, Latin America, APAC, Europe, and the Middle East and Africa. SendGrid reports a recovery and monitors service stability.
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