ccaas-status - Notice history

All systems operational

100% - uptime

CCaaS Europe - Voice Services - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS Americas - Voice Services - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS International - Email Services - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS International - Chat & Social Media - Operational

100% - uptime
Oct 2024 · 99.91%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS International - Reporting & Wallboard - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS International - Admin Portal - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS International - Agent UI - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS International - Core Services - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS International - Contact Expert Chat Services - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS International - Scripting - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS International - AI Voice Bots - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS international - AI Chat Bots - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS International - AI Email Bots - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

CCaaS Custom Connectors to Cisco - Operational

100% - uptime
Oct 2024 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2024
Nov 2024
Dec 2024

Notice history

Dec 2024

Nov 2024

Oct 2024

CiscoConnector failing
  • Update
    Update

    The outage was caused by Azure App Service resource health problems. The custom solution named Cisco Connector is hosted on Azure App Service resources which was having problems with a backend component. The following is from the Azure-supplied report about the incident: Title: PIR - App Service intermittent availability issues in West Europe Tracking ID: 5NXS-NR8 Event type: Service Issue Status: Resolved Service(s): App Service Region(s): West Europe Start time: 2024-10-17T08:30:00Z Resolve time: 2024-10-17T15:15:00Z Last update time: 2024-10-17T15:15:00Z Impacted subscriptions: dcffb1fb-e926-4e1e-bbdb-1894128838b3 (Buzzeasy - Production) What happened? Between 08:30 UTC and 15:15 UTC on 17 October 2024, a platform issue resulted in an impact to App Service in the West Europe region. Impacted customers may have experienced intermittent HTTP 500- level response codes, timeouts or high latency when trying to access apps hosted in the region. What went wrong and why? We determined that this issue had been caused by a backend component App Service operations rely on reaching an operational threshold, which manifested in the impact described above. How did we respond? 08:05 UTC on 17 October 2024 - Service monitoring detected unhealthy resources. 08:30 UTC on 17 October 2024 – Customer impact began. 11:45 UTC on 17 October 2024 – We determined this issue was caused by a backend component reaching an operational threshold. 15:15 UTC on 17 October 2024 - The Azure Platform self-healed the issue after monitoring efforts.

  • Investigating
    Investigating

    Select customers are experiencing failures with their custom Buzzeasy chatbot solution. Specifically, transfers of the chats to live agents using Cisco agent application are failing.

Webchat widget not loading on customers' webpage
  • Update
    Update

    Relevant DevOps workitem: Incident 118058: web-chat-connector-deployment restart cycle

  • Update
    Update

    According to our findings, the intermittent outage of the Buzzeasy webchat service on 2024-10-09 was due to increased traffic flowing through our webchat-connector microservice. The service had to process enough data to the point that the built-in monitoring system's liveness probe's health checking requests did not get a reply in time. As a result, the service was considered non-responsive which triggered automatic restarts, making the webchat widget temporarily unavailable for web pages that were loaded while a restart was in progress. We addressed the problem by on the one hand, increasing the maximum used memory limit of the service and on the other hand, allowing more time for the liveness probe's requests to get a response before restarts are triggered. This will prevent the service from being restarted prematurely while there is no real fault with the resource but rather there would just be some additional time needed for it to process all requests in its buffer. We will be continuing to monitor closely this system in following period. Furthermore, we will be planning to implement additional redundancies and resources between which the service can load balance its traffic in future.

  • Investigating
    Investigating

    Customers using the Buzzeasy webchat widget reported that the widget is intermittently not loading into the webpage where it's supposed to be embedded.

Oct 2024 to Dec 2024

Next