- Level
- confirmed
- Worst impact
- Degraded
- Components
- Core, SMS, RCS
- Down Index
- 21of 100
What to do
Check whether you use Sinch Core, SMS, RCS. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 5h 22m it lasted.
Anything that failed between 2026-06-26 11:58 UTC and 2026-06-26 17:20 UTC may need a replay.Subscribe to Sinch's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=sinch works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Sinch 3
- investigating
We are currently facing a degradation on our customer dashboard affecting Conversation API users. Users may experience issues with their apps after resetting channel credentials. Our engineers are currently working on resolving the issue.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- resolved
This incident has been resolved. Incident Start Time: 2026-06-24 21:39 UTC Incident End Time: 2026-06-26 15:18 UTC
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-1b646e6648
Is Sinch still down?
No, this incident was resolved 2026-06-26 17:20 UTC. For Sinch's live state, see https://down.guide/sinch.
How long did it last?
5h 22m, from 2026-06-26 11:58 UTC to 2026-06-26 17:20 UTC, by the times Sinch posted.
What was affected?
Sinch named Core, SMS, RCS.
What caused it?
Sinch hasn't published a root cause. If it does, it shows here.
Where does this come from?
Sinch's official status page, https://status.sinch.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.