Cloudli incident

Cloudli Virtual Fax API Issue | Problème avec l'API de fax virtuel Cloudli

Major Resolved View vendor source →

Cloudli experienced a major incident on June 15, 2026 affecting Other, lasting 33m. The incident has been resolved; the full update timeline is below.

Started
Jun 15, 2026, 02:22 PM UTC
Resolved
Jun 15, 2026, 02:56 PM UTC
Duration
33m
Detected by Pingoru
Jun 15, 2026, 02:22 PM UTC

Affected components

Other

Update timeline

  1. investigating Jun 15, 2026, 02:22 PM UTC

    We are currently investigating an API issue with the virtual fax product. This issue could have an impact on services for users using the API - our team is analyzing the situation. Regular virtual fax customers not using the API are not affected. *** Nous enquêtons actuellement sur un problème d'API concernant le service de fax virtuel. Ce problème pourrait impacter les services pour les utilisateurs de l'API ; notre équipe analyse la situation. Les clients utilisant le service de fax virtuel sans l'API ne sont pas concernés.

  2. monitoring Jun 15, 2026, 02:31 PM UTC

    A fix has been implemented and we are monitoring the results. *** Un correctif a été mis en œuvre et nous surveillons les résultats.

  3. resolved Jun 15, 2026, 02:56 PM UTC

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

  4. postmortem Jun 17, 2026, 07:08 PM UTC

    ## 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 ProcessFusion 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.