Vonage Outage History

Started Mar 23, 2026, 09:46 PM UTC· resolved Mar 23, 2026, 10:33 PM UTC

1. identified Mar 23, 2026, 09:46 PM UTC

   We are aware of issues that may be affecting some users' access to call recordings in the Interaction Content section. Our engineers are working to resolve the issue as soon as possible. We'll provide further updates within 1 hour. Thank you for your patience and understanding. If you have any questions, please contact https://www.vonage.com/support/

2. resolved Mar 23, 2026, 10:33 PM UTC

   Access to call recordings has been fully restored following today's service interruption. Full resolution has been confirmed effective 2026-03-26 21:40 UTC. You will receive a formal RFO within 5 business days. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact https://www.vonage.com/support/

Read the full incident report →

Started Mar 23, 2026, 04:48 PM UTC· resolved Mar 23, 2026, 06:43 PM UTC

1. identified Mar 23, 2026, 04:48 PM UTC

   Due to sudden maintenance work, the post-call Conversation Analyzer - Sentiment analysis is currently not calculated in the APAC region. We expect the service to be restored on 24th March at 5 PM UTC. Thank you for your patience and understanding. If you have any questions, please contact https://www.vonage.com/support/

2. identified Mar 23, 2026, 06:43 PM UTC

   Conversation Analyzer - Sentiment Analysis service has been fully restored following today's service maintenance. Sentiment calculations for affected interactions will appear within the next 72 hours. You will receive a formal RFO within 5 business days. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact https://www.vonage.com/support/

3. resolved Mar 23, 2026, 06:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 23, 2026, 11:15 AM UTC· resolved Mar 23, 2026, 12:40 PM UTC

1. investigating Mar 23, 2026, 11:15 AM UTC

   We are aware of issues that may be impacting some Vonage customers' calls due to a third party outage that is affecting multiple service providers. We’ll provide further updates within 2h30 min. Thank you for your patience and understanding. If you have any questions, please contact https://www.vonage.com/support/

2. monitoring Mar 23, 2026, 11:45 AM UTC

   Thank you for your patience following our third party's reported outage earlier today which may have impacted your call services. Our third party has identified the issue and applied initial mitigations, and continues to report early signs of recovery across affected services. We remain engaged with them as recovery continues. We'll provide further updates within 60 minutes and once full service is restored. If you have any questions, please contact https://www.vonage.com/support/

3. resolved Mar 23, 2026, 12:40 PM UTC

   Vonage services have been fully restored following today’s service outage reported by our third party, which began at 2026-03-23 10:18:00 UTC. Full resolution of the incident has been confirmed effective 2026-03-23 10:56:00 UTC. You will receive a formal RFO. Thank you for your patience and understanding as we worked with third party to restore services as quickly as possible. If you have any questions, please contact https://www.vonage.com/support/

Read the full incident report →

Started Mar 12, 2026, 03:06 PM UTC· resolved Mar 12, 2026, 07:17 PM UTC

1. investigating Mar 12, 2026, 03:06 PM UTC

   We are currently aware of an ongoing issue affecting the APIs for the NAM region, affecting multiple Vonage services. Our Incident Management team is investigating the issue with priority

2. investigating Mar 12, 2026, 04:06 PM UTC

   We continue to work to resolve the issue that may be impacting your Vonage services. We'll continue to provide further updates here within 1h. Thank you for your patience and understanding. If you have any questions, please contact https://www.vonage.com/support/.

3. monitoring Mar 12, 2026, 05:07 PM UTC

   Vonage services continue to show signs of recovery following today's interruption in API signalling. We'll continue to provide further updates here within 1h and once full service is restored. Thank you for your patience and understanding as we work to restore services as quickly as possible. If you have any questions, please contact https://www.vonage.com/support/.

4. investigating Mar 12, 2026, 06:12 PM UTC

   We continue to work to resolve the issue that may be impacting your performance dashboards. We'll continue to provide further updates here within 1 hour. Thank you for your patience and understanding.

5. resolved Mar 12, 2026, 07:17 PM UTC

   Vonage services have been restored following today’s issue that may be have impacted your performance dashboards. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact https://www.vonage.com/support/.

Read the full incident report →

Started Feb 26, 2026, 10:49 PM UTC· resolved Feb 27, 2026, 05:30 PM UTC

