United States SMS and MMS Carrier Maintenance - T-Mobile
The T-Mobile network in the United States is conducting a planned maintenance from 04 November 2026 at 20:00 PST until 11 November 2026 at 05:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from T-Mobile United States handsets when sending via long codes and short codes.
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 04 November 2026 at 20:00 PST until 11 November 2026 at 05:00 PST. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from T-Mobile United States handsets when sending via long codes and short codes.
Affected components
8SendGrid in the last 90 days
Full historyIncidents in 90 days
70
Days with an incident
39
Median duration
7 h 20 min
This incident
Not comparable
Other SendGrid incidents
All incidentsSendGrid·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Carriers in United States
SendGrid reports MMS delivery delays from a subset of Twilio Long Codes to multiple small carriers in the United States. The affected components are MMS Long Code, North America. SendGrid has identified the cause and a fix is in progress. Messages may arrive, but delivery receipts may be late.
SendGrid·MMS Delivery Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States
SendGrid reports MMS delivery delays and delivery receipt delays from a subset of Twilio Long Codes and Short Codes to AT&T subscribers in the United States. The affected components are MMS Long Code and Short Code in North America. SendGrid has identified the cause and continues to work on the fix.
SendGrid·MMS Delivery Delays and Failures from a Subset of Twilio Short Codes to T-Mobile and Verizon United States
SendGrid reports MMS delivery delays and failures from a subset of Twilio Short Codes to T-Mobile and Verizon subscribers in the United States. The affected components are MMS Short Code and CARRIER NETWORK MMS Short Code in North America. SendGrid reports that the incident is resolved. It lasted about 6 hours and 18 minutes.
SendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
SendGrid reported SMS delivery delays from a subset of Twilio Short Codes and Long Codes to Brisanet network subscribers in Brazil. The incident affected SMS in Latin America and the carrier network for SMS in Latin America. SendGrid reports that the incident is resolved. The outage lasted about 14 hours and 47 minutes.
SendGrid·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks United States
SendGrid reports MMS delivery delays and failures from a subset of Twilio Long Codes to subscribers on multiple small networks in the United States. The affected components are MMS Long Code, North America and CARRIER NETWORK - MMS Long Code, North America. SendGrid reports that the incident is resolved after 16 hours and 15 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