Sinch: Sinch Elastic SIP Trunking - Incident - duplicate call records
Timeline of updates
- resolved
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
From Sinch’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.sinch.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Sinch, started 2026-06-04 17:05 UTC, resolved after 29 h, 1 update(s).
- Title
- Sinch Elastic SIP Trunking - Incident - duplicate call records
- Vendor
- Sinch
- Date
- URL
- https://rewindex.com/company/sinch/incidents/wk6vfq9w44y6
Sinch profileRecent Sinch incidentsAll outages on June 4, 2026Sinch in June 2026MarkdownJSON