Cloudli Communications Incident History

1. resolvedOct 22 · 10:06 UTC

   This incident has been resolved since 4:00 AM EDT. *** Cet incident a été résolu depuis 4:00 AM EDT.

Reported by Cloudli Communications on their status page.

1. resolvedOct 21 · 18:20 UTC

   -------English to Follow--------- Les mises à jour de sécurité de la plateforme Connect sont terminées et tous les systèmes fonctionnent normalement. La performance est revenue à ses niveaux habituels, et nous n'avons observé aucune perte de disponibilité pendant ces travaux. Merci de votre patience pendant que nous complétions cette précaution de routine. Si vous remarquez quoi que ce soit d'inhabituel, veuillez communiquer avec notre équipe de soutien à service@cloudli.com; nous serons heureux de vous aider. ----------------------------------- The security updates to the Connect platform have been completed, and all systems are operating normally. Performance has returned to its usual levels, and we saw no loss of availability during this work. Thank you for your patience while we completed this routine precaution. If you notice anything unusual, please contact our support team at service@cloudli.com and we’ll be glad to help.

Reported by Cloudli Communications on their status page.

1. postmortemOct 13 · 15:24 UTC

   Summary of Events:

   On October 8, 2026, at approximately 8:28 AM EDT, Cloudli received a monitoring alarm indicating that some inbound and outbound calls were failing on the Cloudli Connect platform. The issue was intermittent and affected fewer than 5% of total calls. Cloudli began troubleshooting at 8:37 AM EDT and identified the root cause at 9:04 AM EDT. A hotfix was implemented and completed across all Connect nodes at 9:10 AM EDT, at which point call completion fully recovered. Cloudli continued to monitor the platform and confirmed the incident resolved at 9:19 AM EDT.

   Incident Analysis and Mitigation Measures:

   Initial alarms were received at 8:28 AM EDT, and troubleshooting began at 8:37 AM EDT. At 9:04 AM EDT, the root cause was identified and Cloudli posted an update to its status page. A hotfix was implemented immediately and rolled out to all Connect nodes. Calls began recovering at 9:05 AM EDT, and the rollout was completed at 9:10 AM EDT, at which time the platform entered a monitoring state. Following a short period of proactive monitoring, the incident was formally resolved at 9:19 AM EDT.

   Root cause analysis determined that a small percentage of Connect nodes were unable to communicate with the shared storage network. The condition was triggered during the platform’s automated scaling procedures, in which the order of operations used to bring new systems online allowed the telephony service to start before the supporting storage-access module had fully loaded. Nodes brought online in this state could not communicate with the shared storage network, resulting in intermittent call failures. The condition was not related to a scheduled change or maintenance activity and did not affect all Connect nodes.

   Service was restored by applying a hotfix to all Connect nodes that ensures the storage-access module is fully loaded before the telephony service starts.

   To prevent recurrence, Cloudli has updated its deployment automation scripts so that this startup sequencing is enforced for all newly provisioned systems. This update has been completed and verified, eliminating the edge case that led to this incident.

   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.

Reported by Cloudli Communications on their status page.