Campaigns Application Maintenance
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from Sinch.
State
Resolved
Started
Lasted
30 min
Worst impact
Maintenance
Timeline
3 updatesScheduled
1 min 1%
In progress
30 min 99%
Updates
Times in UTCAs posted by Sinch
Scheduled maintenance is currently in progress. We will provide updates as necessary.
We are deploying small display improvements to the message previewer for RCS and WhatsApp messages.
Affected components
12Sinch in the last 90 days
Full historyIncidents in 90 days
57
Days with an incident
40
Median duration
3 h 2 min
This incident
Not comparable
Other Sinch incidents
All incidents
Sinch·Service Degradation - Customer Dashboard
Sinch reports degradation of Login and Sign up on Dashboard.sinch.com. The incident is resolved and lasted 72 minutes.
Sinch·Delivery Issue France - Bouygues Telecom
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.
Sinch·Delivery Issue - SMS Verification - China
Sinch SMS Verification delivery is degraded for China. Sinch reports that the incident is resolved. The incident lasted from 2026-11-06 02:57 UTC to 2026-11-10 02:00 UTC.
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.
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