1. investigating Feb 26, 2026, 10:49 PM UTC

   We are currently aware of an ongoing issue causing some inbound calls to drop in the NAM region. Our Incident Management team is investigating the issue with priority.

2. resolved Feb 27, 2026, 05:30 PM 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. If you are still experiencing issues, please contact Support.

Read the full incident report →

Started Feb 04, 2026, 05:56 PM UTC· resolved Feb 13, 2026, 01:57 PM UTC

1. investigating Feb 04, 2026, 05:56 PM UTC

   We are currently aware of an ongoing issue affecting outbound calls going back to the IVR. Our Incident Management team is investigating the issue with priority.

2. investigating Feb 04, 2026, 09:17 PM UTC

   The incident management team continues to investigate the issue as a top priority.

3. monitoring Feb 05, 2026, 06:12 PM UTC

   Service is now recovered and we are monitoring. If you are still experiencing issues please contact Support.

4. resolved Feb 13, 2026, 01:57 PM 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 on the Community Hub page.

Read the full incident report →

Started Feb 02, 2026, 09:04 PM UTC· resolved Feb 05, 2026, 01:46 PM UTC

1. investigating Feb 02, 2026, 09:04 PM UTC

   We are currently aware of an ongoing issue affecting outbound calling in the NAM region. Our Incident Management team is investigating the issue with priority.

2. monitoring Feb 03, 2026, 05:44 AM UTC

   Service is now recovered, and we are monitoring. If you are still experiencing issues, please contact Support.

3. resolved Feb 05, 2026, 01:46 PM 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.

Read the full incident report →

Started Dec 22, 2025, 09:07 AM UTC· resolved Dec 22, 2025, 04:48 PM UTC

1. investigating Dec 22, 2025, 09:07 AM UTC

   We are currently aware of an ongoing issue affecting inbound calls to certain number ranges. Our Incident Management team is investigating the issue with priority.

2. monitoring Dec 22, 2025, 12:52 PM UTC

   Service is now recovered and we are monitoring. If you are still experiencing issues please contact Support.

3. resolved Dec 22, 2025, 04:48 PM 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.

Read the full incident report →

Started Dec 18, 2025, 07:30 PM UTC· resolved Dec 22, 2025, 09:56 AM UTC

1. investigating Dec 18, 2025, 05:48 PM UTC

   We are currently aware of an ongoing issue affecting the PCI Agent Assist. Our Incident Management team is investigating the issue with priority.

2. investigating Dec 18, 2025, 07:30 PM UTC

   We are continuing to investigate the issue and have made a change to mitigate the impacted component. If you are still impacted please contact support.

3. investigating Dec 18, 2025, 09:56 PM UTC

   We are continuing to investigate the issue and have made a change to mitigate the impacted component. If you are still impacted please contact support.

4. monitoring Dec 19, 2025, 09:43 AM UTC

   We have made a change to mitigate the impacted component and we are monitoring. If you are still experiencing issues please contact Support.

5. resolved Dec 22, 2025, 09:56 AM UTC

   This incident has been resolved. If you are still impacted please contact support.

Read the full incident report →

Started Dec 17, 2025, 03:58 PM UTC· resolved Dec 17, 2025, 04:03 PM UTC

1. investigating Dec 17, 2025, 03:58 PM UTC

   We are currently aware of an ongoing issue affecting the Schedules. Our Incident Management team is investigating the issue with priority.

2. identified Dec 17, 2025, 04:01 PM UTC

   We have identified the problem. We are now progressing to recover service.

3. resolved Dec 17, 2025, 04:03 PM UTC

   The incident has been resolved.

Read the full incident report →

Started Dec 05, 2025, 01:03 PM UTC· resolved Dec 08, 2025, 06:57 PM UTC

1. investigating Dec 05, 2025, 01:03 PM UTC

   We are currently aware of an ongoing issue involving our telephony partner GTT in the EMEA region. Our Incident Management team is investigating the issue with priority.

2. investigating Dec 08, 2025, 02:24 PM UTC

   The incident management team continues to work with GTT to identify the problem.

3. resolved Dec 08, 2025, 06:57 PM 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.

Read the full incident report →

Started Dec 03, 2025, 01:29 PM UTC· resolved Dec 04, 2025, 11:17 AM UTC

1. investigating Dec 03, 2025, 01:29 PM UTC

   We are currently aware of an ongoing network issue involving our partner GTT in APAC region. Our Incident Management team is investigating the issue with priority

