Live

Sinch Scheduled Maintenance - Core Voice Calling Services - SBCs & Carrier Gateways (Americas region)

MaintenanceOfficial update

Sinch Core Voice Calling Services (Americas region) will be undergoing maintenance to include support for: - routing and media handling updates on the call routing platform, including media redirect headers. - AMR-WB codec for re-INVITEs to prepare for full support of AMR-WB. - improvements for media quality reporting and visibility. Sinch is taking precautions to prevent service impacts, but note that the scheduled work may result in a brief interruption with your service. This is being sent as a courtesy notice if you experience issues that extend beyond the maintenance window. We appreciate your patience and apologize for any inconvenience during this maintenance period. If the maintenance is extended or cancelled, we will advise accordingly. Please contact support@sinch.com for further information.

The latest update from Sinch.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Sinch

Scheduled

Sinch Core Voice Calling Services (Americas region) will be undergoing maintenance to include support for: - routing and media handling updates on the call routing platform, including media redirect headers. - AMR-WB codec for re-INVITEs to prepare for full support of AMR-WB. - improvements for media quality reporting and visibility. Sinch is taking precautions to prevent service impacts, but note that the scheduled work may result in a brief interruption with your service. This is being sent as a courtesy notice if you experience issues that extend beyond the maintenance window. We appreciate your patience and apologize for any inconvenience during this maintenance period. If the maintenance is extended or cancelled, we will advise accordingly. Please contact support@sinch.com for further information.

Affected components

4
Phone Calling (PSTN)SIP TrunkVoice - Phone Calling (PSTN)Voice - SIP Trunk

Sinch in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

54

Days with an incident

36

Median duration

2 h 56 min

This incident

Not comparable

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

28 h 8 min
median 2 h 56 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