Sinch Elastic SIP Trunking - Incident - Inbound call completion issues

What to do

• Check whether you use Sinch API, Inbound Calling, Outbound Calling, International Calling and 1 more. 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 1h 16m it lasted.

  Anything that failed between 2026-07-16 21:14 UTC and 2026-07-16 22:29 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

1. identifiedJul 16, 2026, 9:14 PM UTC

   Sinch has identified the root cause of inbound call completion issues on the Elastic SIP Trunking Platform. We are actively working to restore services. Updates will be provided as soon as possible. We appreciate your patience and apologize for any inconvenience.

   provider

2. monitoringJul 16, 2026, 9:26 PM UTC

   A fix has been implemented and we are closely monitoring. Additional information will be provided as soon as it is available.

   provider

3. resolvedJul 16, 2026, 10:29 PM UTC

   All inbound services for Elastic SIP Trunking have restored as of 21:12 UTC. If you have any additional questions, please submit a ticket to support@sinch.com.

   provider

Corrections

None so far.

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