Emergency Maintenance — Sinch EU4 Network Hub
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 updatesScheduled
2 min 3%
In progress
1 h 27 min 97%
Updates
Times in UTCAs posted by Sinch
Scheduled maintenance is currently in progress. We will provide updates as necessary.
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
6Sinch in the last 90 days
Full historyIncidents in 90 days
68
Days with an incident
49
Median duration
2 h 54 min
This incident
Not comparable
Other Sinch incidents
All incidents
Sinch·Delivery Issue Belgium - Proximus
Sinch reports SMS delivery issues in Belgium on the Proximus network. The issues affect SMS - EMEA and External Connectivity - SMS - EMEA. Sinch reports improvements and is monitoring the situation.

Sinch·Delivery Issue Sweden - Tele2
SMS delivery is degraded in Sweden on Tele2 and affects SMS - EMEA and External Connectivity - SMS - EMEA. Sinch reports that alphanumeric Sender IDs with characters outside A-Z, a-z and 0-9 can have character replacement or substitution. The status is investigating.

Sinch·Delivery Issue Guatemala - Tigo
SMS delivery to Tigo in Guatemala does not work on SMS - LATAM and External Connectivity - SMS - LATAM. Sinch reports the issue as resolved. The incident lasted 68 minutes, from 06:00 UTC to 07:08 UTC.

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