Sinch Elastic SIP Trunking - Incident - duplicate call records

What to do

• Check whether you use Sinch Outbound Calling, User Interface 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 1d 5h it lasted.

  Anything that failed between 2026-06-04 17:05 UTC and 2026-06-05 22:08 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. investigatingJun 4, 2026, 5:05 PM UTC

   Sinch is currently investigating an issue on Elastic SIP Trunking in which non-completed calls are displaying in the CDR view twice. Please note this is not affecting calls or call delivery, it is a CDR presentation issue only for voice termination. Internal teams are actively engaged to resolve the issue. Updates will be provided as soon as possible. We appreciate your patience and apologize for any inconvenience.

   provider

2. investigatingJun 5, 2026, 7:04 AM UTC

   We are continuing to investigate this issue.

   provider

3. resolvedJun 5, 2026, 10:08 PM UTC

   The issue with duplicate call records on Elastic SIP Trunking in which non-completed calls may report twice will be resolved in production on Wednesday, June 10, 2026 at 13:00 UTC. Sinch will be updating our event publisher logic in production at that time. If you have any questions or concerns, please contact us at 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.