DI SMS 365 (SMSx) | Operator Services | Application Maintenance | PCR Number #PCRSDI-12408
Services :: DI SMS 365 (SMSx) PCR Number :: PCRSDI-12408 Start Date and Time (GMT):: 12th November 2026 07:00 Hrs. End Date and Time (GMT):: 12th November 2026 11:00 Hrs. Impact: Mobile Terminating (MT) Traffic: Potential Latency Mobile Originated (MO) Traffic: Potential Latency DR Notification: Potential Latency Description: Digital Interconnect has scheduled a planned maintenance to carry out activities on the internal applications. If you experience any issues during this maintenance , please contact the Operator Service NOC immediately at operatorservices.noc@sinch.com or +1 470.300.8394 (select 'support' from the menu, option 2 for Digital Interconnect and then option 1) and reference this notification.
The latest update from Sinch.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Sinch
Services :: DI SMS 365 (SMSx) PCR Number :: PCRSDI-12408 Start Date and Time (GMT):: 12th November 2026 07:00 Hrs. End Date and Time (GMT):: 12th November 2026 11:00 Hrs. Impact: Mobile Terminating (MT) Traffic: Potential Latency Mobile Originated (MO) Traffic: Potential Latency DR Notification: Potential Latency Description: Digital Interconnect has scheduled a planned maintenance to carry out activities on the internal applications. If you experience any issues during this maintenance , please contact the Operator Service NOC immediately at operatorservices.noc@sinch.com or +1 470.300.8394 (select 'support' from the menu, option 2 for Digital Interconnect and then option 1) and reference this notification.
Affected components
4Sinch in the last 90 days
Full historyIncidents in 90 days
55
Days with an incident
36
Median duration
2 h 59 min
This incident
Not comparable
Other Sinch incidents
All incidents
Sinch·Delivery Issue - SMS Verification - China
Sinch reports delivery issues for SMS Verification traffic to China. The affected components are SMS Verification and Verification - SMS Verification. Sinch is still investigating the issue.
Sinch·Delivery Issue Czech Republic - T-Mobile
Sinch reported a delivery issue in the Czech Republic on the T-Mobile network. The issue affected SMS - EMEA and External Connectivity - SMS - EMEA. Sinch reports that the issue is resolved and that it lasted from 00:30 UTC to 04:35 UTC.
Sinch·Delivery Issue - France
Sinch reported a delivery issue in France that affected SMS - EMEA and External Connectivity - SMS - EMEA. The issue is resolved. Sinch reports that it started on 2026-11-04 at 15:08 UTC and ended on 2026-11-05 at 12:46 UTC.
Sinch·Delivery Issue Spain - DigiMobil
Sinch reported a delivery issue in Spain for DigiMobil. The issue affected SMS - EMEA and External Connectivity - SMS - EMEA. Sinch reports that the issue is resolved. It lasted from 01:45 UTC to 02:37 UTC.
Sinch·Delivery Issue Colombia - Claro
Sinch reported a delivery issue in Colombia on the Claro network. The issue affected SMS - LATAM and External Connectivity - SMS - LATAM. Sinch reports that the issue is resolved.
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