Sinch Internal Maintenance – Chatlayer Platform (US Region)
We are writing to inform you that, as part of our continuous efforts to improve the performance and reliability of the Chatlayer platform, we will perform scheduled maintenance on the network routing layer of the Americas, US region at the time specified below. Maintenance Start Time: 2026-12-09 08:00 UTC Maintenance End Time: 2026-12-09 09:00 UTC Impact: Bot, voice and integration traffic may be interrupted for up to 2 minutes during the window, while traffic switches to the new routing layer. Outside of this short interruption, no impact is expected. We appreciate your patience and apologize for any inconvenience during this maintenance period. If for any reason the maintenance is extended or rescheduled, we will update this page accordingly. Please contact support@sinch.com if you require further information or assistance.
The latest update from Sinch.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Sinch
We are writing to inform you that, as part of our continuous efforts to improve the performance and reliability of the Chatlayer platform, we will perform scheduled maintenance on the network routing layer of the Americas, US region at the time specified below. Maintenance Start Time: 2026-12-09 08:00 UTC Maintenance End Time: 2026-12-09 09:00 UTC Impact: Bot, voice and integration traffic may be interrupted for up to 2 minutes during the window, while traffic switches to the new routing layer. Outside of this short interruption, no impact is expected. We appreciate your patience and apologize for any inconvenience during this maintenance period. If for any reason the maintenance is extended or rescheduled, we will update this page accordingly. Please contact support@sinch.com if you require further information or assistance.
Affected components
6Sinch in the last 90 days
Full historyIncidents in 90 days
65
Days with an incident
49
Median duration
2 h 55 min
This incident
Not comparable
Other Sinch incidents
All incidents
Sinch·Delivery Issue Canada - Bell Canada
SMS delivery to Bell Canada in Canada does not work correctly for ShortCode and Toll Free, including external connectivity. Sinch reports that the incident is resolved. The outage lasted 52 minutes.

Sinch·Delivery Issue Qatar - Ooredoo Qatar
SMS delivery through Ooredoo Qatar in Qatar had failures and delays. Sinch reports that the incident is resolved. It lasted from 02:35 UTC to 05:23 UTC on 2026-11-18.

Sinch·Delivery Issue Chile - Claro
Sinch reported a delivery issue in Chile on the Claro network. The issue affected SMS - LATAM and External Connectivity - SMS - LATAM. Sinch reports that the incident is resolved. It lasted 30 minutes.

Sinch·Customer Support - Ticketing System
Sinch reports a major outage in its Customer Support ticketing system. The problem affected email parsing into the ticket system and the Customer Support area of Dashboard.sinch.com. Sinch resolved the incident on 14 November 2026, about 35 hours after it started.

Sinch·Delivery Issue SMS Verfication China
Sinch reports a delivery issue with SMS Verification to China. The issue affects all networks in China and causes failed messages, missing delivery receipts, and late delivery receipts. Sinch has identified the issue and continues work with its carriers on a resolution.
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