Cloudli Outage History

Cloudli is up right now

Cloudli had 38 outages in the last 2 years totaling 413h 36m of downtime — averaging 1.6 incidents per month.

There were 38 Cloudli outages since June 26, 2024 totaling 413h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cloudli.com

Minor April 24, 2026

Performance Degradation Partner Quoting Tool

Detected by Pingoru
Apr 24, 2026, 05:04 PM UTC
Resolved
Apr 24, 2026, 07:43 PM UTC
Duration
2h 39m
Affected: Other
Timeline · 3 updates
  1. identified Apr 24, 2026, 05:04 PM UTC

    We are aware of an API issue with our upstream provider that is affecting the Partner Quoting Tool. We are working with our provider to resolve this issue. We will provide updates as they become available.

  2. monitoring Apr 24, 2026, 05:33 PM UTC

    Our upstream provider has resolved the issue. We will be monitoring throughout the remainder of the day.

  3. resolved Apr 24, 2026, 07:43 PM UTC

    This issue is resolved.

Read the full incident report →

Minor April 15, 2026

Intermittent Inbound Outbound Call Issues

Detected by Pingoru
Apr 15, 2026, 10:00 PM UTC
Resolved
Apr 16, 2026, 11:37 AM UTC
Duration
13h 36m
Affected: Inbound CallingInbound CallingOutbound CallingOutbound Calling
Timeline · 5 updates
  1. investigating Apr 15, 2026, 10:00 PM UTC

    We have received alarms that some customers are experiencing outbuond call issues. We are investigating the issue.

  2. identified Apr 15, 2026, 10:17 PM UTC

    We have restored service and will begin to implement further improvement.

  3. monitoring Apr 15, 2026, 10: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.

  4. monitoring Apr 15, 2026, 10:28 PM UTC

    A resolution has been implemented. We will continue to monitor the system health.

  5. resolved Apr 16, 2026, 11:37 AM UTC

    This incident has been resolved. Monitoring has shown that the system remains stable. We will follow up with an incident report within three (3) business days.

Read the full incident report →

Notice April 7, 2026

Canadian Inbound/Outbound Call Traffic

Detected by Pingoru
Apr 07, 2026, 02:42 PM UTC
Resolved
Apr 07, 2026, 03:15 PM UTC
Duration
32m
Affected: Inbound CallingOutbound Calling
Timeline · 3 updates
  1. investigating Apr 07, 2026, 02:42 PM UTC

    Nous sommes au courant d’un problème qui pourrait affecter le trafic des appels entrants et sortants pour les clients canadiens. **** We are aware of an issue that could affect inbound and outbound call traffic for Canadian customers.

  2. monitoring Apr 07, 2026, 02:42 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 07, 2026, 03:15 PM UTC

    L’incident ayant affecté le trafic des appels entrants et sortants pour les clients canadiens est maintenant entièrement résolu. Le service a été rétabli et fonctionne normalement. **** The incident impacting inbound and outbound call traffic for Canadian customers has been fully resolved. Service has been restored and is operating normally.

Read the full incident report →

Notice March 25, 2026

Short flap - systems recovered

Detected by Pingoru
Mar 25, 2026, 04:03 PM UTC
Resolved
Mar 27, 2026, 05:54 PM UTC
Duration
2d 1h
Affected: Online Portal (Web Consoles)Online PortalOnline PortalInbound CallingAPI ServicesRouting ServicesInbound CallingOutbound CallingCall NotificationsOutbound CallingPresenceInternet (ISP) ConnectivitySMS / Texting NotificationsOtherMobile Notifications (SSI)SMS & MMSOther
Timeline · 3 updates
  1. monitoring Mar 25, 2026, 04:03 PM UTC

    We experienced a short flap but the systems recovered. Outbound calls may take longer than usual to connect. We continue monitoring the systems. ****** Nous avons rencontré une brève interruption, mais les systèmes sont désormais rétablis. Les appels sortants peuvent entraîner des délais de connexion plus longs que d'habitude. Nous continuons de surveiller les systèmes.

  2. monitoring Mar 25, 2026, 06:05 PM UTC

    We are continuing to monitor the system. **** Nous continuons à surveiller le système.

  3. resolved Mar 27, 2026, 05:54 PM UTC

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

Read the full incident report →

Major March 24, 2026

Inbound and outbound calls issues | Appels entrants et sortants

