Live

Sinch Internal Maintenance – Chatlayer Platform (APAC, India Region)

MaintenanceOfficial update

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 APAC, India region at the time specified below. Maintenance Start Time: 2027-01-13 15:00 UTC Maintenance End Time: 2027-01-13 16: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 UTC

As posted by Sinch

Scheduled

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 APAC, India region at the time specified below. Maintenance Start Time: 2027-01-13 15:00 UTC Maintenance End Time: 2027-01-13 16: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

4
Chatlayer Bot Engine - IndiaChatlayer App Integrations - IndiaChatlayer - Chatlayer Bot Engine - IndiaChatlayer - Chatlayer App Integrations - India

Sinch in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

65

Days with an incident

49

Median duration

2 h 55 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

8 days
median 2 h 55 min
90 days agoToday

Other Sinch incidents

All incidents

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=sinch
Slack
/feed subscribe https://outages.live/feed.xml?providers=sinch

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane