outages.live
Live
Sinch logoSinchIncident · 2026-09-27 22:49 UTC

Delivery Issue Belgium - Proximus

ResolvedOfficial update

This incident has been resolved. Incident Start Time: 2026-09-27 22:01 UTC Incident End Time: 2026-09-28 02:00 UTC

The latest update from Sinch.

State

Resolved

Started

35 d ago

2026-09-27 22:49 UTC

Lasted

3 h 19 min

until 2026-09-28 02:08 UTC

Worst impact

Degraded

Timeline

4 updates
22:4923:3900:2901:1802:08
DegradedUpdate postedTimes in UTC

Investigating

1 h 2 min 31%

Identified

1 h 44 min 52%

Monitoring

34 min 17%

Updates

Times in UTC

As posted by Sinch

Resolved2026-09-28 02:08 UTC

This incident has been resolved. Incident Start Time: 2026-09-27 22:01 UTC Incident End Time: 2026-09-28 02:00 UTC

Monitoring2026-09-28 01:34 UTC

A fix has been implemented and we are monitoring the results.

Identified2026-09-27 23:51 UTC

The carrier has confirmed a degradation on their end, and they are currently working on resolving the issue. As soon as we have any updates, they will be shared accordingly.

Investigating2026-09-27 22:49 UTC

We are currently observing delivery issues in Belgium - Proximus Incident Start Time: 2026-09-27 22:01 UTC Impact: Delayed MT's/Delayed MO's/Missing delivery receipts/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

2
SMS - EMEAExternal Connectivity - SMS - EMEA

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.cc/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.cc/feed.xml?providers=sinch
Slack
/feed subscribe https://outages.cc/feed.xml?providers=sinch

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane