Buzzeasy incident

Voice Service Degradation

Minor Resolved View vendor source →

Buzzeasy experienced a minor incident on June 8, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jun 08, 2026, 01:57 PM UTC
Resolved
Jun 08, 2026, 01:57 PM UTC
Duration
Detected by Pingoru
Jun 08, 2026, 01:57 PM UTC

Update timeline

  1. resolved Jun 08, 2026, 01:57 PM UTC

    Type: Incident Duration: 12 minutes Affected Components: CCaaS Europe - Voice Services Jun 8, 14:05:00 GMT+0 - Monitoring - Recovery actions were initiated to restore service. Jun 8, 14:09:00 GMT+0 - Resolved - Follow-up testing confirmed that voice services had returned to normal operation. Jun 8, 13:57:00 GMT+0 - Investigating - Automated monitoring detected the issue and generated an alert. Jun 8, 14:03:00 GMT+0 - Identified - Test calls confirmed an issue affecting voice call processing on the impacted server. Jun 9, 14:00:00 GMT+0 - Postmortem - The incident was caused by a software defect within a third-party voice gateway component that was triggered under specific high-load conditions. When the defect was triggered, the affected voice server was no longer able to process call-related activities correctly, resulting in disruption to voice client connectivity, call control functions, and audio handling for impacted calls Service was restored following recovery actions on the affected voice server Corrective Action Plan: Improvements to the Call Probing Implementation Deploy new Voice Gateway version 20.20.0 GA on QA Enable Active-Active Voice Gateway functionality on QA Deploy new Voice Gateway version 20.20.0 GA on Production Enable Active-Active Voice Gateway functionality on Production for Instance 5-6