Cloudli Outage History

Started Oct 13, 2025, 04:17 PM UTC· resolved Oct 15, 2025, 02:03 AM UTC

1. investigating Oct 13, 2025, 04:17 PM UTC

   Dear clients, We are currently investigating an issue with one of our USA IP network carriers impacting some of our USA customers services. We have identified the issue and are working the affected carrier to investigate further.

2. monitoring Oct 13, 2025, 04:38 PM UTC

   The issue has been identified on the affected IP carrier and traffic as been routed to our alternate IP network carriers as a temporary fix while we continue to investigate the affected IP network carrier. Service has restored.

3. monitoring Oct 13, 2025, 07:03 PM UTC

   We are continuing to work with our ISP for a permanent resolution, and will update this incident to a resolved status when permanent resolution has been acheived. Additionally, we would like to clarify that this issue is not related to our Global SBC infrastructure.

4. resolved Oct 15, 2025, 02:03 AM UTC

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

Read the full incident report →

Started Oct 08, 2025, 03:54 PM UTC· resolved Oct 10, 2025, 09:58 PM UTC

1. investigating Oct 08, 2025, 03:54 PM UTC

   We are currently experiencing an intermittent issue affecting outgoing calls on some USA accounts. Impacts: This could potentially cause abnormal delays or an inability to initiate calls. *** Nous rencontrons actuellement un problème intermittent affectant les appels sortants sur certains comptes américains. Impacts: Ceci pourrait potentiellement entraîner des délais anormaux ou à une incapacité à initier des appels.

2. monitoring Oct 08, 2025, 05:31 PM UTC

   We have put a work around in place and calls should be completing. If you are still experiencing issues please contact our support team. We continue to monitor the results. *** Nous avons mis en place une solution de contournement et les appels devraient être traités. Si vous rencontrez toujours des problèmes, veuillez contacter notre équipe d'assistance. Nous suivons de près les résultats.

3. resolved Oct 10, 2025, 09:58 PM UTC

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

Read the full incident report →

Started Oct 07, 2025, 08:22 PM UTC· resolved Oct 08, 2025, 03:48 PM UTC

1. investigating Oct 07, 2025, 08:22 PM UTC

   We are currently experiencing an issue affecting inbound calls with a carrier. We are investigating and we will update shortly. Impacts: This could potentially cause abnormal delays or an inability to receive calls. *** Nous rencontrons actuellement un problème affectant les appels entrants avec un opérateur. Nous enquêtons et nous mettrons à jour prochainement. Impacts: Ceci pourrait potentiellement entraîner des délais anormaux ou à une incapacité à recevoir des appels.

2. identified Oct 07, 2025, 09:42 PM UTC

   We have implemented a patch and calls are working fine again. Our teams continues to work on identifying the root cause and working through a final fix. *** Nous avons déployé un correctif et les appels fonctionnent à nouveau correctement. Nos équipes continuent de travailler à l'identification de la cause du problème et à la mise au point d'une solution définitive.

3. monitoring Oct 07, 2025, 11:11 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.

4. resolved Oct 08, 2025, 03:48 PM UTC

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

Read the full incident report →

Started Oct 03, 2025, 04:07 PM UTC· resolved Oct 05, 2025, 04:30 AM UTC

1. investigating Oct 03, 2025, 04:07 PM UTC

   We are currently experiencing an issue affecting Caller-Names (CNAM) on some inbound calls. We are working with the affected service provider to get this resolve as soon as possible. Impacts: Some calls are showing "0" instead of the caller-name. *** Nous rencontrons actuellement un problème affectant les noms de l'appelant (CNAM) sur les certains appels entrants. Nous collaborons avec l'opérateur concerné pour résoudre ce problème au plus vite. Conséquences : Certains appels affichent « 0 » au lieu du nom de l'appelant.

2. identified Oct 03, 2025, 07:42 PM UTC

   The issue has been identified and a fix is planned to be implemented this evening. *** Le problème a été identifié et un correctif devrait être mis en œuvre ce soir.

