Customer Support - Ticketing System
This incident has been resolved. Incident Start Time : 2026-09-25 14:46 UTC Incident End Time : 2026-09-25 16:03 UTC
The latest update from Sinch.
State
Resolved
Started
37 d ago
2026-09-25 15:31 UTC
Lasted
55 min
until 2026-09-25 16:26 UTC
Worst impact
Degraded
Timeline
2 updatesInvestigating
55 min 100%
Updates
Times in UTCAs posted by Sinch
This incident has been resolved. Incident Start Time : 2026-09-25 14:46 UTC Incident End Time : 2026-09-25 16:03 UTC
We are currently experiencing an issue with our ticketing system related to the following emails: support@sinch.com Impact: Customers may experience delayed responses from support. Incident Start Time : 2026-09-25 14:46 UTC As an alternative in the meantime, please raise all tickets via our ticketing portal at support.sinch.com.
Affected components
2Sinch in the last 90 days
Full historyIncidents in 90 days
46
Days with an incident
32
Median duration
2 h 55 min
This incident
69% shorter than the median
Other Sinch incidents
All incidents
Sinch·Delivery Issue Belgium - VOOmobile & MobiStar
This incident has been resolved. Incident Start Time: 2026-10-28 15:06 UTC Incident End Time: 2026-10-28 20:25 UTC
Sinch·Delivery Issue United States - AT&T
This incident has been resolved. Incident Start Time: 2026-10-27 03:14 UTC Incident End Time: 2026-10-27 04:11 UTC
Sinch·Service Degradation - Customer Dashboard and Account Balance
At 2026-10-26 12:58, UTC a planned change caused unforeseen issues affecting the Sinch customer dashboard and our balance calculations. Our engineering teams immediately investigated the issue. Once identified, the change was successfully rolled back and functionality was restored. During the below time frame customers may have experienced issues reaching the Sinch customer dashboard, or experienced problems sending traffic over a subset of accounts due to a block caused by the balance calculation discrepancy. Incident Start Time: 2026-10-26 12:58 UTC Incident End Time: 2026-10-26 15:11 UTC For any inquiries, please contact support@sinch.com
Sinch·Service Degredation - Lookup API
This incident has been resolved. Incident Start Time: 2026-10-26 00:30 UTC Incident End Time: 2026-10-26 01:59 UTC
Sinch·Delivery Issue Sweden - Telia
This incident has been resolved. Incident Start Time: 2026-10-25 09:10 UTC Incident End Time: 2026-10-25 21:28 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