outages.live
Live
Sinch logoSinchMaintenance ·

Campaigns Application Maintenance

ResolvedOfficial update

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The latest update from Sinch.

State

Resolved

Started

Lasted

33 min

Worst impact

Maintenance

Timeline

5 updates
15:3015:3815:4615:5516:03
MaintenanceUpdate postedTimes in UTC

Scheduled

3 min 10%

In progress

30 min 90%

Updates

Times in UTC

As posted by Sinch

Resolved
In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

Disable duplication of deleted campaigns in UI via API

Resolved
Scheduled

Disable duplication of deleted campaigns in UI via API

Affected components

12
Campaigns (France 🇫🇷)Campaigns API (France 🇫🇷)Campaigns (Europe 🇪🇺)Campaigns API (Europe 🇪🇺)Campaigns (North America 🇺🇸 / 🇨🇦)Campaigns API (North America 🇺🇸 / 🇨🇦)Campaigns - Campaigns (France 🇫🇷)Campaigns - Campaigns API (France 🇫🇷)

Sinch in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

53

Days with an incident

35

Median duration

2 h 56 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

28 h 8 min
median 2 h 56 min
90 days agoToday

Other Sinch incidents

All incidents
Sinch logo

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.

Resolved
Sinch logo

Sinch·Delivery Issue Spain - DigiMobil

Sinch reported a delivery issue in Spain for DigiMobil. The issue affected SMS - EMEA and External Connectivity - SMS - EMEA. Sinch reports that the issue is resolved. It lasted from 01:45 UTC to 02:37 UTC.

Resolved
Sinch logo

Sinch·Delivery Issue Colombia - Claro

Sinch reported a delivery issue in Colombia on the Claro network. The issue affected SMS - LATAM and External Connectivity - SMS - LATAM. Sinch reports that the issue is resolved.

Resolved
Sinch logo

Sinch·Delivery Issue Sweden - Telavox

Sinch reported a delivery issue in Sweden for Telavox. The issue affected SMS - EMEA and External Connectivity - SMS - EMEA. Sinch resolved the incident. It lasted 48 minutes.

Resolved
Sinch logo

Sinch·Delivery Issue Canada - ICE Wireless

Sinch reported a major SMS delivery outage in Canada. The outage affected ShortCode and Toll Free SMS, including external connectivity for both. Sinch resolved the incident. The outage lasted 5 hours and 39 minutes.

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=sinch
Slack
/feed subscribe https://outages.live/feed.xml?providers=sinch

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane