Vonage API experienced a minor incident on July 16, 2026 affecting Voice API, lasting 1h 40m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 16, 2026, 08:06 AM UTC
We are aware of an issue currently impacting Voice API WebSocket connections in the EU and APAC regions, where authentication headers are not being sent. We are actively working to resolve this as quickly as possible and will provide a further update within 1 hour. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com
- identified Jul 16, 2026, 08:56 AM UTC
We have identified the issue that's impacting WebSocket connections where authentication headers are not being sent. We will continue to provide updates along the way until full service is restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- monitoring Jul 16, 2026, 09:07 AM UTC
Vonage services continue to show signs of recovery following the interruption in WebSocket connections, where authentication headers are not being sent. We'll continue to provide further updates here. Thank you for your patience and understanding as we work to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com
- resolved Jul 16, 2026, 09:46 AM UTC
Vonage services impacting WebSocket connections in the EU and APAC regions where authentication headers were not being sent have been fully restored following the service interruption, which began at [2026-07-01 16:16] UTC. Full resolution has been confirmed effective [2026-07-16 08:53] UTC. Thank you for your patience and understanding as we worked to restore services. If you have any questions, please contact api.support.vonage.com.