Delivery Issue Belgium - Proximus
Sinch reports degraded SMS delivery in Belgium on Proximus. The affected components are SMS - EMEA and External Connectivity - SMS - EMEA. Sinch is investigating the incident.
State
Investigating
Started
Ongoing for
11 min
Worst impact
Degraded
Timeline
1 updateInvestigating
11 min 100%
Updates
Times in UTCAs posted by Sinch
We are currently observing delivery issues in Belgium - Proximus Incident Start Time: 2026-11-20 08:34 UTC Impact: Failed/Delayed MTs, Failed/Delayed MOs, Missing/Late delivery receipts We will update as soon as we have more information. If you have any questions, please contact support@sinch.com.
Affected components
2Sinch in the last 90 days
Full historyIncidents in 90 days
68
Days with an incident
49
Median duration
2 h 54 min
This incident
94% shorter than the median
Other Sinch incidents
All incidents
SinchΒ·Delivery Issue Sweden - Tele2
Sinch reports SMS delivery issues in Sweden on the Tele2 network. The problem affects SMS - EMEA and External Connectivity - SMS - EMEA. Sinch is investigating. Alphanumeric Sender IDs with characters outside A-Z, a-z and 0-9 may have character replacement or substitution.

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.

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