Delivery Issue - SMS Verification - China
Sinch reports delivery issues for SMS Verification traffic to China. The affected components are SMS Verification and Verification - SMS Verification. Sinch is investigating the problem.
State
Investigating
Started
Ongoing for
54 min
Worst impact
Degraded
Timeline
1 updateInvestigating
54 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
70% shorter than the median
Other Sinch incidents
All incidents
Sinch·Delivery Issue Czech Republic - T-Mobile
Sinch reported a delivery issue for SMS 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. The incident lasted from 00:30 UTC to 04:35 UTC.
Sinch·Delivery Issue - France
Sinch reported delivery issues for SMS in France. The issue affected SMS - EMEA and External Connectivity - SMS - EMEA. Sinch reported delayed mobile-terminated messages, delayed mobile-originated messages, and late delivery receipts. Sinch resolved the incident.
Sinch·Delivery Issue Spain - DigiMobil
Sinch reports a delivery issue for SMS in Spain on the DigiMobil network. The issue affects SMS - EMEA and External Connectivity - SMS - EMEA. Sinch resolved the incident, which lasted 52 minutes.
Sinch·Delivery Issue Colombia - Claro
Sinch reports SMS delivery issues in Colombia on the Claro network. The affected components are SMS - LATAM and External Connectivity - SMS - LATAM. Sinch reports that the incident is resolved.
Sinch·Delivery Issue Sweden - Telavox
Sinch reported a delivery issue in Sweden for SMS - EMEA and External Connectivity - SMS - EMEA. The incident is resolved. 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.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.
https://outages.cc/feed.xml?providers=sinch/feed subscribe https://outages.cc/feed.xml?providers=sinchFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane