- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 12of 100
What to do
Check whether you use Sinch 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 0m it lasted.
Anything that failed between 2026-10-02 10:20 UTC and 2026-10-02 06:00 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 1
- resolved
We want to inform you that we experienced a performance degradation impacting our Calling service. Incident Start Time: 2026-10-02 05:51 UTC Incident End Time: 2026-10-02 09:05 UTC Impact: Customers may have experienced failed attempts when making PSTN outbound calls. We sincerely apologize for any inconvenience this may have caused and appreciate your understanding while we worked to resolve the issue. For further information or assistance, please contact us at support@sinch.com.
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-6fa4a85d4e
Is Sinch still down?
No, this incident was resolved 2026-10-02 06:00 UTC. For Sinch's live state, see https://down.guide/sinch.
How long did it last?
0m, from 2026-10-02 10:20 UTC to 2026-10-02 06:00 UTC, by the times Sinch posted.
What was affected?
Sinch named 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.