Resolved after 13 minutes, on May 22, 2026.
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.
Update timeline
- investigating May 22, 2026, 02:35 PM UTC
Agents began observing symptoms of unresponsive or silent calls..
- identified May 22, 2026, 02:46 PM UTC
A telephony service on one of the EU customer virtual machines experienced a software crash. Automatic recovery restarted the affected service..
- monitoring May 22, 2026, 02:47 PM UTC
The first successful call from the recovered service was observed..
- resolved May 22, 2026, 02:48 PM UTC
This incident has been resolved..
- monitoring May 28, 2026, 02:00 PM UTC
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.
Your product runs on more than Buzzeasy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services