ccaas-status - Notice history

99.99% uptime

CCaaS Europe - Voice Services - Operational

99.91% uptime
Mar 2026 · 99.99%Apr · 99.76%May · 99.98%
Mar 2026
Apr 2026
May 2026

CCaaS Americas - Voice Services - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS International - Email Services - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS International - Chat & Social Media - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS International - Reporting & Wallboard - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS International - Admin Portal - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS International - Agent UI - Operational

99.99% uptime
Mar 2026 · 100.0%Apr · 99.96%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS International - Core Services - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS International - Contact Expert Chat Services - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS International - Scripting - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS International - AI Voice Bots - Operational

99.99% uptime
Mar 2026 · 99.99%Apr · 99.99%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS international - AI Chat Bots - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS International - AI Email Bots - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

CCaaS Custom Connectors to Cisco - Operational

100.0% uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%
Mar 2026
Apr 2026
May 2026

Notice history

View current status

May 2026

EU02 single-instance voice platform degradation
ResolvedPartial outage1 hour 37 minutes
  • PostmortemUTC

    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.

  • ResolvedUTC

    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.

  • MonitoringUTC

    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.

  • IdentifiedUTC

    Tenants hosted on the affected voice instance were moved to the secondary instance while the investigation continues.

  • InvestigatingUTC

    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.

Apr 2026

Customers are experiencing unresponsive agent interface and inability to start/end calls
ResolvedPartial outage1 hour 38 minutes
  • PostmortemUTC

    The issue was caused by a backlog in the voice processing layer, which led to internal call queues becoming saturated. As a result, new calls could not be established, and existing sessions could not be properly terminated. 

      

    Further investigation showed that this condition was triggered by a recently deployed minor version update to a third-party telephony component within the voice server (applied during the maintenance window on April 18, 2026). This version exhibited stability issues when handling higher call volumes, leading to the observed behaviour. 

    Corrective action plan:
    Rollback to the previous stable version of the voice server software.

  • ResolvedUTC

    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.

  • MonitoringUTC

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

  • IdentifiedUTC

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

  • InvestigatingUTC

    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.

Customers are experiencing unresponsive agent interface and inability to start/end calls
ResolvedPartial outage1 hour 36 minutes
  • PostmortemUTC

    The issue was caused by a backlog in the voice processing layer, which led to internal call queues becoming saturated. As a result, new calls could not be established, and existing sessions could not be properly terminated. 

      

    Further investigation showed that this condition was triggered by a recently deployed minor version update to a third-party telephony component within the voice server (applied during the maintenance window on April 18, 2026). This version exhibited stability issues when handling higher call volumes, leading to the observed behaviour. 

    Corrective action plan:
    Rollback to the previous stable version of the voice server software.

  • ResolvedUTC

    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.

  • MonitoringUTC

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

  • InvestigatingUTC

    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.

APR18
Graia CCaaS Security Patching
CompletedMaintenance3 hours 28 minutes
  • CompletedApril 18, 2026 at 6:28 AMUTC

    Dear Graia Customer,

    We would like to inform you that we have completed the scheduled maintenance for Graia International.

    To benefit immediately from the new changes please refresh your browser with CTRL+F5.

    The latest release notes will be available at https://docs-ccaas.graia.ai/releasenotes/release_notes.html

    Kind Regards,

    GraiaTeam

  • In progressApril 18, 2026 at 3:00 AMUTC
    Maintenance is now in progress
  • PlannedApril 18, 2026 at 3:00 AMUTC

    Dear Customer,

    We would like to inform you that on 18-04-2026 there will be a scheduled maintenance window for applying security patches on the Graia CCaaS Voice components.

    Graia International: 18-04-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

Mar 2026

Previous

Mar 2026 to May 2026

Next