Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Vonage Contact Centre (VCC) Outage History

Every past Vonage Contact Centre (VCC) outage tracked by IsDown, with detection times, duration, and resolution details.

There were 154 Vonage Contact Centre (VCC) outages since November 2023. The 66 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major March 23, 2026

March 2026: IR27286 - Call connectivity issues in EMEA region

Detected Mar 23, 2026 7:15 AM EDT · Resolved Mar 23, 2026 8:42 AM EDT · Duration about 1 hour

Vonage Contact Centre experienced call connectivity issues in the EMEA region for 1.5 hours due to a third-party outage that affected multiple service providers. The incident impacted outbound voice interactions, preventing some customers from making calls. The third party identified and resolved the underlying issue, with full service restoration confirmed by 10:56 UTC.

Major March 12, 2026

March 2026: IR27281 - Service outage in NAM region

Detected Mar 12, 2026 11:06 AM EDT · Resolved Mar 12, 2026 3:21 PM EDT · Duration about 4 hours

A major service outage affected Vonage Contact Centre APIs in the NAM region, impacting multiple components including ContactPad, VCC Platform Supervisor & Admin, WebRTC, Statistics/Reporting, Conversation Analyzer, and AI Studio Virtual Assistant. The incident primarily affected performance dashboards and API signaling across Vonage services. The outage lasted 4.3 hours before all services were fully restored.

Major February 26, 2026

February 2026: IR27275 - Inbound calls dropping issues in NAM region

Detected Feb 26, 2026 5:49 PM EST · Resolved Feb 27, 2026 12:37 PM EST · Duration about 19 hours

Vonage Contact Centre experienced a major incident where inbound calls were dropping in the North American (NAM) region, affecting Inbound Voice Interactions components. The issue persisted for 18.8 hours before being resolved, with the team working on a root cause analysis to be shared with affected customers.