2. monitoring Dec 03, 2025, 04:22 PM UTC

   We have identified the problem with one of our carrier partners. Mitigations have been applied to restore service and we are working with the carrier to fully remediate the root cause.

3. resolved Dec 04, 2025, 11:17 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.

Read the full incident report →

Started Nov 27, 2025, 12:17 PM UTC· resolved Nov 27, 2025, 04:23 PM UTC

1. investigating Nov 27, 2025, 12:17 PM UTC

   We are aware that some users are having difficulties configuring Virtual Assistant in the AI Studio. Our Incident Management Teams is investigating this issue with priority.

2. monitoring Nov 27, 2025, 12:55 PM UTC

   Service is now recovered and we are monitoring.

3. resolved Nov 27, 2025, 04:23 PM 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.

Read the full incident report →

Started Nov 12, 2025, 09:33 PM UTC· resolved Nov 13, 2025, 02:01 PM UTC

1. investigating Nov 12, 2025, 09:33 PM UTC

   We are currently aware of an ongoing issue affecting agents' wrap-up duration in the NAM region for some customers. Our Incident Management team is investigating the issue with priority. If you are experiencing issues, please contact Support.

2. monitoring Nov 12, 2025, 10:14 PM UTC

   Service is now recovered, and we are monitoring. If you are still experiencing issues, please contact Support.

3. resolved Nov 13, 2025, 02:01 PM 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.

Read the full incident report →

Started Oct 29, 2025, 12:43 AM UTC· resolved Oct 29, 2025, 08:05 AM UTC

1. investigating Oct 29, 2025, 12:43 AM UTC

   We are currently investigating this issue.

2. investigating Oct 29, 2025, 12:54 AM UTC

   We are aware of an issue with our onward cloud provider which is causing performance issues with some areas of our platform.

3. investigating Oct 29, 2025, 01:00 AM UTC

   We are continuing to investigate this issue.

4. investigating Oct 29, 2025, 01:02 AM UTC

   We are continuing to investigate this issue.

5. monitoring Oct 29, 2025, 01:57 AM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Oct 29, 2025, 08:05 AM UTC

   This incident has been resolved, if you are still experiencing issues please contact support.

Read the full incident report →

Started Oct 24, 2025, 05:01 PM UTC· resolved Oct 29, 2025, 08:09 AM UTC

1. investigating Oct 24, 2025, 05:01 PM UTC

   We are currently aware of an ongoing issue affecting calls using WebRTC in the NAM region. Our Incident Management team is investigating the issue with priority.

2. investigating Oct 24, 2025, 05:39 PM UTC

   Service is now recovered and we are monitoring. If you are still experiencing issues please contact Support.

3. investigating Oct 24, 2025, 07:20 PM UTC

   We are currently aware of an ongoing issue affecting calls using WebRTC in the NAM region. Our Incident Management team is investigating the issue with priority.

4. monitoring Oct 24, 2025, 08:28 PM UTC

   Service is now recovered and we are monitoring. If you are still experiencing issues please contact Support.

5. resolved Oct 29, 2025, 08:09 AM UTC

   This incident has been resolved, if you are still experiencing issues please contact support.

Read the full incident report →

Started Oct 24, 2025, 12:31 PM UTC· resolved Oct 24, 2025, 06:55 PM UTC

1. investigating Oct 24, 2025, 12:31 PM UTC

   We are currently aware of an ongoing issue affecting interaction plan configuration in Interaction Architect for selected VCC accounts on our EMEA and NAM nodes. Our Incident Management team is investigating the issue with priority

2. monitoring Oct 24, 2025, 12:46 PM UTC

   Service is now recovered, and we are monitoring. If you are still experiencing issues, please contact Support.

3. resolved Oct 24, 2025, 06:55 PM UTC

   This incident has been resolved, if you are still experiencing issues please contact support.

Read the full incident report →

Started Oct 20, 2025, 02:40 PM UTC· resolved Oct 21, 2025, 01:05 AM UTC

1. investigating Oct 20, 2025, 02:40 PM UTC

   We are aware of issues that may be impacting your VCC service following a service disruption reported by Amazon Web Services (AWS) today. AWS have applied initial mitigations and our teams remain engaged with them. We’ll provide further updates as more information becomes available or once full service is restored. Thank you for your patience and understanding.

