Is Buzzeasy down?

Last checked just now
Current status
Buzzeasy is up

No incidents right now.

Official status page: https://status.graia.cx · Polled every 5 minutes · 15 components tracked

Buzzeasy is operational right now. Last checked just now; the most recent incident resolved 15d ago.

Real-time Buzzeasy status, recent outages, and incident history — pulled directly from Buzzeasy's official status page at https://status.graia.cx every 5 minutes. Pingoru tracks 15 Buzzeasy services and has captured 23 incidents in the last 90 days (99.11% uptime). Get email, Slack, Discord, or webhook alerts the moment Buzzeasy reports a new incident — free for 5 monitors, no credit card.

Users who monitor Buzzeasy also follow these CRM services: HubSpot Intercom Jira Service Desk ActiveCampaign Teamwork Alchemer Formstack Help Scout Intapp Bullhorn View all 6,000+ providers
Buzzeasy uptime 99.11% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started May 30, 2026, 03:00 AM UTC · Resolved May 30, 2026, 03:00 AM UTC
    Timeline · 1 update
    • resolved · May 30, 2026, 03:00 AM UTC

      Type: Maintenance Duration: 2 hours and 37 minutes Affected Components: CCaaS International - AI Voice Bots, CCaaS Americas - Voice Services, CCaaS Europe - Voice Services May 30, 03:00:01 GMT+0 - Identified - Maintenance is now in progress May 30, 05:37:00 GMT+0 - Completed - Maintenance has completed successfully. May 30, 03:00:00 GMT+0 - Identified - Dear Customer, We would like to inform you that on 30-05-2026 there will be a scheduled maintenance window for applying security patches on the Graia CCaaS Voice components. Graia International: 30-05-2026 | 03:00 UTC | 3 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

    Latest: Type: Maintenance Duration: 2 hours and 37 minutes Affected Components: CCaaS International - AI Voice Bots, CCaaS Americas - Voice Services, CCaaS Europe - Voice Services May 30, …

  2. Resolved
    Started May 09, 2026, 12:23 PM UTC · Resolved May 09, 2026, 12:23 PM UTC
    Timeline · 1 update
    • resolved · May 09, 2026, 12:23 PM UTC

      Type: Incident Duration: 1 hour and 37 minutes Affected Components: CCaaS Europe - Voice Services May 9, 12:23:00 GMT+0 - Investigating - 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. May 9, 13:00:00 GMT+0 - Identified - Tenants hosted on the affected voice instance were moved to the secondary instance while the investigation continues. May 9, 13:33:00 GMT+0 - Monitoring - 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. May 9, 14:00:00 GMT+0 - Resolved - 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.

    Latest: Type: Incident Duration: 1 hour and 37 minutes Affected Components: CCaaS Europe - Voice Services May 9, 12:23:00 GMT+0 - Investigating - We are currently investigating the reporte…

  3. Resolved 1h 37m
    Started May 09, 2026, 12:23 PM UTC · Resolved May 09, 2026, 02:00 PM UTC
    CCaaS Europe - Voice Services
    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.

    Latest: 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 indicate…

  4. Resolved
    Started Apr 22, 2026, 05:37 AM UTC · Resolved Apr 22, 2026, 05:37 AM UTC
    Timeline · 1 update
    • resolved · Apr 22, 2026, 05:37 AM UTC

      Type: Incident Duration: 1 hour and 38 minutes Affected Components: CCaaS Europe - Voice Services, CCaaS International - Agent UI Apr 22, 05:37:00 GMT+0 - Investigating - Some customers are seeing that they cannot receive/make calls or that agents cannot end ongoing ones. We’re aware of the issue and are working on it urgently. We’re really sorry to be holding you up today! Please know our teams are working hard to get everything up and running, and we will update you as soon as possible with the latest information. Apr 22, 06:01:00 GMT+0 - Identified - We identified the problem and have started working on recovering functionality. Apr 22, 06:10:00 GMT+0 - Monitoring - We recovered functionality of the affected service and are continuing to monitor the system. Apr 22, 07:15:00 GMT+0 - Resolved - The incident will now be considered closed with the root cause to be announced when we conclude the investigation. In our status page's terms, this will come as a 'Postmortem' update to the incident.

    Latest: Type: Incident Duration: 1 hour and 38 minutes Affected Components: CCaaS Europe - Voice Services, CCaaS International - Agent UI Apr 22, 05:37:00 GMT+0 - Investigating - Some cust…

  5. Resolved 1h 38m
    Started Apr 22, 2026, 05:37 AM UTC · Resolved Apr 22, 2026, 07:15 AM UTC
    ccaas-statusCCaaS Europe - Voice ServicesCCaaS International - Agent UI
    Timeline · 4 updates
    • investigating · Apr 22, 2026, 05:37 AM UTC

      Some customers are seeing that they cannot receive/make calls or that agents cannot end ongoing ones. We’re aware of the issue and are working on it urgently. We’re really sorry to be holding you up today! Please know our teams are working hard to get everything up and running, and we will update you as soon as possible with the latest information.

    • identified · Apr 22, 2026, 06:01 AM UTC

      We identified the problem and have started working on recovering functionality.

    • monitoring · Apr 22, 2026, 06:10 AM UTC

      We recovered functionality of the affected service and are continuing to monitor the system.

    • resolved · Apr 22, 2026, 07:15 AM UTC

      The incident will now be considered closed with the root cause to be announced when we conclude the investigation. In our status page's terms, this will come as a 'Postmortem' update to the incident.

    Latest: The incident will now be considered closed with the root cause to be announced when we conclude the investigation. In our status page's terms, this will come as a 'Postmortem' upda…

See the full Buzzeasy outage history

9 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Buzzeasy outage history →

Or sign up free to get alerts when Buzzeasy breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 14 incidents View full outage history →