Skip to main content
Sinch

Service Degradation - Elastic SIP Trunking - US East

Degraded Lasted 0m · started · Sinch's page

Level
confirmed
Worst impact
Degraded
Regions
us

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-09-09 16:18 UTC and 2026-09-09 14:30 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

  1. resolved

    During the below time frame we experienced an issue with our Elastic SIP Trunking services in the US East region. Incident Start Time: 2026-09-09 14:34 UTC Incident End Time: 2026-09-09 14:42 UTC Impact: Customers may have experienced intermittent issues with non-completed calls on Elastic SIP Trunking We sincerely apologize for any inconvenience this may have caused.

    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-8e6b2b97b4

Is Sinch still down?

No, this incident was resolved 2026-09-09 14:30 UTC. For Sinch's live state, see https://down.guide/sinch.

How long did it last?

0m, from 2026-09-09 16:18 UTC to 2026-09-09 14:30 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.