Vonage Outage History

Vonage is up right now

Vonage had 65 outages in the last 2 years totaling 477h 56m of downtime — averaging 2.7 incidents per month.

There were 65 Vonage outages since August 1, 2025 totaling 477h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://vcc.statuspage.io

Minor October 1, 2025

IR27208 - Czechia to Czechia calls not connecting

Detected by Pingoru
Oct 01, 2025, 01:31 PM UTC
Resolved
Oct 07, 2025, 11:35 AM UTC
Duration
5d 22h
Affected: Outbound Voice InteractionsOutbound Voice Interactions
Timeline · 4 updates
  1. investigating Oct 01, 2025, 01:31 PM UTC

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

  2. identified Oct 01, 2025, 04:02 PM UTC

    We have identified the problem affecting calling Czechia. We are actively working to recover service.

  3. monitoring Oct 02, 2025, 08:16 AM UTC

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

  4. resolved Oct 07, 2025, 11:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 30, 2025

IR27207 - VBC ContactPad login issues in NAM

Detected by Pingoru
Sep 30, 2025, 01:44 PM UTC
Resolved
Sep 30, 2025, 04:45 PM UTC
Duration
3h
Affected: ContactPadContactPad
Timeline · 3 updates
  1. investigating Sep 30, 2025, 01:44 PM UTC

    We are currently aware of an ongoing issue affecting the ContactPad login for Vonage Business Communications application. Our Incident Management team is investigating the issue with priority.

  2. monitoring Sep 30, 2025, 01:59 PM UTC

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

  3. resolved Sep 30, 2025, 04:45 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 →

Major September 29, 2025

IR27206 - Inbound calls to Swiss numbers failing

Detected by Pingoru
Sep 29, 2025, 04:06 PM UTC
Resolved
Sep 29, 2025, 08:18 PM UTC
Duration
4h 11m
Affected: Inbound Voice InteractionsInbound Voice Interactions
Timeline · 3 updates
  1. investigating Sep 29, 2025, 04:06 PM UTC

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

  2. monitoring Sep 29, 2025, 05:12 PM UTC

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

  3. resolved Sep 29, 2025, 08:18 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 →

Minor September 25, 2025

IR27205 - Outbound calls to China failing to connect from outside China

Detected by Pingoru
Sep 25, 2025, 08:50 AM UTC
Resolved
Sep 25, 2025, 04:40 PM UTC
Duration
7h 50m
Affected: Outbound Voice InteractionsOutbound Voice InteractionsOutbound Voice InteractionsOutbound Voice InteractionsOutbound Voice InteractionsOutbound Voice Interactions
Timeline · 4 updates
  1. investigating Sep 25, 2025, 08:50 AM UTC

    We are currently aware of an ongoing issue affecting outbound calling using non-Chinese number to call China. Our Incident Management team is investigating the issue with priority.

  2. identified Sep 25, 2025, 09:12 AM UTC

    We have identified the problem affecting calling China. We are working with our partner carriers to fully recover the service.

  3. monitoring Sep 25, 2025, 11:31 AM UTC

    Service is now recovered and we are monitoring. Please remember to follow the following rules when calling China, in order to prevent your callback numbers from being blocked by Chinese Operators: - Make no calls with a duration shorter than 3 minutes. - Make no unsolicited marketing calls. - Make minimal repeat calls from the same number in a rolling hour. - Make no calls from invalid, modified or spoofed origination (From) numbers.

  4. resolved Sep 25, 2025, 04:40 PM UTC

    This issue has been resolved. If you are still experiencing issues please contact support.

Read the full incident report →

Minor September 10, 2025

IR27195 - Error with Dial List calls and when using Log a Call - NAM

Detected by Pingoru
Sep 10, 2025, 03:53 PM UTC
Resolved
Sep 10, 2025, 05:32 PM UTC
Duration
1h 38m
Affected: Outbound Voice InteractionsOutbound Voice InteractionsSalesforce.com IntegrationSalesforce.com Integration
Timeline · 4 updates
  1. investigating Sep 10, 2025, 03:53 PM UTC

    We are currently aware of an ongoing issue affecting outbound calling via dial lists and using Log a Call for the subset of NAM Salesforce instances. Our Incident Management team is investigating the issue with priority.

  2. identified Sep 10, 2025, 04:31 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Sep 10, 2025, 05:02 PM UTC

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

  4. resolved Sep 10, 2025, 05:32 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 →