3. resolved Oct 05, 2025, 04:30 AM UTC

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

Read the full incident report →

Started Aug 21, 2025, 04:16 PM UTC· resolved Aug 22, 2025, 01:33 AM UTC

1. investigating Aug 21, 2025, 04:16 PM UTC

   Dear clients, We are currently experiencing an intermittent issue affecting some calls. We are investigating the issue. We will provide additional updates at 30 minute intervals.

2. identified Aug 21, 2025, 04:56 PM UTC

   We have identified the cause of the issue with inbound and outbound calls. We are currently preparing a fix for testing. We will provide an additional update in 30 minutes. We are estimating full resolution within 45 minutes. ------------- Technical Description: The issues being experienced right now are due to the configuration of our virtualization stack's switching protocols. We intend to implement a change to isolate specific traffic within the virtual network to enable better transfer rates under high load.

3. identified Aug 21, 2025, 05:44 PM UTC

   We are still in the process of implementing the resolution. All testing of the solution successfully passed. We will follow up within 30 minutes or sooner upon completion of implementing the fix.

4. identified Aug 21, 2025, 06:16 PM UTC

   We are still in the process of implementing the resolution, and have moved into post implementation testing of the solution. We will follow up within 30 minutes or sooner upon finalizing the resolution.

5. identified Aug 21, 2025, 06:53 PM UTC

   We are continuing to perform testing. Inbound and Outbound calls are passing at this time, however, we are not stating that we are complete. We will follow up within 1 hr or sooner upon finalizing the resolution. At that time we will move the incident into monitoring.

6. resolved Aug 22, 2025, 01:33 AM UTC

   We have verified that the issue is resolved. All inbound and outbound call traffic is passing. ------------- Technical Description: The issues experienced today were due to the configuration of our virtualization stack's switching protocols. The change made to isolate specific traffic within the virtual network, while effective, resulted in a issue between our system pbx and it's proxy servers causing intermittent call traffic spikes. We have resolved the issue by changing the routing path between the HA Pairs (our system pbx) and the proxy servers that support it's integration into the RTPEngine components of the gSBC. Further details will be provided upon request via Cloudli Technical Support in the form of an RFO in 2 -3 business days.

Read the full incident report →

Started Aug 20, 2025, 12:30 PM UTC· resolved Aug 21, 2025, 02:39 AM UTC

1. investigating Aug 20, 2025, 01:43 PM UTC

   We are currently experiencing an issue affecting outbound calls. Impacts: This could potentially cause abnormal delays or an inability to initiate calls. *** Nous éprouvons actuellement une problématique affectant les appels sortants. Impacts: Ceci pourrait potentiellement entraîner des délais anormaux ou à une incapacité à initier des appels.

2. identified Aug 20, 2025, 01:57 PM UTC

   The issue has been identified and fix is being implemented. Impact: Some outbound calls were getting no audio

3. monitoring Aug 20, 2025, 02:03 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.

4. investigating Aug 20, 2025, 02:34 PM UTC

   We are currently investigating this issue.

5. investigating Aug 20, 2025, 03:33 PM UTC

   Our Engineering teams continues to investigate this issue.

6. monitoring Aug 20, 2025, 04:11 PM UTC

   We believe that we have isolated the issue. We have implemented a resolution. All calls are working both inbound and outbound. We are continuing to monitor the situation closely.

7. monitoring Aug 20, 2025, 06:15 PM UTC

   We have implemented additional measures to bring us to resolution. Calls are working both inbound and outbound, please contact support if you continue to experience issues. We are continuing to monitor the situation closely.

8. resolved Aug 21, 2025, 02:39 AM UTC

   All systems are operational and stabilized. An RFO will be provided upon request to technical support in 2-3 business days.

Read the full incident report →

Started Aug 01, 2025, 03:04 PM UTC· resolved Aug 01, 2025, 07:24 PM UTC