2. investigating Oct 20, 2025, 05:20 PM UTC

   We continue to monitor the impact to some Vonage services, following a service disruption reported by Amazon Web Services (AWS) earlier today. AWS has applied initial mitigations and are reporting early signs of recovery across affected services. Our teams remain engaged with AWS as recovery continues. We’ll provide further updates as more information becomes available or once full service is restored. Thank you for your patience and understanding.

3. investigating Oct 20, 2025, 08:18 PM UTC

   We continue to monitor the impact to some Vonage services, following a service disruption reported by Amazon Web Services (AWS) earlier today. AWS has applied initial mitigations and are reporting early signs of recovery across affected services. Our teams remain engaged with AWS as recovery continues. We’ll provide further updates as more information becomes available or once full service is restored. Thank you for your patience and understanding.

4. monitoring Oct 20, 2025, 10:48 PM UTC

   We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VBC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once AWS confirms full service is restored. Thank you for your continued patience and understanding.

5. resolved Oct 21, 2025, 01:05 AM UTC

   Vonage services have been restored following today’s service disruption reported by AWS. Full resolution of the incident has been confirmed by AWS effective 6:53 pm ET. You may see delays with historical reporting as the platform processes the data backlog. We thank you for your patience and understanding as we worked with AWS to restore services as quickly as possible.

Read the full incident report →

Started Oct 20, 2025, 09:53 AM UTC· resolved Oct 21, 2025, 01:04 AM UTC

1. monitoring Oct 20, 2025, 09:53 AM UTC

   We’re continuing to monitor the ongoing incident that has been impacting some Vonage services. AWS have applied initial mitigations and are reporting early signs of recovery across affected services. If you see a yellow warning message on your ContactPad (e.g. “Backup WebRTC is not connected”), please note this is for information only — calls should still be handled as normal. Our teams remain closely engaged with AWS as recovery continues. We’ll provide further updates as more information becomes available or once full service is restored. Thank you for your patience and understanding.

2. monitoring Oct 20, 2025, 11:31 AM UTC

   Following a service disruption reported by Amazon Web Services (AWS), we are monitoring the impact to some Vonage services, which may have affected your VBC service. AWS has applied initial mitigations and are reporting early signs of recovery. We are engaged with AWS as recovery continues. We will provide further updates as more information becomes available and once full service is restored. Thank you for your patience and understanding.

3. monitoring Oct 20, 2025, 12:06 PM UTC

   We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VCC services. AWS has identified a potential root cause and applied initial mitigations, and are reporting early signs of recovery across affected services. We remain engaged with AWS as recovery continues. We’ll provide further updates as more information becomes available or once full service is restored. Thank you for your continued patience and understanding.

4. monitoring Oct 20, 2025, 12:59 PM UTC

   We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VCC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once full service is restored. Thank you for your continued patience and understanding.

5. monitoring Oct 20, 2025, 02:05 PM UTC

   We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VCC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once full service is restored. Thank you for your continued patience and understanding.

6. investigating Oct 20, 2025, 03:32 PM UTC

   We are aware of issues that may be impacting your VCC service following a service disruption reported by Amazon Web Services (AWS) today. AWS have applied initial mitigations and our teams remain engaged with them. We’ll provide further updates as more information becomes available or once full service is restored. Thank you for your patience and understanding.

7. investigating Oct 20, 2025, 05:20 PM UTC

   We continue to monitor the impact to some Vonage services, following a service disruption reported by Amazon Web Services (AWS) earlier today. AWS has applied initial mitigations and are reporting early signs of recovery across affected services. Our teams remain engaged with AWS as recovery continues. We’ll provide further updates as more information becomes available or once full service is restored. Thank you for your patience and understanding.

8. investigating Oct 20, 2025, 08:18 PM UTC

   We continue to monitor the impact to some Vonage services, following a service disruption reported by Amazon Web Services (AWS) earlier today. AWS has applied initial mitigations and are reporting early signs of recovery across affected services. Our teams remain engaged with AWS as recovery continues. We’ll provide further updates as more information becomes available or once full service is restored. Thank you for your patience and understanding.

9. monitoring Oct 20, 2025, 10:49 PM UTC

   We continue to see recovery following the Amazon Web Services (AWS) reported service disruption earlier today which may have impacted your VBC services. AWS has identified a potential root cause and applied mitigations, and is reporting signs of recovery across affected services. We will provide further updates as more information becomes available and once AWS confirms full service is restored. Thank you for your continued patience and understanding.

