Sinch: Service Outage - Sinch Engage Classic

What to do

Check whether you use Sinch Engage Classic (appengage.sinch.com). 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 50m it lasted.
Anything that failed between 2026-04-01 10:55 UTC and 2026-04-01 11:46 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.

investigatingApr 1, 2026, 10:55 AM UTC
We are currently experiencing a complete outage of the Sinch Engage Classic system. The service is not accessible at this time. Our teams are actively investigating the issue and working to restore functionality as quickly as possible. We will provide further updates as more information becomes available.
provider
monitoringApr 1, 2026, 11:14 AM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedApr 1, 2026, 11:46 AM UTC
This incident has been resolved. Incident Start Time: 2026-04-01 09:36 UTC Incident End Time: 2026-04-01 11:06 UTC
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Sinch still down?

No, this incident was resolved 2026-04-01 11:46 UTC. For Sinch's live state, see https://down.guide/sinch.

How long did it last?

50m, from 2026-04-01 10:55 UTC to 2026-04-01 11:46 UTC, by the times Sinch posted.

What was affected?

Sinch named Engage Classic (appengage.sinch.com).

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.