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
19 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
1 min 2%
In progress
18 min 98%
Updates
Times in UTCAs posted by Sinch
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Fix preview for users using custom sender
Affected components
12Sinch in the last 90 days
Full historyIncidents in 90 days
59
Days with an incident
40
Median duration
2 h 56 min
This incident
Not comparable
Other Sinch incidents
All incidents
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.
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.
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