10. resolved Oct 21, 2025, 01:04 AM UTC

    Vonage services have been restored following today’s service disruption reported by AWS. Full resolution of the incident has been confirmed by AWS effective 6:53 pm ET. You may see delays with historical reporting as the platform processes the data backlog. We thank you for your patience and understanding as we worked with AWS to restore services as quickly as possible.

Read the full incident report →

Started Oct 16, 2025, 10:05 AM UTC· resolved Oct 16, 2025, 01:58 PM UTC

1. investigating Oct 16, 2025, 10:05 AM UTC

   We are currently aware of an ongoing issue affecting outbound calling Hungary from Hungarian numbers. Our Incident Management team is investigating the issue with priority.

2. monitoring Oct 16, 2025, 12:05 PM UTC

   Service is now recovered and we are monitoring. If you are still experiencing issues please contact Support.

3. resolved Oct 16, 2025, 01:58 PM 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.

Read the full incident report →

Started Oct 15, 2025, 04:50 PM UTC· resolved Oct 15, 2025, 10:51 PM UTC

1. investigating Oct 15, 2025, 04:50 PM UTC

   We are currently aware of an issue affecting the connectivity for all regions. Our Incident Management team is investigating the issue with priority.

2. investigating Oct 15, 2025, 04:52 PM UTC

   We are continuing to investigate this issue.

3. investigating Oct 15, 2025, 06:06 PM UTC

   The incident management team continues to investigate the issue as a top priority.

4. investigating Oct 15, 2025, 06:59 PM UTC

   Our Engineers are working to restore inbound and outbound calling services. We appreciate your continued patience as we work to resolve the issues affecting your service. We will post further updates as soon as they become available

5. investigating Oct 15, 2025, 07:28 PM UTC

   Our Engineers are working to restore inbound and outbound calling services. We appreciate your continued patience as we work to resolve the issues affecting your service. We will post further updates as soon as they become available. If you experience any issues contacting us using the standard contact numbers, please use +18556240126

6. investigating Oct 15, 2025, 08:13 PM UTC

   Thank you for your patience as our engineers continue working to resolve the intermittent issues affecting inbound and outbound calls. Restoring normal service remains our highest priority. We will post further updates as soon as they become available.

7. investigating Oct 15, 2025, 09:03 PM UTC

   Thank you for your patience as our engineers continue working to resolve the intermittent issues affecting inbound and outbound calls. Restoring normal service remains our highest priority. We will post further updates as soon as they become available.

8. resolved Oct 15, 2025, 10:51 PM UTC

   Thank you for your patience as we worked to resolve the issue that may have affected your ability to make or receive calls today. Corrective actions have been implemented and services have been restored for all customers. We understand that consistent, reliable service is critical to your business and we apologize for this service interruption.

Read the full incident report →

Started Oct 15, 2025, 12:14 PM UTC· resolved Oct 15, 2025, 02:12 PM UTC

1. investigating Oct 15, 2025, 12:14 PM UTC

   We have identified a problem with digital interactions in the EMEA and NAM region. We are now progressing to recover service.

2. resolved Oct 15, 2025, 02:12 PM UTC

   This issue has been resolved, and the service is now recovered. 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.

Read the full incident report →

Started Oct 13, 2025, 03:01 PM UTC· resolved Oct 14, 2025, 02:23 PM UTC

1. investigating Oct 13, 2025, 03:01 PM UTC

   We are currently aware of an ongoing issue involving one of the third-party carriers. Our Incident Management team is investigating the issue with priority.

2. investigating Oct 13, 2025, 03:02 PM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 13, 2025, 04:46 PM UTC

   Service is now recovered, and we are monitoring. If you are still experiencing issues, please contact Support.

4. resolved Oct 14, 2025, 02:23 PM UTC

   This non Vonage incident has been resolved.

Read the full incident report →

Started Oct 13, 2025, 09:36 AM UTC· resolved Oct 13, 2025, 10:29 AM UTC

1. investigating Oct 13, 2025, 09:36 AM UTC

   We are currently aware of an ongoing issue affecting the Community Hub portal. Our Incident Management team is investigating the issue with priority.

2. resolved Oct 13, 2025, 10:29 AM UTC

   The incident has been resolved. If you are still experiencing issues please contact Support.

Read the full incident report →