Cleeng had 20 outages in the last 2 years totaling 814h 10m of downtime — averaging 0.8 incidents per month.
There were 20 Cleeng outages since August 23, 2024 totaling 814h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.
August 20, 2026 at 08:05–08:30 CET The service platform experienced a period of degradation during this time. The issue has been resolved, and the platform is now fully operational and functioning as expected.
Cleeng reporting data has not refreshed since 07:00 CET today (2026-08-11). This happened because our job runners did not run the scheduled data pipeline. We are aware of the situation, a fix has been put in place, and the data pipelines are working now. We expect the data to start refreshing within 30 minutes. Please note that no data has been lost as a result of this incident, and it has no consequence on our platform operations.
The reporting data is fully refreshed. All data pipelines are working as expected.
Starting at 9:10 CET, we identified an issue affecting the checkout experience, where some customers were unable to load the checkout page or complete their purchases. The issue was caused by outdated cached credentials within one of our services. A temporary fix has been implemented, and the issue has not reoccurred since. We continue to monitor the platform closely while our engineering team works on a permanent solution, which is expected to be deployed by Monday at the latest. We apologize for any inconvenience caused and appreciate your patience.
The Cleeng Checkout and Widgets are fully operational in production. The issue has been resolved, and payment processing is functioning normally. No further occurrences have been observed since the fix was implemented.
We’re investigating an incident affecting Cleeng Widgets across all environments. Users may encounter 504 Gateway Timeout errors when loading checkout and other widget pages. Our engineering team is working to restore service. We’ll provide further updates as soon as more information is available.
We’ve isolated the incident to an AWS CloudFront issue affecting traffic to Cleeng Widgets across all environments. Our engineering team is monitoring the disruption and evaluating recovery options.
The incident has been traced to an ongoing AWS CloudFront service disruption, which is preventing traffic from reaching Cleeng Hosted Widgets. AWS is working to restore the service; updates are available on the AWS Health Dashboard: https://health.aws.amazon.com/health/status Hosted Widget clients remain impacted. We're monitoring AWS recovery and assessing alternative solutions.
The AWS CloudFront issue has been resolved, and Cleeng Hosted Widgets are fully operational in production. Registrations, account creation, and payment processing have been restored.
We are currently aware of an ongoing issue reported by our email provider, Mailchimp, which may cause delays in the delivery of 2FA emails. Mailchimp posted an incident on 24 June 2026 at 13:26 UTC, stating that they are investigating connectivity issues and email sending delays. As a result, customers using 2FA may experience delays in receiving their authentication codes when attempting to log in. Mailchimp's engineering team is actively investigating the issue and working toward a resolution. We are closely monitoring the situation and will provide updates as soon as more information becomes available. We apologize for the inconvenience and appreciate your patience.
Update – Improvements Observed in 2FA Email Delivery Delays We are seeing improvements regarding the issue affecting 2FA email delivery. Our email provider, Mandrill, posted an update on today (24 June 2026 at 15:26 UTC), indicating that connectivity issues and email sending delays are improving, while their engineering team continues to work on a permanent fix. Customers using 2FA may still experience intermittent delays in receiving their authentication codes when attempting to log in, though service performance is improving. We will continue to monitor the situation closely and provide further updates as more information becomes available. Thank you for your patience and understanding.
The issue affecting 2FA email delivery has been resolved. Mandrill marked the incident as resolved today at 18:48 UTC, confirming that the connectivity issues and email sending delays have been addressed. Customers should now be able to receive their 2FA emails as expected when attempting to log in. We will continue to monitor the service to ensure stability. We apologize for any inconvenience caused and thank you for your patience throughout this incident.
Login using 2FA may fail intermittently due to delayed or missing authentication emails sent via Mandrill. Users may be unable to complete the login process when a 2FA is required. This issue is caused by an ongoing incident with our email service provider (Mandrill), which is affecting email delivery performance. We are actively monitoring the situation and coordinating with them to resolve it as quickly as possible.
Mandrill confirmed that the issue regarding delayed emails is now resolved. As a result, login flows requiring 2FA emails should now function as expected.
Between 12:11 CET and 12:24 CET, Cleeng experienced a platform service disruption that may have impacted access to certain services. The issue has now been resolved, and services have been restored. We are continuing to closely monitor the platform to ensure ongoing stability. While service has been restored, our engineering team is still actively investigating the incident to determine the root cause and prevent similar occurrences in the future. We apologize for the disruption and thank you for your patience.
We are currently experiencing increased error rates affecting some endpoints. Our monitoring systems have detected higher-than-normal failed requests, and our engineering team is actively working on a resolution. Impact: Certain integrations and API requests may fail or respond slowly. Some customers may experience errors when accessing specific services.
The disruption affecting the endpoints has been resolved. All systems are now operating normally, and API requests and integrations are functioning as expected. We apologize for any inconvenience caused and thank you for your patience.
We have identified an issue affecting exportable tables in the dashboard. Some users may experience difficulty accessing the exportable tables in the publisher dashboard, however, the scheduled exports are not affected and are still being delivered as expected. Our team is actively investigating and working to restore full functionality. We apologize for any inconvenience this may have caused.
A fix has been implemented and is ready for release.
The fix is deployed, exportable reports should now work as expected.
We recently identified an issue affecting subscription counts in your reports, which began on 26 March 2026 at 13:22 CET and was fully resolved on 27 March 2026 at 13:05 CET. During this window, subscription totals were understated in the dashboard and subscription report. All data has since been corrected and is now accurate. No action is required on your end. We apologize for any inconvenience this may have caused.
Please be aware that due to a partial outage affecting a third-party data processing service, Cleeng reporting data refresh is currently delayed. We have been observing the delay since approximately 19:00 CET yesterday (5 March) and are coordinating with the vendor while they restore full service. Impact: ChurnIQ dashboards and exported data reports may not yet reflect the most recent activity. Data may appear delayed by several hours. Who is impacted: Clients using ChurnIQ dashboards or receiving exported reporting files may see data that is not fully up to date. Please note that Cleeng platform operations are not affected. All standard platform functionality and client transactions continue to operate normally.
We are continuing to investigate this issue.
Our vendor has identified the cause and is working on a fix.
Fix has been implemented and the data is now refreshed. We are monitoring the pipelines now.
Data pipelines operating normally
We are currently experiencing an external outage with Snowflake. Due to this, you may experience delayed visibility for the most recent data. The last successful data refresh occurred at 12:01 AM CET on December 16, 2025. As of 05:04 UTC, Snowflake has developed a fix and is preparing it for deployment. Snowflake estimates that the service will be restored within the next 5 hours.
Snowflake has provided an updated timeline, with service estimated to be restored by 3:00 PM UTC. We will continue to monitor and share further updates.
This incident has been resolved.
CloudFlare is experiencing a global outage, causing unavailability of our marketing pages (cleeng.com). This is NOT affecting Cleeng APIs, but you may be impacted by outages of our third party services (e.g. Adyen, https://status.adyen.com/).
This incident has been resolved.
Cleeng Sandbox environment was not available for almost 1 hour from 12:10 to 13:10 CET on 13th November 2025. The issue is fixed, and it is available for use now.
We experienced a service outage affecting MediaStore Widgets from yesterday, 12:26 CET until today, 14:10 CET. Root Cause: Human error during deployment - an external dependency was installed without sufficient testing, causing the widget service to fail. Impact: embedding of MediaStore Widgets was not working during this period. Resolution: The problematic dependency was rolled back and service was fully restored at 14:10. We apologize for the inconvenience and have implemented additional testing protocols to prevent similar issues in the future.
Between 13:32 and 14:05 CEST, we observed a temporary issue with the Configuration Service database, which may have affected certain integrations (Adyen, SK2, Samsung, Vizio, ReCaptcha). Most live traffic continued to receive configuration data from our fast-access memory layer, which temporarily stores recent settings as additional safeguard. Additionally, configuration changes made between 07:00 and 14:05 CEST were not saved and have been lost. A detailed timeline and impact assessment is in progress. RCA will be shared once available.
Dear Broadcasters, We've concluded our investigation into the recent incident regarding configuration sync delay. For a more comprehensive postmortem, please feel free to review the document attached below, which contains the full Root Cause Analysis \(RCA\). Thank you for your patience and continued support. [RCA\_2025Q2 - Configuration per Broadcaster Service Incident.pdf](https://drive.google.com/file/d/1e_uNO04PG7L7RYcgKK3qHgUj0sq9_lK2/view?usp=sharing)
For some unknown reason, workflow for 15 minutes data refresh is not running automatically since ~19:00 CET. Consequently, data is not be refreshed every 15 minutes, we will trigger a few manual runs to keep the data refreshed. As we see now, all other data refresh pipelines are running normally. We are currently working to find the solution.
This incident has been resolved.
Some drill-fields are temporarily unavailable. We are working to restore the full functionality as soon as possible.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are experiencing significant delays for transactional emails to customers. The team is working on resolving this issue.
The issue is now under control - emails are sent out with minimal delay (seconds) now. The team is working on a permanent fix.
The issue has been resolved.
Dear Broadcasters, We've concluded our investigation into the recent incident regarding the delayed customer email delivery. For a more comprehensive postmortem, please feel free to review the document attached below, which contains the full Root Cause Analysis \(RCA\). Thank you for your patience and continued support. [RCA-2024Q4-Delayed customer email delivery.pdf](https://drive.google.com/file/d/1J6-EhjlowfSVR2I-n-LDosw02ArIx0s0/view?usp=drive_link)
We are encountering a degradation of service with regards to the Churn IQ dashboard, which led to minor gaps in the data in exportable tables. Our team managed to already identify the root cause and we are actively working to resolve the matter.
The missing data is synchronised, data in ChurnIQ is updated.