- Level
- confirmed
- Worst impact
- Partial outage
- Components
- SMS
- Regions
- us
What to do
Check whether you use Sinch SMS in us. 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 55m it lasted.
Anything that failed between 2026-04-22 14:43 UTC and 2026-04-22 15:39 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 experiencing issues with Conversation API SMS channel in the US region. Incident Start Time: 2026-04-22 13:20 UTC Impact: SMS requests routed via the conversation API in the US region might be rejected or throttled.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved Incident Start Time: 2026-04-22 13:20 UTC Incident End Time: 2026-04-22 15:00 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-74d85592bf
Is Sinch still down?
No, this incident was resolved 2026-04-22 15:39 UTC. For Sinch's live state, see https://down.guide/sinch.
How long did it last?
55m, from 2026-04-22 14:43 UTC to 2026-04-22 15:39 UTC, by the times Sinch posted.
What was affected?
Sinch named SMS in us.
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.