Buzzeasy incident

Calls unresponsive at agents

Minor Resolved View vendor source →

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

Started
May 19, 2026, 11:50 AM UTC
Resolved
May 19, 2026, 11:50 AM UTC
Duration
Detected by Pingoru
May 19, 2026, 11:50 AM UTC

Update timeline

  1. resolved May 19, 2026, 11:50 AM UTC

    Type: Incident Duration: 18 minutes Affected Components: CCaaS Europe - Voice Services May 19, 11:50:00 GMT+0 - Investigating - Agents began reporting symptoms of unresponsive or silent calls. May 19, 12:02:00 GMT+0 - Identified - A telephony service on one of the EU customer virtual machines experienced a software crash. Automatic recovery restarted the affected service. May 19, 12:03:00 GMT+0 - Monitoring - Successful outbound call from the recovered service was observed. May 19, 12:08:00 GMT+0 - Resolved - Agents continued to experience effects from calls that were already active during the incident (e.g. calls stuck, no audio, inability to end or retrieve calls). New calls established after recovery were handled normally. May 21, 14:00:00 GMT+0 - Postmortem - The incident was caused by a third-party voice gateway component becoming overloaded under specific high-load conditions. This overload triggered a software defect in the component, leading to worker thread conflicts. As a result, voice client connectivity for affected calls was disrupted, causing loss of call control and audio handling failures. Corrective Action Plan: Call Probing Implementation Automated Stuck Call Handling