1. investigating Aug 01, 2025, 03:04 PM UTC

   Hi, Please note that we are aware of the issue causing Clarity Portal to present Internal server Error Messages. This is not service impacting. An error in some subsystems related to the presentation and consolidation of invoice data is causing certain fields in the Dashboard page of Clarity to fail to display. We are actively working through resolution of the problem. Please submit a ticket in the event that you experience an issue through your regular support channels Thank you for your patience.

2. resolved Aug 01, 2025, 07:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 21, 2025, 02:09 PM UTC· resolved May 21, 2025, 03:17 PM UTC

1. identified May 21, 2025, 02:09 PM UTC

   Please note that we are aware of the following issue that may affect some of your accounts: - A large Canadian Internet service provider is currently experiencing connectivity issues affecting the Canadian Est regions (Quebec, Ontario). Our services are not affected by this event but some clients may have lost their IP connectivity. We keep following and monitoring the progress of this event with the affected provider. We will provide further updates as they become available. *** Veuillez noter que nous sommes conscients du problème suivant qui pourrait affecter certains de vos comptes : - Un important fournisseur d'accès Internet canadien rencontre actuellement des problèmes de connectivité dans l'Est canadien (Québec et Ontario). Nos services ne sont pas affectés par cet incident, mais certains clients pourraient avoir perdu leur connexion IP. Nous continuons de suivre l'évolution de cet incident avec le fournisseur concerné. Nous vous tiendrons informés dès que possible.

2. monitoring May 21, 2025, 02:36 PM UTC

   A fix has been implemented by the affected carrier and we are monitoring the results. *** Un correctif a été mis en œuvre par l'opérateur concerné et nous surveillons les résultats.

3. resolved May 21, 2025, 03:17 PM UTC

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

Read the full incident report →

Started May 05, 2025, 07:37 PM UTC· resolved May 06, 2025, 04:04 AM UTC

1. investigating May 05, 2025, 07:37 PM UTC

   We are currently experiencing an issue affecting the Mobile Application for Cloudli Business Phone. Impacts: This could potentially cause inability to initiate or receive calls. *** Nous rencontrons actuellement un problème affectant l'application mobile Cloudli Business Phone. Conséquences : Cela pourrait entraîner l'impossibilité de passer ou de recevoir des appels.

2. monitoring May 05, 2025, 08:26 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 May 06, 2025, 04:04 AM UTC

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

Read the full incident report →

Started Apr 29, 2025, 03:53 PM UTC· resolved Apr 29, 2025, 10:02 PM UTC

1. investigating Apr 29, 2025, 03:53 PM UTC

   We are currently experiencing an issue affecting incoming and outgoing calls. Impacts: This could potentially cause abnormal delays or an inability to initiate or receive calls. *** Nous éprouvons actuellement une problématique affectant les appels entrants et sortants. Impacts: Ceci pourrait potentiellement entraîner des délais anormaux ou à une incapacité à initier ou recevoir des appels.

2. monitoring Apr 29, 2025, 04:24 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 Apr 29, 2025, 10:02 PM UTC

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

Read the full incident report →

Started Mar 28, 2025, 03:32 PM UTC· resolved Mar 28, 2025, 05:36 PM UTC

1. investigating Mar 28, 2025, 03:32 PM UTC

   One of the Canadian Telco provider is currently experiencing an issue affecting inbound calls quality to many Canadian numbers Impacts: This could potentially cause call quality degradation issues such as delays, robotic voices, cuts, drops or others. *** Un opérateur de télécommunications canadien rencontre actuellement un problème affectant la qualité des appels entrants vers de nombreux numéros canadiens. Impact : Cela pourrait entraîner une dégradation de la qualité des appels, comme des retards, des voix robotisées, des coupures, des interruptions de connexion, etc.

2. monitoring Mar 28, 2025, 04:16 PM UTC

   A fix has been implemented by the affected Telco carrier and we are monitoring the results. *** Un correctif a été mis en œuvre par l'opérateur télécom concerné et nous surveillons les résultats.

3. resolved Mar 28, 2025, 05:36 PM UTC

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