Detected by Pingoru
Mar 24, 2026, 08:00 PM UTC
Resolved
Mar 24, 2026, 10:59 PM UTC
Duration
2h 58m
Affected: Online PortalInbound CallingAPI ServicesInbound CallingOutbound CallingCall NotificationsOutbound CallingInternet (ISP) ConnectivitySMS / Texting NotificationsMobile Notifications (SSI)SMS & MMSOtherOther
Timeline · 4 updates
  1. investigating Mar 24, 2026, 08:00 PM UTC

    We are experiencing an issue affecting incoming and outgoing calls. We are investigating. Impacts: This could potentially cause abnormal delays or an inability to initiate or receive calls. *** Nous rencontrons actuellement un problème affectant les appels entrants et sortants. Nous menons l'enquête. Impacts: Ceci pourrait potentiellement entraîner des délais anormaux ou à une incapacité à initier ou recevoir des appels.

  2. monitoring Mar 24, 2026, 08:48 PM UTC

    A fix has been implemented, calls are operational since 4:03 EDT and we are monitoring. Un correctif a été mis en place, les appels sont opérationnels depuis 16h03 HAE et nous assurons une surveillance.

  3. monitoring Mar 24, 2026, 09:59 PM UTC

    We are continuing to monitor the system. **** Nous continuons à surveiller le système.

  4. resolved Mar 24, 2026, 10:59 PM UTC

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

Read the full incident report →

Notice March 20, 2026

Incident with Inbound and Outbound calls on Cloud Business Phone and Fax services

Detected by Pingoru
Mar 20, 2026, 05:44 PM UTC
Resolved
Mar 20, 2026, 08:10 PM UTC
Duration
2h 25m
Affected: Inbound CallingSMS & MMSInbound CallingInbound CallingInbound CallingInbound CallingInbound CallingOutbound CallingInbound CallingOutbound CallingOutbound CallingOutbound CallingOutbound CallingOutbound CallingOutbound CallingSMS & MMS
Timeline · 3 updates
  1. investigating Mar 20, 2026, 05:44 PM UTC

    Bonjour, Veuillez noter qu'un problème technique peut affecter certains de vos comptes : Les appels entrants et sortants sont perturbés sur les services Cloud Business Phone et Fax. Nous avons identifié le problème et travaillons à sa résolution. Merci de votre patience. *** Hi, Please note that we have an issue that may affect some of your accounts: Inbound and Outbound calls are affected on Cloud Business Phone and Fax services We have identified the issue, and we are implementing the correction. Thank you for your patience.

  2. identified Mar 20, 2026, 06:05 PM UTC

    The issue has been identified, and the fix has been implemented. All services ae operational and we are now monitoring them. *** Le problème a été identifié et corrigé. Tous les services sont opérationnels et nous les surveillons actuellement.

  3. resolved Mar 20, 2026, 08:10 PM UTC

    The incident has been fully resolved since 1:49 EDT. L'incident est entièrement résolu depuis 1h49 HAE

Read the full incident report →

Minor March 13, 2026

Inbound and outbound calls | Appels entrants et sortants

Detected by Pingoru
Mar 13, 2026, 03:48 PM UTC
Resolved
Mar 13, 2026, 09:37 PM UTC
Duration
5h 48m
Affected: Routing ServicesInbound CallingInbound CallingInbound CallingInbound CallingInbound CallingInbound CallingInbound CallingOutbound CallingOutbound CallingInbound CallingOutbound CallingOutbound CallingOutbound CallingOutbound CallingOutbound CallingOutbound CallingInternet (ISP) ConnectivityOutbound Calling
Timeline · 3 updates
  1. investigating Mar 13, 2026, 03:48 PM UTC

    We are currently experiencing an issue affecting incoming and outgoing calls due to an IP backbone issue. Impacts: This could potentially cause abnormal delays or an inability to initiate or receive calls. *** Nous rencontrons actuellement un problème affectant les appels entrants et sortants en raison d'un problème de réseau IP. Impacts: Ceci pourrait potentiellement entraîner des délais anormaux ou à une incapacité à initier ou recevoir des appels.

  2. monitoring Mar 13, 2026, 04:20 PM UTC

    The affected IP backbone carrier has implemented a solution and we are monitoring the results. Service is currently restored to normal operations. *** L'opérateur IP dorsale concerné a mis en œuvre une solution et nous suivons les résultats. Le service est désormais rétabli.

  3. resolved Mar 13, 2026, 09:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 11, 2026

Network Provider Issues

Detected by Pingoru
Feb 11, 2026, 03:51 PM UTC
Resolved
Feb 11, 2026, 05:44 PM UTC
Duration
1h 52m
Affected: Inbound CallingInbound CallingOutbound CallingOutbound CallingInternet (ISP) Connectivity
Timeline · 7 updates

Read the full incident report →

