Live

Delivery Issue France - Bouygues Telecom

0

Sinch reports delivery issues in France for Bouygues Telecom. The issue affects SMS - EMEA and External Connectivity - SMS - EMEA. Missing or late delivery receipts occurred. Sinch applied a fix and monitored the results. The incident is resolved. It lasted from 2026-11-09 12:07 UTC to 2026-11-10 01:40 UTC.

State

Resolved

Started

Lasted

13 h 59 min

Worst impact

Degraded

Timeline

4 updates
14:0217:3121:0100:3104:00
DegradedUpdate postedTimes in UTC

Investigating

11 h 31 min 82%

Monitoring

2 h 28 min 18%

Updates

Times in UTC

As posted by Sinch

Resolved

This incident has been resolved. Incident Start Time: 2026-11-09 12:07 UTC Incident End Time: 2026-11-10 01:40 UTC

Monitoring

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

Investigating

We are continuing to investigate this issue.

Investigating

We are currently observing delivery issues in France - Bouygues Telecom Incident Start Time: 2026-11-09 12:07 UTC Impact: 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

Sinch in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

57

Days with an incident

40

Median duration

3 h 2 min

This incident

4.6Γ— the median

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

4 days
median 3 h 2 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