Read the full incident report →

Started Mar 28, 2025, 02:10 PM UTC· resolved Mar 28, 2025, 02:26 PM UTC

1. investigating Mar 28, 2025, 02:10 PM UTC

   We are currently investigating this issue

2. resolved Mar 28, 2025, 02:26 PM UTC

   This incident has been resolved. Our team has thoroughly investigated the matter and implemented mitigation measures to prevent recurrence

Read the full incident report →

Started Jan 23, 2025, 10:31 PM UTC· resolved Jan 24, 2025, 04:22 AM UTC

1. investigating Jan 23, 2025, 10:31 PM UTC

   Dear clients, We are currently investigating an issue with Oracle Cloud affecting some of our Clarity services since around 4:20PM EST (21:20 GMT). Our Engineering Team is currently working with the provider to bring the services back online. Inbound and Outbound Calls are working and are not affected. Impacts: We have identified the Portal, Call Recording and API related services being affected. --- Chers clients, Nous étudions actuellement un problème avec Oracle Cloud qui affecte certains de nos services Clarity depuis environ 16h20 EST (21h20 GMT). Notre équipe d'ingénierie travaille actuellement avec le fournisseur pour remettre les services en ligne. Les appels entrants et sortants fonctionnent et ne sont pas affectés. Impacts : nous avons identifié les services liés au portail, à l'enregistrement des appels et à l'API comme étant affectés.

2. investigating Jan 23, 2025, 11:43 PM UTC

   Our engineering team continues to investigate the issue with the Cloud provider. --- Notre équipe d'ingénierie continue d'enquêter sur le problème avec le fournisseur de Cloud.

3. monitoring Jan 24, 2025, 12:28 AM 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.

4. resolved Jan 24, 2025, 04:22 AM UTC

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

Read the full incident report →

Started Dec 30, 2024, 09:57 AM UTC· resolved Dec 30, 2024, 01:25 PM UTC

1. investigating Dec 30, 2024, 09:57 AM UTC

   Since around 3:30 AM EST one Canadian telco carrier is experiencing problem mostly in Quebec regions like Notre-Dames-Des-Laurentides, Stoneham, Saint-Brigitte-De-Laval. We are currently working with the affected carrier to resolve this as soon as possible. Impacts: This could potentially cause abnormal delays or an inability to receive calls. *** Depuis environ 3:30 AM HNE, un transporteur canadien éprouve des problèmes principalement dans les régions du Québec comme Notre-Dames-Des-Laurentides, Stoneham, Saint-Brigitte-De-Laval. Nous travaillons actuellement avec le transporteur concerné pour résoudre ce problème dès que possible. Impacts : Cela pourrait potentiellement entraîner des délais anormaux ou une incapacité à recevoir des appels.

2. monitoring Dec 30, 2024, 11:15 AM UTC

   The Canadian Telco identified and resolved the issue at about 4:45 AM EST. Inbound calls have received OK since that moment. We will continue to monitor the situation. ------ La fournissuer de télécommunications canadienne a identifié et résolu le problème vers 4 h 45 HNE. Les appels entrants sont reçus correctement depuis ce moment. Nous continuerons de surveiller la situation.

3. resolved Dec 30, 2024, 01:25 PM UTC

   The Canadian Telco confirmed the resolution of the issue at 4:45 AM EST. Inbound calls have received OK since that moment. This issue is resolved. ------ La fournissuer de télécommunications canadienne a confirmé la résolution du problème vers 4 h 45 HNE. Les appels entrants sont reçus correctement depuis ce moment. Cette problem est résolu.

Read the full incident report →

Started Nov 13, 2024, 12:37 AM UTC· resolved Nov 13, 2024, 01:55 AM UTC

1. monitoring Nov 13, 2024, 12:37 AM UTC

   We saw a brief network issue that has been resolved. We are closely monitoring. All systems are up and operational at this time.

2. resolved Nov 13, 2024, 01:55 AM UTC

   This incident has been resolved.

Read the full incident report →