Cloudli Communications Status Page

Oct 8, 2026 · resolved Oct 8

The issue is fully resolved. We will provide an RFO for this incident within three (3) business days.

Sep 3, 2026 · resolved Sep 3

## Summary of Events: On September 3rd, 2026, at 11:52 AM EDT, Cloudli Communications identified an issue with the WorkerNode Auto-scaler incorrectly shutting down multiple instances hosting micro-services, including those supporting the VS API and Cloudli Quoting Tool, resulting in temporary service disruption. The affected services were restored at 12:11 PM EDT. The WorkerNode auto-scaler determines the compute resources required to run micro-services in our hosting facility and scales instances accordingly. The process relies on resource-usage metrics. During this incident, the WorkerNode auto-scaler did not receive all required metric information and scaled the environment down, draining some micro-services nodes. Because the configured minimum node count was set too low, the environment was allowed to scale below the capacity required to re-allocate all affected micro-services to alternate instances. ## Incident Analysis and Mitigation Measures: Post-incident analysis identified incomplete metrics as the condition that caused the WorkerNode auto-scaler to reduce capacity beyond a safe operating threshold. The minimum auto-scaler node setting has been increased to a safe level to prevent the environment from scaling below the capacity required to maintain service availability. Engineering has also identified the metrics-reading issue and is working on permanent correction. These safeguards are intended to prevent a similar metrics issue from causing an unsafe reduction in WorkerNode micro-services capacity in the future. ## Final Remarks: While the incident was short in duration, 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. 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 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.

Is Cloudli Communications down right now?

No — Cloudli Communications is up. All systems operational as of Oct 12, 4:52 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.