Vonage experienced a major incident on August 5, 2025 affecting Inbound Voice Interactions and Inbound Voice Interactions and 1 more component, lasting 16h 11m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 05, 2025, 04:11 PM UTC
We are currently aware of an ongoing issue affecting outbound and inbound calling in the NAM. Our Incident Management team is investigating the issue with priority.
- investigating Aug 05, 2025, 04:35 PM UTC
The incident management team continues to investigate the issue as a top priority.
- investigating Aug 05, 2025, 05:21 PM UTC
We are continuing to investigate this issue. Please note that this impacts EMEA and NAM calls at the moment and is intermittent.
- identified Aug 05, 2025, 05:44 PM UTC
We have identified the problem affecting calls. Our Voice engineering team are working to control traffic flows to restore service.
- identified Aug 05, 2025, 06:44 PM UTC
The voice engineering team have identified the cause of the processing demands. Traffic control is being put in place to restore normal processing levels.
- identified Aug 05, 2025, 08:11 PM UTC
Vonage is working with our Voice edge equipment partner as a priority. The work is ongoing and has all voice engineering focused on this.
- identified Aug 05, 2025, 09:57 PM UTC
Vonage is working with our Voice edge equipment partner as a priority. The work is focused on controlling repeating retry requests through upscaling and throttling.
- identified Aug 05, 2025, 10:38 PM UTC
Vonage has worked to control the repeating retry requests. Our testing is showing positive results, and we are now monitoring.
- monitoring Aug 05, 2025, 11:09 PM UTC
Vonage has confirmed the changes made have restored service. Our testing is showing positive results, and we are now moving to monitoring.
- monitoring Aug 06, 2025, 01:12 AM UTC
Service is now recovered and we are monitoring. If you are still experiencing issues, please contact Support.
- resolved Aug 06, 2025, 08:22 AM UTC
This issue has been resolved. We are now working to generate a full root cause analysis which will be shared in the form of an Incident Report with affected customers.