Minor February 5, 2026

Clarity - Outbound Call Issues

Detected by Pingoru
Feb 05, 2026, 03:15 PM UTC
Resolved
Feb 05, 2026, 03:48 PM UTC
Duration
32m
Affected: Outbound Calling
Timeline · 3 updates
  1. investigating Feb 05, 2026, 03:15 PM UTC

    We are currently experiencing an issue with Freeswitch Gateways in Clarity. We are investigating the issue and will follow up when we have identified the issue. This is not globally impacting and is being reported only for notification purposes.

  2. monitoring Feb 05, 2026, 03:31 PM UTC

    The issue was confirmed to be with the Clarity Freeswitch gateways. Resolution is being tested now.

  3. resolved Feb 05, 2026, 03:48 PM UTC

    This issue is resolved.

Read the full incident report →

Minor January 30, 2026

Transfert de l'enregistrement des appels vers Dropbox | Call Recording transfer to Dropbox

Detected by Pingoru
Jan 30, 2026, 10:22 PM UTC
Resolved
Feb 02, 2026, 04:47 PM UTC
Duration
2d 18h
Affected: Other
Timeline · 3 updates
  1. identified Jan 30, 2026, 10:22 PM UTC

    Chers clients, Un problème a été détecté lors du transfert des enregistrements d'appels vers l'espace de stockage Dropbox et qui pourrais affecter certains clients utilisant cette fonctionalité. Nous travaillons actuellement à sa résolution le plus rapidement possible. Nous vous tiendrons informés de l'avancement de la situation. Impact : Les enregistrements des appels continuent d'être sauvegardés et mis en file d'attente en toute sécurité et seront transférés vers votre Dropbox une fois le problème résolu. *** Dear clients, A problem has been detected with the transfer of call recordings to customer's Dropbox storage that may impact some customers using this feature. We are currently working on the issue in order to resolve it as soon as possible. We will update you upon further progress. Impact: Call recordings continue to safely be saved and queued and will be transferred to your Dropbox when the issue is resolved.

  2. monitoring Feb 02, 2026, 04:07 PM UTC

    Le service d'enregistrement fonctionne à nouveau normalement. Tous les enregistrements effectués pendant l'incident ont été synchronisés avec succès avec les comptes Dropbox correspondants. **** The recording service has resumed to it's normal level of operation. All recordings generated during the incident have been successfully synchronized with the corresponding Dropbox accounts.

  3. resolved Feb 02, 2026, 04:47 PM UTC

    Nous confirmons que tous les enregistrements ont été transférés sur les comptes appropriés. Merci. **** All recordings are confirmed to have been transferred to the appropriate accounts. Thank you.

Read the full incident report →

Major January 9, 2026

Telco Carrier Inbound calls issue in Windsor ON. | Appels entrants d'un transporteur canadien à Windsor ON

Detected by Pingoru
Jan 09, 2026, 01:00 AM UTC
Resolved
Jan 09, 2026, 09:14 PM UTC
Duration
20h 13m
Affected: Inbound CallingInbound CallingInbound CallingInbound Calling
Timeline · 4 updates
  1. identified Jan 08, 2026, 07:29 PM UTC

    Since this morning, one of the Canadian Telco provider is currently experiencing an interconnection issue affecting inbound calls on some Canadian numbers in Windsor ON region. This affects mostly Bell originating calls. The issue has been identified and escalated for resolution by the affected carrier. Impacts: This could potentially cause inability to receive some calls in the affected region. *** Depuis ce matin, un fournisseur de télécommunications canadien rencontre actuellement un problème d'interconnexion affectant les appels entrants vers certains numéros canadiens de la région de Windsor, ON. Ce problème touche principalement les appels émis par Bell. Le problème a été identifié et transmis au transporteur concerné pour résolution. Conséquences : Il est possible que vous ne puissiez pas recevoir certains appels dans la region affecté.

  2. identified Jan 08, 2026, 11:32 PM UTC

    Affected carrier has dispatched technicians at the affected site location identified as the source of the interconnection issue in the Windsor,ON region. More info to come. *** L'opérateur a dépêché des techniciens sur le site identifié comme la source du problème d'interconnexion dans la region de Windsor, ON. Plus d'informations à venir.

  3. monitoring Jan 09, 2026, 03:04 PM UTC

    A fix has been implemented by the affected carrier yesterday evening and we are monitoring the results. *** Un correctif a été mis en place hier soir par l'opérateur concerné et nous suivons les résultats.

  4. resolved Jan 09, 2026, 09:14 PM UTC

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

Read the full incident report →

Major December 12, 2025