Minor September 8, 2025

IR27192 - India inbound numbers not connecting

Detected by Pingoru
Sep 08, 2025, 07:49 AM UTC
Resolved
Sep 12, 2025, 11:08 AM UTC
Duration
4d 3h
Affected: Inbound Voice InteractionsInbound Voice InteractionsInbound Voice InteractionsInbound Voice Interactions
Timeline · 7 updates
  1. investigating Sep 08, 2025, 07:49 AM UTC

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

  2. investigating Sep 08, 2025, 10:03 AM UTC

    The incident management team continues to work with the Carrier service provider to identify the problem.

  3. identified Sep 08, 2025, 01:58 PM UTC

    The provider of the impacted number range informed us that the outage is caused by a hardware malfunction in India, which has caused problems for a number of networks. We are working with them to get the issue resolved. As soon as we have any update we will let you know.

  4. identified Sep 09, 2025, 08:30 AM UTC

    The provider of the impacted number range is working to develop an alternative path. As soon as we have any update we will let you know.

  5. identified Sep 09, 2025, 03:03 PM UTC

    The provider of the impacted number range is working on resolving the issue related to the hardware malfunction, and have provided an ETA of 3 to 5 business days. We continue to monitor the progress and we will provide the next update in 3 business days, on Friday September 12th.

  6. monitoring Sep 11, 2025, 08:27 AM UTC

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

  7. resolved Sep 12, 2025, 11:08 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 →

Minor September 5, 2025

IR27191 - Unable to create new VCC users

Detected by Pingoru
Sep 05, 2025, 02:14 PM UTC
Resolved
Sep 12, 2025, 08:25 AM UTC
Duration
6d 18h
Affected: VCC Platform Supervisor & AdminVCC Platform Supervisor & AdminVCC Platform Supervisor & AdminVCC Platform Supervisor & AdminVCC Platform Supervisor & AdminVCC Platform Supervisor & Admin
Timeline · 7 updates
  1. investigating Sep 05, 2025, 02:14 PM UTC

    We are currently aware of an ongoing issue affecting the User Admin for the subset of accounts. Our Incident Management team is investigating the issue with priority.

  2. identified Sep 05, 2025, 02:16 PM UTC

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

  3. identified Sep 05, 2025, 03:30 PM UTC

    The incident management team continues to recover service.

  4. identified Sep 05, 2025, 04:27 PM UTC

    We are aware of an issue with licence management that can give an error when creating new user accounts effecting only a small subset of accounts in an 'edge-case' situation. We are not aware of impact to other product functionality. Our Incident Management and Development teams are aware and are preparing a permanent fix. If you are impacted with an error when attempting to create a user in Vonage Contact Centre please contact Customer Support. They can provide you with a temporary solution to ensure you can create new users and operate as normal. We anticipate the next milestone for this incident to be next week (W/C 8th September) as our Development Teams release the permanent fix into the product.

  5. identified Sep 08, 2025, 01:51 PM UTC

    We continue to make progress on the permanent resolution that is planned to be live W/C 8th Sept. If you are impacted with an error when attempting to create a user in Vonage Contact Centre please contact Customer Support who will provide you with a interim solution.

  6. monitoring Sep 11, 2025, 09:07 AM UTC

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

  7. resolved Sep 12, 2025, 08:25 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 →

Minor September 1, 2025

IR27190 - Conversation Analyzer Transcripts not completed

Detected by Pingoru
Sep 01, 2025, 07:24 AM UTC
Resolved
Sep 01, 2025, 11:37 AM UTC
Duration
4h 12m
Affected: Conversation AnalyzerConversation Analyzer
Timeline · 5 updates
  1. investigating Sep 01, 2025, 07:24 AM UTC

    We are currently investigating this issue.

  2. investigating Sep 01, 2025, 09:14 AM UTC

    We are continuing to investigate this issue.

  3. identified Sep 01, 2025, 09:15 AM UTC

    The issue was identified and a solution was implemented

  4. monitoring Sep 01, 2025, 09:15 AM UTC

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

  5. resolved Sep 01, 2025, 11:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 26, 2025

IR27187 - Unable to create new support cases

