Vonage: Websocket Incident on June 10th(resolved)
Timeline of updates
- resolved
Incident time: Issue start time: June 10, 2024, 13:46:00 UTC Issue end time: June 10, 2024, 13:47:00 UTC Statement: At 13:46 UTC on 10th June, the infrastructure that handles Audio Over WebSockets to customers was accidentally restarted in our US-East datacenter. This caused ongoing WebSocket calls to drop. No further impact was seen. Cause: A bug in the deployment process caused a non-graceful restart of our WebSocket Media Servers in the US-East region. The deployment process should have used a graceful restart mechanism, which first waited for calls to end before restarting the system. Regions: Only Audio Over WebSocket calls in the us-east datacentre were impacted. Mitigations: The deployment process bug has been fixed. Future deployments will wait for calls to end before restarting the system.
From Vonage’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 vonageapi.statuspage.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Vonage, started 2024-06-27 17:34 UTC, resolved after 0 min, 1 update(s).
- Title
- Websocket Incident on June 10th(resolved)
- Vendor
- Vonage
- Date
- URL
- https://rewindex.com/company/vonage/incidents/f3yfysyqyljn
Vonage profileRecent Vonage incidentsAll outages on June 27, 2024Vonage in June 2024MarkdownJSON