Intermittent Inbound/Outbound calls

Detected by Pingoru
Dec 12, 2025, 04:23 PM UTC
Resolved
Dec 12, 2025, 06:05 PM UTC
Duration
1h 42m
Affected: Inbound CallingOutbound Calling
Timeline · 2 updates
  1. monitoring Dec 12, 2025, 04:23 PM UTC

    We experienced an intermittent issue affecting inbound/outbound calls between 10:28 and 10:58 EST. Calls are now working. Our team will continue to monitor the situation. Impacts: This could potentially have cause abnormal delays or an inability to initiate/receive calls.

  2. resolved Dec 12, 2025, 06:05 PM UTC

    We are marking this incident as resolved. Please note that we will provide an analysis of the incident via Statuspage today.

Read the full incident report →

Minor October 20, 2025

Cloudli Connect Outbound calls | Appels Sortants Cloudli Connect

Detected by Pingoru
Oct 20, 2025, 02:17 PM UTC
Resolved
Oct 20, 2025, 05:00 PM UTC
Duration
2h 42m
Affected: Routing ServicesOutbound CallingCall Notifications
Timeline · 3 updates
  1. investigating Oct 20, 2025, 02:17 PM UTC

    We are currently experiencing an issue affecting outgoing calls, our engineering team is investigating. Impacts: This could potentially cause abnormal delays or an inability to initiate calls. *** Nous rencontrons actuellement un problème affectant les appels sortants. Notre équipe d'ingénieurs mène l'enquête. Impacts: Cela pourrait entraîner des retards anormaux ou une impossibilité de passer des appels.

  2. monitoring Oct 20, 2025, 02:37 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 Oct 20, 2025, 05:00 PM UTC

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

Read the full incident report →

Minor October 13, 2025

Cloudli USA Network Issue

Detected by Pingoru
Oct 13, 2025, 04:17 PM UTC
Resolved
Oct 15, 2025, 02:03 AM UTC
Duration
1d 9h
Affected: Inbound CallingInbound CallingOutbound CallingOutbound Calling
Timeline · 4 updates
  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 →

Major October 8, 2025

Outbound calls on some USA accounts | Appels sortants Comptes américains

Detected by Pingoru
Oct 08, 2025, 03:54 PM UTC
Resolved
Oct 10, 2025, 09:58 PM UTC
Duration
2d 6h
Affected: Outbound Calling
Timeline · 3 updates
  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 →

Major October 7, 2025

Clarity Inbound calls | Appels entrants Clarity

Detected by Pingoru
Oct 07, 2025, 08:22 PM UTC
Resolved
Oct 08, 2025, 03:48 PM UTC
Duration
19h 25m
Affected: Inbound Calling
Timeline · 4 updates
  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 →

Major October 3, 2025

Inbound Caller Names (CNAM) | Noms des appelants entrants (CNAM)

Detected by Pingoru
Oct 03, 2025, 04:07 PM UTC
Resolved
Oct 05, 2025, 04:30 AM UTC
Duration
1d 12h
Affected: Inbound Calling
Timeline · 3 updates
  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 →

Minor August 21, 2025

Clarity Calls Incident

Detected by Pingoru
Aug 21, 2025, 04:16 PM UTC
Resolved
Aug 22, 2025, 01:33 AM UTC
Duration
9h 16m
Affected: Inbound CallingOutbound Calling
Timeline · 6 updates
  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 →

Minor August 20, 2025

Clarity Outbound calls | Clarity Appels Sortants

Detected by Pingoru
Aug 20, 2025, 12:30 PM UTC
Resolved
Aug 21, 2025, 02:39 AM UTC
Duration
14h 8m
Affected: Inbound CallingOutbound Calling
Timeline · 8 updates
  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 →

Minor August 1, 2025

GENERAL NOTICE

Detected by Pingoru
Aug 01, 2025, 03:04 PM UTC
Resolved
Aug 01, 2025, 07:24 PM UTC
Duration
4h 19m
Affected: Clarity Portal
Timeline · 2 updates
  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 →

Notice May 21, 2025

Canadian ISP provider incident | Incident fournisseur d'accès Internet canadien

Detected by Pingoru
May 21, 2025, 02:09 PM UTC
Resolved
May 21, 2025, 03:17 PM UTC
Duration
1h 7m
Affected: Routing ServicesInbound CallingInbound CallingInbound CallingInbound CallingInbound CallingCall NotificationsOutbound CallingInbound CallingOutbound CallingOutbound CallingOutbound CallingOutbound CallingInternet (ISP) ConnectivityOutbound Calling
Timeline · 3 updates
  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 →