Live

Emergency Maintenance — Sinch EU4 Network Hub

MaintenanceOfficial update

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The latest update from Sinch.

State

In progress

Started

Ongoing for

1 h 29 min

Worst impact

Maintenance

Timeline

2 updates
14:2514:4715:0915:3115:54
MaintenanceUpdate postedTimes in UTC

Scheduled

2 min 3%

In progress

1 h 27 min 97%

Updates

Times in UTC

As posted by Sinch

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

We are reaching out to inform you that to improve the performance and reliability of our services, we will be performing an emergency maintenance at our EU4 Network Hub on the schedule below. Type: Emergency Network Maintenance Start Time: 2026-11-20 14:25 UTC End Time: 2026-11-20 19:00 UTC Impact: You may see brief connectivity issues during the maintenance period. We appreciate your patience and apologize for any inconvenience experienced during this maintenance period. If for any reason the maintenance is extended or cancelled, we will advise you accordingly. Please contact support@sinch.com should you require further information or assistance.

Affected components

6
SMPP - EUSMS - EMEAHTTP - EUExternal Connectivity - SMS - EMEAMessaging APIs - SMPP - EUMessaging APIs - HTTP - EU

Sinch in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

68

Days with an incident

49

Median duration

2 h 54 min

This incident

Not comparable

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

9 days
median 2 h 54 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