External Maintenance - United States - T-Mobile
United States - T-Mobile has scheduled a maintenance. Impact SMS: Clients may experience delayed or failed Short Code and 10DLC MT/MO traffic towards T-Mobile US Impact MMS: Clients may experience delayed or failed Short Code and 10DLC MT/MO traffic towards T-Mobile US Maintenance Start Time: 2026-11-5 04:00 UTC Maintenance End Time: 2026-11-5 13:00 UTC
The latest update from Sinch.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Sinch
United States - T-Mobile has scheduled a maintenance. Impact SMS: Clients may experience delayed or failed Short Code and 10DLC MT/MO traffic towards T-Mobile US Impact MMS: Clients may experience delayed or failed Short Code and 10DLC MT/MO traffic towards T-Mobile US Maintenance Start Time: 2026-11-5 04:00 UTC Maintenance End Time: 2026-11-5 13:00 UTC
Affected components
8Sinch in the last 90 days
Full historyIncidents in 90 days
51
Days with an incident
34
Median duration
2 h 59 min
This incident
Not comparable
Other Sinch incidents
All incidents
SinchΒ·Delivery Issue Colombia - Claro
Sinch reports a delivery issue for SMS in Colombia on the Claro network. The issue affects SMS - LATAM and External Connectivity - SMS - LATAM. Sinch reports delayed MTs, delayed MOs, missing delivery receipts, and late delivery receipts. Sinch is investigating.

SinchΒ·Delivery Issue Sweden - Telavox
Sinch reported a delivery issue in Sweden for Telavox. The issue affected SMS - EMEA and External Connectivity - SMS - EMEA. Sinch resolved the incident. It lasted 48 minutes.

SinchΒ·Delivery Issue Canada - ICE Wireless
Sinch reported a major SMS delivery outage in Canada. The outage affected ShortCode and Toll Free SMS, including external connectivity for both. Sinch resolved the incident. The outage lasted 5 hours and 39 minutes.

SinchΒ·Delivery Issue Bolivia - Entel
Sinch reported a delivery issue for SMS to Entel in Bolivia. The issue affected SMS - LATAM and External Connectivity - SMS - LATAM. Sinch reports that the issue is resolved. It lasted from 02:35 UTC to 07:09 UTC on 2026-11-03.

SinchΒ·Delivery Issue United States - Google Voice
Sinch reported a delivery issue for SMS - US - ShortCode and External Connectivity - SMS - US - ShortCode in the United States with Google Voice. Sinch resolved the incident. The incident started on 2026-11-01 at 23:57 UTC and ended on 2026-11-02 at 04:38 UTC.
Follow Sinch
Your coding agent knows when Sinch is down, and tells you when a failure is theirs, not yours. You can also get Sinch 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 "sinch" and tell me if Sinch 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=sinch/feed subscribe https://outages.live/feed.xml?providers=sinchFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane