Sinch incident

Sinch Elastic SIP Trunking - Incident - duplicate call records

Notice Resolved View vendor source →

Sinch experienced a notice incident on June 4, 2026 affecting Outbound Calling and User Interface, lasting 1d 5h. The incident has been resolved; the full update timeline is below.

Started
Jun 04, 2026, 05:05 PM UTC
Resolved
Jun 05, 2026, 10:08 PM UTC
Duration
1d 5h
Detected by Pingoru
Jun 04, 2026, 05:05 PM UTC

Affected components

Outbound CallingUser Interface

Update timeline

  1. investigating Jun 04, 2026, 05: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.

  2. investigating Jun 05, 2026, 07:04 AM UTC

    We are continuing to investigate this issue.

  3. resolved Jun 05, 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 [email protected]