Delivery Issue - SMS Verification - China
Sinch reports delivery problems for SMS Verification traffic to China. The affected components are SMS Verification and Verification - SMS Verification. Sinch is investigating the issue.
State
Investigating
Started
Ongoing for
27 min
Worst impact
Degraded
Timeline
1 updateInvestigating
27 min 100%
Updates
Times in UTCAs posted by Sinch
We are currently observing delivery issues towards China for SMS Verification traffic. Incident Start Time: 2026-11-06 02:57 UTC Impact: Delayed MTs/Failed MTs/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
2Sinch in the last 90 days
Full historyIncidents in 90 days
55
Days with an incident
36
Median duration
2 h 59 min
This incident
85% shorter than the median
Other Sinch incidents
All incidents
Sinch·Delivery Issue Czech Republic - T-Mobile
Sinch reported a delivery issue in the Czech Republic on the T-Mobile network. The issue affected SMS - EMEA and External Connectivity - SMS - EMEA. Sinch reports that the issue is resolved and that it lasted from 00:30 UTC to 04:35 UTC.
Sinch·Delivery Issue - France
Sinch reported a delivery issue in France that affected SMS - EMEA and External Connectivity - SMS - EMEA. The issue is resolved. Sinch reports that it started on 2026-11-04 at 15:08 UTC and ended on 2026-11-05 at 12:46 UTC.
Sinch·Delivery Issue Spain - DigiMobil
Sinch reported a delivery issue in Spain for DigiMobil. The issue affected SMS - EMEA and External Connectivity - SMS - EMEA. Sinch reports that the issue is resolved. It lasted from 01:45 UTC to 02:37 UTC.
Sinch·Delivery Issue Colombia - Claro
Sinch reported a delivery issue in Colombia on the Claro network. The issue affected SMS - LATAM and External Connectivity - SMS - LATAM. Sinch reports that the issue is resolved.
Sinch·Delivery Issue Sweden - Telavox
Sinch reported a delivery issue in Sweden for Telavox. The issue affected SMS - EMEA and External Connectivity - SMS - EMEA. Sinch resolved the incident. It lasted 48 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