Detected by Pingoru
Aug 26, 2025, 10:32 AM UTC
Resolved
Aug 26, 2025, 12:45 PM UTC
Duration
2h 12m
Affected: Community HubCommunity HubCommunity HubCommunity HubCommunity HubCommunity Hub
Timeline · 3 updates
  1. identified Aug 26, 2025, 10:32 AM UTC

    We have identified an issue preventing new support cases to be opened in our community hub. We have identified the possible root cause and we are working towards a resolution.

  2. monitoring Aug 26, 2025, 11:03 AM UTC

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

  3. resolved Aug 26, 2025, 12:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 21, 2025

IR27186 - Historical Analytics not displaying some data

Detected by Pingoru
Aug 21, 2025, 08:23 AM UTC
Resolved
Aug 21, 2025, 02:32 PM UTC
Duration
6h 9m
Affected: Statistics / ReportingStatistics / Reporting
Timeline · 4 updates
  1. investigating Aug 21, 2025, 08:23 AM UTC

    We are currently investigating this issue.

  2. identified Aug 21, 2025, 10:35 AM UTC

    We have identified the possible root cause, and we are working in deploying a solution.

  3. identified Aug 21, 2025, 12:22 PM UTC

    We are actively working on the resolution. We are speeding up processing the remaining messages to restore the historical data being available in Analytics

  4. resolved Aug 21, 2025, 02:32 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 →

Minor August 19, 2025

IR27184 - Real Time Analytics and Team Monitoring data not displayed

Detected by Pingoru
Aug 19, 2025, 10:23 AM UTC
Resolved
Aug 19, 2025, 12:34 PM UTC
Duration
2h 11m
Affected: Statistics / ReportingStatistics / ReportingStatistics / ReportingStatistics / ReportingStatistics / ReportingStatistics / Reporting
Timeline · 4 updates
  1. identified Aug 19, 2025, 10:23 AM UTC

    We have identified an issue with Real Time Analytics and Team Monitoring not displaying some data. We have found the possible root cause and we are currently working on a solution.

  2. identified Aug 19, 2025, 10:49 AM UTC

    We have restored service to our EMEA and APAC nodes.

  3. monitoring Aug 19, 2025, 10:49 AM UTC

    We have restored service to our NAM nodes.

  4. resolved Aug 19, 2025, 12:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 16, 2025

IR27183 - GTT Outage

Detected by Pingoru
Aug 16, 2025, 03:00 PM UTC
Resolved
Aug 17, 2025, 11:14 AM UTC
Duration
20h 13m
Affected: Inbound Voice InteractionsInbound Voice Interactions
Timeline · 2 updates
  1. monitoring Aug 16, 2025, 03:00 PM UTC

    We are aware of an an issue involving GTT. Service is now recovered and we are monitoring. If you are still experiencing issues please contact Support.

  2. resolved Aug 17, 2025, 11:14 AM UTC

    This issue has been resolved. If you are still experiencing issues please contact Support.

Read the full incident report →

Major August 5, 2025

IR27180 - NAM calls not connecting

Detected by Pingoru
Aug 05, 2025, 04:11 PM UTC
Resolved
Aug 06, 2025, 08:22 AM UTC
Duration
16h 11m
Affected: Inbound Voice InteractionsInbound Voice InteractionsOutbound Voice InteractionsOutbound Voice InteractionsWebRTCWebRTCAI Studio Virtual AssistantAI Studio Virtual Assistant
Timeline · 11 updates

Read the full incident report →

Minor August 1, 2025

IR27177 - VCC Historical Analytics not displaying specific metrics

Detected by Pingoru
Aug 01, 2025, 11:03 AM UTC
Resolved
Aug 01, 2025, 03:26 PM UTC
Duration
4h 22m
Affected: Statistics / ReportingStatistics / ReportingStatistics / ReportingStatistics / ReportingStatistics / ReportingStatistics / Reporting
Timeline · 5 updates
  1. investigating Aug 01, 2025, 11:03 AM UTC

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

  2. investigating Aug 01, 2025, 12:01 PM UTC

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

  3. identified Aug 01, 2025, 01:57 PM UTC

    We have identified the problem with Historical Analytics reporting. We are now progressing to recover service.

  4. monitoring Aug 01, 2025, 03:05 PM UTC

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

  5. resolved Aug 01, 2025, 03:26 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 →