Is Buzzeasy down?

Last checked 8m ago
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 8m ago; the most recent incident resolved 12d 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 15 incidents in the last 90 days (98.48% 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 98.48% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jul 20, 2026, 08:42 AM UTC · Resolved Jul 20, 2026, 08:42 AM UTC
    Timeline · 1 update
    • resolved · Jul 20, 2026, 08:42 AM UTC

      Type: Incident Duration: 41 minutes Affected Components: CCaaS International - Reporting & Wallboard, CCaaS International - Scripting, CCaaS International - Email Services, CCaaS International - Admin Portal, CCaaS International - Agent UI, CCaaS International - Core Services, CCaaS International - AI Voice Bots, CCaaS Americas - Voice Services, CCaaS Europe - Voice Services Jul 20, 08:42:00 GMT+0 - Investigating - The problem manifests to users of the portal web administration interface by it failing to load beyond the initial blank screen or to load page-specific content when navigating between menus. Contact center agents also see an error message such as “Failed to get voice configuration”, are unable to receive or initiate calls or are faling to load the web application entirely. Jul 20, 09:23:00 GMT+0 - Resolved - This incident has been resolved. Jul 20, 08:52:00 GMT+0 - Identified - The SRE team discovered the fact that a node is unresponsive by noticing the unusual metrics it is exhibiting. Jul 20, 09:08:00 GMT+0 - Identified - The existing pods that were on the unreachable node were moved away from it. Jul 20, 09:05:00 GMT+0 - Identified - The node pool was expanded with an additional node to take over the workload of the unresponsive one. Jul 20, 09:15:00 GMT+0 - Monitoring - Graia team members observed recovered functionality.

    Latest: Type: Incident Duration: 41 minutes Affected Components: CCaaS International - Reporting & Wallboard, CCaaS International - Scripting, CCaaS International - Email Services, CCaaS I…

  2. Resolved 41m
    Started Jul 20, 2026, 08:42 AM UTC · Resolved Jul 20, 2026, 09:23 AM UTC
    CCaaS Europe - Voice ServicesCCaaS Americas - Voice ServicesCCaaS International - Email ServicesCCaaS International - Reporting & WallboardCCaaS International - Admin PortalCCaaS International - Agent UICCaaS International - Core ServicesCCaaS International - ScriptingCCaaS International - AI Voice Bots
    Timeline · 6 updates
    • investigating · Jul 20, 2026, 08:42 AM UTC

      The problem manifests to users of the portal web administration interface by it failing to load beyond the initial blank screen or to load page-specific content when navigating between menus. Contact center agents also see an error message such as “Failed to get voice configuration”, are unable to receive or initiate calls or are faling to load the web application entirely.

    • identified · Jul 20, 2026, 08:52 AM UTC

      The SRE team discovered the fact that a node is unresponsive by noticing the unusual metrics it is exhibiting.

    • identified · Jul 20, 2026, 09:05 AM UTC

      The node pool was expanded with an additional node to take over the workload of the unresponsive one.

    • identified · Jul 20, 2026, 09:08 AM UTC

      The existing pods that were on the unreachable node were moved away from it.

    • monitoring · Jul 20, 2026, 09:15 AM UTC

      Graia team members observed recovered functionality.

    • resolved · Jul 20, 2026, 09:23 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved
    Started Jun 28, 2026, 03:00 AM UTC · Resolved Jun 28, 2026, 03:00 AM UTC
    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

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

  4. Resolved
    Started Jun 08, 2026, 01:57 PM UTC · Resolved Jun 08, 2026, 01:57 PM UTC
    Timeline · 1 update
    • 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

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

  5. Resolved
    Started Jun 08, 2026, 11:29 AM UTC · Resolved Jun 08, 2026, 11:29 AM UTC
    Timeline · 1 update
    • resolved · Jun 08, 2026, 11:29 AM UTC

      Type: Incident Duration: 14 days and 17 minutes Affected Components: CCaaS Europe - Voice Services Jun 22, 11:39:00 GMT+0 - Identified - Test calls confirmed an issue affecting voice call processing on the impacted server. Jun 22, 11:40:00 GMT+0 - Monitoring - Recovery actions were initiated to restore service. Jun 8, 11:29:00 GMT+0 - Investigating - One of the EU region voice servers began reporting error conditions. Jun 22, 11:46:00 GMT+0 - Resolved - Follow-up testing confirmed that voice services had returned to normal operation.

    Latest: Type: Incident Duration: 14 days and 17 minutes Affected Components: CCaaS Europe - Voice Services Jun 22, 11:39:00 GMT+0 - Identified - Test calls confirmed an issue affecting voi…

See the full Buzzeasy outage history

6 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 · 11 incidents View full outage history →