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.
State
Resolved
Started
Lasted
27 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
27 min 100%
Updates
Times in UTCAs posted by Sinch
This incident has been resolved. Incident Start Time: 2026-11-13 01:40 UTC Incident End Time: 2026-11-13 02:10 UTC
We are currently observing delivery issues in Chile - Claro Incident Start Time: 2026-11-13 01:40 UTC Impact: Failed MT's/Delayed MT's/Delayed MO's/Failed 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
2Sinch in the last 90 days
Full historyIncidents in 90 days
63
Days with an incident
42
Median duration
2 h 56 min
This incident
84% shorter than the median
Other Sinch incidents
All incidents
Sinch·Customer Support - Ticketing System
Sinch reports a major outage that stops emails from parsing into the Customer Support ticketing system. This affects Customer Support and Dashboard.sinch.com - Customer Support. Sinch identified the issue and states that it is tied to a larger ongoing issue with Microsoft services. Sinch continues to work on a fix. Customers can raise tickets at support.sinch.com.
Sinch·Delivery Issue SMS Verfication China - China Mobile
Sinch reports a delivery issue for SMS Verification in China on the China Mobile network. The affected components are SMS Verification and Verification - SMS Verification. Sinch is investigating the issue.
Sinch·Delivery Issue - United States - AT&T
Sinch reported a delivery issue for SMS Verification and SMS - US - 10DLC, and for External Connectivity - SMS - US - 10DLC, in the United States on the AT&T network. The impact was failed, delayed, or missing MT messages and delivery receipts. Sinch resolved the incident, which lasted about 3 hours and 41 minutes.
Sinch·Minor Service Outage
Sinch reported a minor service outage on several SMS and MMS components. The affected components include MM4 and MM7 (MMS 365), SMS 365 Operator RoW, International SMS 365, and US SMS and MMS services for Toll Free and 10DLC. Sinch states that the outage is resolved. It lasted 45 minutes.
Sinch·Partial System Outage
Sinch reports a partial outage that affects SMS and MMS Toll Free and 10DLC services in the US, SMS Toll Free in Canada, and the Campaign Registry status for the US. Sinch resolved the outage after 15 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