Buzzeasy Outage History
Buzzeasy is up right nowBuzzeasy had 19 outages in the last 2 years totaling 1h 37m of downtime — averaging 0.8 incidents per month.
There were 19 Buzzeasy outages since October 9, 2025 totaling 1h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.
Web interface users unable to log in
Timeline · 1 update
- resolved Sep 30, 2026, 05:50 AM UTC
Type: Incident Duration: 2 hours and 56 minutes Affected Components: CCaaS International - Agent UI, CCaaS International - Admin Portal Sep 30, 07:05:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 30, 08:45:42 GMT+0 - Resolved - This incident has been resolved. We'll post the root cause shortly as the "postmortem" of this incident. Sep 30, 05:50:00 GMT+0 - Investigating - We are currently investigating an incident that manifests as userts being unable to log in to our web interface. Sep 30, 06:45:00 GMT+0 - Identified - We've identified the source of the problem and are working to fix it as soon as we can.
Agent UI slowness reported
Timeline · 1 update
The Graia CCaaS platform is experiencing intermittent degradation affecting call handling across all customer instances.
Timeline · 1 update
Portal stuck, Agent App fails to get voice config
Timeline · 1 update
Graia CCaaS Software Patching
Timeline · 1 update
- resolved Jun 28, 2026, 03:00 AM UTC
Type: Maintenance Affected Components: CCaaS International - AI Voice Bots, CCaaS Americas - Voice Services, CCaaS Europe - Voice Services Jun 24, 12:05:25 GMT+0 - Identified - Dear Customer, We would like to inform you that on 28-06-2026 there will be a scheduled maintenance window for applying software patches on the Graia CCaaS Voice components. Graia International: 28-06-2026 | 03:00 UTC | 2 h During this time all components will be operational, but we do anticipate a short voice service interruption during key moments of the update. Thank you for your understanding. If you have any questions, please contact us via the known communication channels. Kind Regards, Graia Team
Voice Service Degradation
Timeline · 1 update
Calls unresponsive at agents
Timeline · 1 update
EU02 single-instance voice platform degradation
Timeline · 5 updates
- investigating May 09, 2026, 12:23 PM UTC
We are currently investigating the reported incident that some customers are unable to handle inbound voice calls. This is affecting all agents of the affected customers but only customers hosted on one of our voice server instances.
- identified May 09, 2026, 01:00 PM UTC
Tenants hosted on the affected voice instance were moved to the secondary instance while the investigation continues.
- monitoring May 09, 2026, 01:33 PM UTC
We recovered the affected voice instance and performed test calls. The condition causing the service disruption was identified, and successful test calls after moving a test tenant back to the original instance confirmed that the instance was operating normally again.
- resolved May 09, 2026, 02:00 PM UTC
This incident has been resolved. As a precaution, tenants continue to run on the secondary voice instance until the root cause analysis can be completed.
- resolved May 12, 2026, 09:36 AM UTC
The incident was caused by a low-level third-party voice gateway component becoming overloaded, resulting in loss of voice client connectivity for agents. Initial analysis indicates a potential software bug in the affected component related to worker thread collisions under a specific combination of call load conditions. Although warning logs were generated by the affected service, the monitoring system did not detect the condition in time due to vendor-introduced log syntax changes that no longer matched the existing monitoring pattern. Corrective action plan: * Finalize voice gateway component bug assessment and apply fixes. * Update and validate monitoring rules for the new log entry syntax.
Customers are experiencing unresponsive agent interface and inability to start/end calls
Timeline · 1 update
Inbound Call Processing Failure
Timeline · 1 update
Part of EU voice servers unable to receive calls
Timeline · 1 update
Azure host machine failure
Timeline · 1 update
- resolved Mar 10, 2026, 01:10 PM UTC
Type: Incident Affected Components: CCaaS Europe - Voice Services, CCaaS International - AI Voice Bots Mar 10, 13:10:00 GMT+0 - Investigating - On 2026-03-10 between 13:10 - 13:25 UTC one of our virtual machines was temporarily unavailable for service due to an unplanned redeployment by Microsoft Azure that was necessary because of the host physical machine's failure. We apologize for any inconveniences this may have caused. Summary from Microsoft Azure: We're sorry, your virtual machine isn't available and it is being redeployed due to an unexpected failure on the host server. Azure has begun the auto-recovery process and is currently starting the virtual machine on a different host. Mar 10, 13:55:38 GMT+0 - Investigating - Relevant DevOps workitems: Task 148105: GMNT#2026031010000221 — Complete failure Graia
Graia Agent interface delays
Timeline · 1 update
Performance issues observed by some customers
Timeline · 1 update
- resolved Jan 16, 2026, 01:00 PM UTC
Type: Incident Affected Components: CCaaS Europe - Voice Services Jan 16, 13:00:00 GMT+0 - Investigating - We are currently investigating reports of problems mainly with voice channels. We apologize for the inconveniences caused and are attempting to resolve them as soon as possible Jan 21, 08:21:30 GMT+0 - Investigating - Relevant DevOps workitems: Task 144208: GMNT#2026011610000213 — Urgent Request - System Performance Issues Task 144172: GMNT#2026011610000115 — Hiba - Hajdu Ádám Task 144185: GMNT#2026011610000124 — Contact Number Task 144189: GMNT#2026011610000161 — FW: Issues with idle agents but calls waiting Jan 16, 17:03:58 GMT+0 - Resolved - Following an extensive troubleshootig session, our team found that there was a faulty node of our containarized infrastructure in which a lot of services were in a restart loop. The team isolated the faulty node following this up by its replacement with healthy one that no longer exhibits the behavior that was causing problems.
Intermittent Issue: Accept Button Missing in Agent UI
Timeline · 1 update
Partial Service Disruption Affecting Inbound Voice Services
Timeline · 1 update
- resolved Nov 24, 2025, 07:15 AM UTC
Type: Incident Affected Components: CCaaS Europe - Voice Services Nov 24, 07:15:00 GMT+0 - Investigating - Dear customer, A partial outage was discovered that impacted incoming calls for a few customers. Our team has resolved the issue, and the service has been fully re-established. We apologize for any inconvenience this may have caused. Graia.ai Team Nov 27, 09:49:06 GMT+0 - Investigating - Related DevOps workitems: Task 141787: Investigate VE EXT3 connector logs Bug 141817: VE Connector unregisters inbound numbers unexpectedly when SignalR client is reconnecting
CCaaS admin portal and agent UI access issues
Timeline · 1 update
Intermittent issues accessing the CCaaS admin portal and agent UI
Timeline · 1 update
- resolved Oct 09, 2025, 09:29 AM UTC
Type: Incident Affected Components: CCaaS International - Agent UI, CCaaS International - Admin Portal Oct 9, 09:29:00 GMT+0 - Investigating - Dear customer, We would like to inform you that, due to Microsoft ongoing service issues, you might experience problems when trying to access the admin portal or the agent UI. We will come back with an update as soon as possible. Thank you for understanding. Graia.ai Team Oct 9, 22:00:39 GMT+0 - Resolved - The issue was mitigated on Microsoft side. This incident can be closed. Oct 9, 19:53:00 GMT+0 - Investigating - Microsoft states that the issue was resolved on their end. Keeping under observation. Oct 9, 11:02:32 GMT+0 - Investigating - Microsoft acknowledged the issue and is working on mitigating the impact. MS reference number: QNBQ-5W8