Bandwidth: UC Product - Duplicate Call Incident
Timeline of updates
- resolved
Bandwidth customers using our UC product may have received duplicate inbound calls via our JFK Data Center for a brief period of time. One call would be the valid call of the two duplicate calls, and the other would have been an invalid call with no party on the other end. Bandwidth teams have identified the cause of the issue and implemented a solution to resolve this incident. At this time the Bandwidth Network and UC Product suite are operating as expected.
From Bandwidth’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.bandwidth.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Bandwidth, started 2021-06-08 17:00 UTC, resolved after 0 min, 1 update(s).
- Title
- UC Product - Duplicate Call Incident
- Vendor
- Bandwidth
- Date
- URL
- https://rewindex.com/company/bandwidth/incidents/tzx2j0qb2s7r
Bandwidth profileRecent Bandwidth incidentsAll outages on June 8, 2021Bandwidth in June 2021MarkdownJSON