Cloudli Communications Status Page

Aug 26, 2026 · resolved Aug 26

## Summary of Events: On August 26, 2026, at approximately 10:46 AM EDT, Cloudli identified an issue affecting outbound call routing across the Cloudli Connect and Contact Centre platforms. By 10:50 AM EDT, Cloudli confirmed that inbound calling on both Contact Centre and standard Connect services was not affected and continued to function normally. The root cause was identified at 11:02 AM EDT, at which point Cloudli began implementing corrective measures and outbound calls began recovering. A fix was implemented and the affected systems were placed into a monitoring state at 11:06 AM EDT, marking restoration of outbound calling service. Cloudli continued to monitor system performance and confirmed the incident fully resolved at 11:29 AM EDT. ## Incident Analysis and Mitigation Measures: Root cause analysis determined that the disruption originated from a failure at a single node within Cloudli's BGP network. Due to a misconfiguration of the BGP network by an upstream provider, the affected node did not recover correctly following the failure, which disrupted outbound call routing across the impacted services. This aspect of the issue was resolved promptly, restoring service to the majority of the affected telephony nodes. Further investigation identified that a single telephony node had IP routing tables cached. This required Cloudli to manually reset the routing table cache on that node in order to fully restore outbound calling service. To prevent recurrence, Cloudli is replacing the affected BGP node and working with the upstream provider to correct the underlying misconfiguration. Additionally, Cloudli has modified the routing table configuration on the affected telephony node so that IP routing tables are no longer cached, removing the need for manual intervention should a similar event occur. ## Final Remarks: At Cloudli, we take any interruption of service very seriously and are continuously evaluating new processes and mitigation measures that can be proactively implemented to ensure service continuity. When service interruptions do occur, our incident management procedure prioritizes prompt and clear notification, and timely status and resolution updates to our customers and partners. We thank you for your continued support. Please feel free to reach out if you would like to discuss the particulars of this incident report further.

Aug 20, 2026 · resolved Aug 20

This incident has been resolved. *** Cet incident a été résolu.

Aug 11, 2026 · resolved Aug 11

This issue has been resolved and confirmed via monitoring.

Jul 29, 2026 · resolved Jul 29

## Summary of Events: On July 29, 2026, beginning at approximately 9:07 AM EDT, Cloudli was notified of system alarms affecting portions of the Cloudli Connect voice platform. Two client hosts supporting registrar workloads experienced kernel panics caused by Media service modules operating in kernel mode. The incident affected SIP registrations and carrier connectivity and resulted in failed calls, including 603 “All Routes Exhausted” responses, as well as isolated calls with no audio issues. ## Incident Analysis and Mitigation Measures: Initial alarms were received at 9:07 AM EDT, and troubleshooting began at 9:10 AM. The unresponsive client host was rebooted at 9:15 AM. Cloudli posted investigating and identified updates at 9:21 AM and 9:23 AM, respectively. Test calls succeeded by 9:30 AM, and monitoring began at 9:33 AM, marking the system “Operational.” At this time Cloudli NOC continued monitoring the systems proactively as we began root cause analysis to implement a resolution. Cloudli issued a monitoring update at 12:47 PM notifying partners and customers of additional measures taken to mitigate the issue. The incident was formally resolved at 2:26 PM EDT. Root cause analysis determined that client hosts experienced kernel panics associated with media service modules running in kernel mode for improved performance. The host failures disrupted registrar services and carrier routing-data access. Although cluster jobs were distributed across separate servers and datacenters, each registrar cluster relies on a single caching database instance, by design, for carrier database access. When the carrier cluster could not access the caching database, calls returned 603 “All Routes Exhausted” responses. The media service modules instability also caused intermittent audio failures. Service was restored by rebooting the affected client hosts and restarting the media service module instances associated with audio failures. Engineering will continue investigating media service modules’ kernel-mode panic behavior and implement options that preserve performance and host stability. Cloudli will also complete additional redundancy work, including removal of the single-instance caching database dependency within each registrar cluster. ## Final Remarks: At Cloudli, we take any interruption of service very seriously and are continuously evaluating new processes and mitigation measures that can be proactively implemented to ensure service continuity. When service interruptions do occur, our incident management procedure prioritizes prompt and clear notification, and timely status and resolution updates to our customers and partners. We thank you for your continued support. Please feel free to reach out if you would like to discuss the particulars of this incident report further.

Jun 15, 2026 · resolved Jun 15

## Executive Summary Virtual Fax API communications were disrupted. This impacted the provisioning of Virtual Fax accounts, fax transmission through both the API and Portal, and retrieval of faxes through the API and Portal. Fax2Email and Email2Fax services remained fully operational throughout the incident. ## Root Cause Analysis On June 13, 2026, at 23:17 \(EST\), the 3rd-Party Fax Backend LetsEncrypt certificate was automatically renewed. As part of the certificate renewal process, a new intermediate signing certificate was introduced. The server responsible for Cloudli Virtual Fax API integrations did not have this intermediate certificate present in its trusted certificate store and was therefore unable to validate the renewed 3rd-Party Fax Backend certificate. ## Incident Analysis and Mitigation Measures: Because the underlying server infrastructure and messaging services remained operational, existing monitoring systems did not detect the issue. The first customer-reported indication of the problem occurred on June 14, 2026, at 23:57 EDT when a customer opened a support ticket reporting fax failures through Portal. The NOC team was notified on June 15, 2026, at 08:45 EDT and immediately began investigating. ## Conclusion The issue was resolved at 10:30 EST on June 15, 2026, after the missing intermediate signing certificate was imported into the server trusted certificate store. Additional monitoring was implemented later that day to proactively detect similar failures and automatically notify the on-call team. ## Final Remarks: At Cloudli, we take any interruption of service very seriously and are continuously evaluating new processes and mitigation measures that can be proactively implemented to ensure service continuity. When service interruptions do occur, our incident management procedure prioritizes prompt and clear notification, along with timely status updates and resolution communications to our customers and partners. We thank you for your continued support. Please feel free to reach out if you would like to discuss the particulars of this incident report further.

Is Cloudli Communications down right now?

No — Cloudli Communications is up. All systems operational as of Aug 28, 1:45 AM UTC.

What is Cloudli Communications's current status?

Cloudli Communications: All Systems Operational. Alert24 checks Cloudli Communications's status page continuously and can notify you the moment it changes.

How do I get alerted when Cloudli Communications goes down?

Alert24 monitors Cloudli Communications and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.