CANCELED - DI SMS 365 (SMSX) | Operator Services | Application, Database and System Maintenance || PCR Number #PCRSDI-12384
This maintenance is canceled for 10/29/26 05:00 Hrs (GMT) Services :: DI SMS 365 (SMSX) PCR Number :: PCRSDI-12384 Start Date and Time (GMT):: 29th October 2026 05:00 Hrs. End Date and Time (GMT):: 29th October 2026 10:00 Hrs. Impact Mobile Terminating (MT) Traffic : No Impact Mobile Originated (MO) Traffic : No Impact DR Notification : No Impact Report Manager Access : Impacted. Report Manager Statistics : Impacted. Description: Digital Interconnect has scheduled a planned maintenance to carry out activities on the internal application and systems. Report Manager may experience several slowdowns up to 1 minute and delayed up to 1 minute data in reports. 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
Started
4 d ago
2026-10-29 05:00 UTC
Ongoing for
4 days
Worst impact
Maintenance
Timeline
1 updateScheduled
4 days 100%
Updates
Times in UTCAs posted by Sinch
This maintenance is canceled for 10/29/26 05:00 Hrs (GMT) Services :: DI SMS 365 (SMSX) PCR Number :: PCRSDI-12384 Start Date and Time (GMT):: 29th October 2026 05:00 Hrs. End Date and Time (GMT):: 29th October 2026 10:00 Hrs. Impact Mobile Terminating (MT) Traffic : No Impact Mobile Originated (MO) Traffic : No Impact DR Notification : No Impact Report Manager Access : Impacted. Report Manager Statistics : Impacted. Description: Digital Interconnect has scheduled a planned maintenance to carry out activities on the internal application and systems. Report Manager may experience several slowdowns up to 1 minute and delayed up to 1 minute data in reports. 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
46
Days with an incident
32
Median duration
2 h 55 min
This incident
Not comparable
Other Sinch incidents
All incidentsSinch·Delivery Issue Belgium - VOOmobile & MobiStar
This incident has been resolved. Incident Start Time: 2026-10-28 15:06 UTC Incident End Time: 2026-10-28 20:25 UTC
Sinch·Delivery Issue United States - AT&T
This incident has been resolved. Incident Start Time: 2026-10-27 03:14 UTC Incident End Time: 2026-10-27 04:11 UTC
Sinch·Service Degradation - Customer Dashboard and Account Balance
At 2026-10-26 12:58, UTC a planned change caused unforeseen issues affecting the Sinch customer dashboard and our balance calculations. Our engineering teams immediately investigated the issue. Once identified, the change was successfully rolled back and functionality was restored. During the below time frame customers may have experienced issues reaching the Sinch customer dashboard, or experienced problems sending traffic over a subset of accounts due to a block caused by the balance calculation discrepancy. Incident Start Time: 2026-10-26 12:58 UTC Incident End Time: 2026-10-26 15:11 UTC For any inquiries, please contact support@sinch.com
Sinch·Service Degredation - Lookup API
This incident has been resolved. Incident Start Time: 2026-10-26 00:30 UTC Incident End Time: 2026-10-26 01:59 UTC
Sinch·Delivery Issue Sweden - Telia
This incident has been resolved. Incident Start Time: 2026-10-25 09:10 UTC Incident End Time: 2026-10-25 21:28 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.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 "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.cc/feed.xml?providers=sinch/feed subscribe https://outages.cc/feed.xml?providers=sinchFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane