Delivery Issue Spain - DigiMobil
Sinch reports a delivery issue for SMS in Spain on the DigiMobil network. The issue affects SMS - EMEA and External Connectivity - SMS - EMEA. Sinch resolved the incident, which lasted 52 minutes.
State
Resolved
Started
Lasted
41 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
41 min 100%
Updates
Times in UTCAs posted by Sinch
This incident has been resolved. Incident Start Time: 2026-11-05 01:45 UTC Incident End Time: 2026-11-05 02:37 UTC
We are currently observing delivery issues in Spain - DigiMobil Incident Start Time: 2026-11-05 01:45 UTC Impact: Delayed MT's/Delayed 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
52
Days with an incident
35
Median duration
2 h 55 min
This incident
77% shorter than the median
Other Sinch incidents
All incidents
Sinch·Delivery Issue Colombia - Claro
Sinch reports SMS delivery issues in Colombia on the Claro network. The affected components are SMS - LATAM and External Connectivity - SMS - LATAM. Sinch reports that the incident is resolved.
Sinch·Delivery Issue Sweden - Telavox
Sinch reported a delivery issue in Sweden for SMS - EMEA and External Connectivity - SMS - EMEA. The incident is resolved. It lasted 48 minutes.
Sinch·Delivery Issue Canada - ICE Wireless
Sinch reported an SMS delivery outage for ICE Wireless in Canada. The outage affected ShortCode, Toll Free, and their external connectivity components. Sinch resolved the incident.
Sinch·Delivery Issue Bolivia - Entel
Sinch reported a delivery issue in Bolivia for Entel. The issue affected SMS - LATAM and External Connectivity - SMS - LATAM. Sinch reports that the incident is resolved. The incident lasted from 02:35 UTC to 07:09 UTC.
Sinch·Delivery Issue United States - Google Voice
Sinch reported a delivery issue with SMS ShortCode and External Connectivity for SMS ShortCode in the United States, specific to Google Voice. Sinch later resolved the incident. The incident lasted 4 hours and 41 minutes, from 2026-11-01 23:57 UTC to 2026-11-02 04:38 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.cc/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.cc/feed.xml?providers=sinch/feed subscribe https://outages.cc/feed.xml?providers=sinchFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane