Campaigns Application Maintenance
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from Sinch.
State
In progress
Started
Ongoing for
49 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
3 min 7%
In progress
46 min 93%
Updates
Times in UTCAs posted by Sinch
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Reduce display latencies on URL redirections
Affected components
12Sinch in the last 90 days
Full historyIncidents in 90 days
63
Days with an incident
42
Median duration
2 h 56 min
This incident
Not comparable
Other Sinch incidents
All incidents
Sinch·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.
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.
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