Live

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

The latest update from Sinch.

State

Resolved

Started

6 d ago

2026-10-26 13:33 UTC

Lasted

2 h 32 min

until 2026-10-26 16:05 UTC

Worst impact

Partial outage

Timeline

4 updates
13:3314:1114:4915:2716:05
Partial outageUpdate postedTimes in UTC

Investigating

42 min 28%

Identified

1 h 5 min 43%

Monitoring

45 min 29%

Updates

Times in UTC

As posted by Sinch

Resolved2026-10-26 16:05 UTC

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

Monitoring2026-10-26 15:21 UTC

A second fix has been implemented and we are seeing correct account balances and customer accounts have been unblocked. We are continuing to monitoring the results.

Identified2026-10-26 14:15 UTC

A fix has been implemented and we are seeing improvements for the dashboard. We are continuing to investigate the incorrect account balances.

Investigating2026-10-26 13:33 UTC

We are currently investigating a service outage on the customer dashboard, Dashboard.sinch.com and with our balance calculation causing a subset of customer accounts to be blocked. Start Time: 2026-10-26 12:58 UTC Impact: Clients may experience issues reaching the customer dashboard and may see an incorrect account balance. Our engineering team is working to restore full functionality as soon as possible. For any inquiries, please contact support@sinch.com.

Affected components

32
PaymentSMS - APACSMS AdministrationSMS - EMEANumbers AdministrationSMS - LATAMAnalyticsSMS - CA - ShortCode

Sinch in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

46

Days with an incident

32

Median duration

2 h 55 min

This incident

About the median

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

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

Other Sinch incidents

All incidents

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane