THIS IS A SCHEDULED EVENT Jul <var data-var='date'>8</var>, <var data-var='time'>08:00</var> - <var data-var='time'>18:00</var> CEST Jul <var data-var='date'> 3</var>, <var data-var='time'>13:09</var> CEST Scheduled - We will be performing planned maintenance on the Cleeng Sandbox environment on July 8, 2026. The Sandbox environment is expected to be unavailable from 08:00 CET until the end of the day. Please avoid using Sandbox during this maintenance window. We will post an update once the environment is available again.

Scheduled Sandbox Maintenance – July 8, 2026

Jun <var data-var='date'>24</var>, <var data-var='time'>21:11</var> CEST Resolved - 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. Jun <var data-var='date'>24</var>, <var data-var='time'>17:47</var> CEST Monitoring - 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. Jun <var data-var='date'>24</var>, <var data-var='time'>16:50</var> CEST Identified - 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.

Delays in 2FA Email Delivery

Jun <var data-var='date'>23</var>, <var data-var='time'>20:59</var> CEST Resolved - Mandrill confirmed that the issue regarding delayed emails is now resolved at 19:43 CET (17:43 UTC). As a result, login flows requiring 2FA emails should now function as expected. Jun <var data-var='date'>23</var>, <var data-var='time'>17:53</var> CEST Identified - 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.

Cleeng Publisher Login Failures Due to 2FA Email Delivery Delays

Jun <var data-var='date'>23</var>, <var data-var='time'>12:57</var> CEST Resolved - Between 12:11 CET and 12:34 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.

Cleeng Platform Outage

Apr <var data-var='date'> 4</var>, <var data-var='time'>00:31</var> CEST Resolved - 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. Apr <var data-var='date'> 4</var>, <var data-var='time'>00:03</var> CEST Identified - 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.

Core Platform - Service Degradation

Apr <var data-var='date'> 1</var>, <var data-var='time'>16:32</var> CEST Resolved - The fix is deployed, exportable reports should now work as expected. Apr <var data-var='date'> 1</var>, <var data-var='time'>16:12</var> CEST Monitoring - A fix has been implemented and is ready for release. Apr <var data-var='date'> 1</var>, <var data-var='time'>13:27</var> CEST Investigating - 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.

ChurnIQ - Degraded Performance of Exportable Tables

Mar <var data-var='date'>27</var>, <var data-var='time'>13:31</var> CET Resolved - 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.

ChurnIQ - Subscription Reporting Irregularity – Resolved

Mar <var data-var='date'> 6</var>, <var data-var='time'>17:45</var> CET Resolved - Data pipelines operating normally Mar <var data-var='date'> 6</var>, <var data-var='time'>17:30</var> CET Monitoring - Fix has been implemented and the data is now refreshed. We are monitoring the pipelines now. Mar <var data-var='date'> 6</var>, <var data-var='time'>16:05</var> CET Identified - Our vendor has identified the cause and is working on a fix. Mar <var data-var='date'> 6</var>, <var data-var='time'>14:36</var> CET Update - We are continuing to investigate this issue. Mar <var data-var='date'> 6</var>, <var data-var='time'>14:25</var> CET Investigating - 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.

Cleeng Reporting Data refresh is delayed.

Dec <var data-var='date'>16</var>, <var data-var='time'>18:03</var> CET Resolved - This incident has been resolved. Dec <var data-var='date'>16</var>, <var data-var='time'>13:44</var> CET Update - 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. Dec <var data-var='date'>16</var>, <var data-var='time'>09:49</var> CET Identified - 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.

ChurnIQ - Snowflake Outage

Nov <var data-var='date'>18</var>, <var data-var='time'>19:57</var> CET Resolved - This incident has been resolved. Nov <var data-var='date'>18</var>, <var data-var='time'>13:28</var> CET Monitoring - 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/).

CloudFlare global outage

Nov <var data-var='date'>13</var>, <var data-var='time'>13:29</var> CET 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.

Cleeng Sandbox environment unavailable

Jul <var data-var='date'> 8</var>, <var data-var='time'>00:30</var> CEST Resolved - 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.

MediaStore Widgets - service outage

May <var data-var='date'> 5</var>, <var data-var='time'>15:13</var> CEST Resolved - 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.

Core Platform - Configuration Sync Delay

Apr <var data-var='date'> 9</var>, <var data-var='time'>12:43</var> CEST Resolved - This incident has been resolved. Apr <var data-var='date'> 9</var>, <var data-var='time'>12:43</var> CEST Monitoring - The issue has been resolved as of 12:22 PM on April 9, 2025. The partial outage was a result of heavy load on the operational database, which has now been restarted and brought back up to full operational capacity. We will continue monitoring the platform. Apr <var data-var='date'> 9</var>, <var data-var='time'>12:21</var> CEST Investigating - We are experiencing a service degradation since 11:30 AM CET on April 9, 2025. Our engineers are currently working on bringing our systems back to normal.

Jan <var data-var='date'>17</var>, <var data-var='time'>10:28</var> CET Resolved - This incident has been resolved. Dec <var data-var='date'>18</var>, <var data-var='time'>09:51</var> CET Update - We are continuing to monitor for any further issues. Dec <var data-var='date'>18</var>, <var data-var='time'>09:29</var> CET Monitoring - Some drill-fields are temporarily unavailable. We are working to restore the full functionality as soon as possible.

We are currently experiencing an issue with drill-fields in the ChurnIQ dashboards

Jan <var data-var='date'> 9</var>, <var data-var='time'>09:08</var> CET Resolved - This incident has been resolved. Jan <var data-var='date'> 8</var>, <var data-var='time'>23:26</var> CET Investigating - 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.

15 minutes data autorefresh is not running automatically

Dec <var data-var='date'>18</var>, <var data-var='time'>15:10</var> CET Completed - The scheduled maintenance has been completed. Dec <var data-var='date'>18</var>, <var data-var='time'>15:00</var> CET In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec <var data-var='date'>16</var>, <var data-var='time'>16:22</var> CET Scheduled - Our platform will undergo a planned maintenance operation that requires short (<1 minute) downtime. During that time, our API will be unavailable. Scheduled processes (such as subscription processing) will remain unimpaired.

Scheduled database maintenance

Nov <var data-var='date'> 5</var>, <var data-var='time'>06:10</var> CET Resolved - The issue has been resolved. Nov <var data-var='date'> 5</var>, <var data-var='time'>05:27</var> CET Identified - The issue is now under control - emails are sent out with minimal delay (seconds) now. The team is working on a permanent fix. Nov <var data-var='date'> 5</var>, <var data-var='time'>04:58</var> CET Investigating - We are experiencing significant delays for transactional emails to customers. The team is working on resolving this issue.

Delayed customer email delivery

Aug <var data-var='date'>27</var>, <var data-var='time'>15:00</var> CEST Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>27</var>, <var data-var='time'>14:00</var> CEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>27</var>, <var data-var='time'>14:00</var> CEST Scheduled - As per AWS requirement, we will need to upgrade our operational Database to the latest version for the Sandbox environment. Upgrade maintenance window is scheduled between 14:00 and 15:00 CET on 27th Aug 2024. During the maintenance window our Sandbox environment, which is used for running tests will not be available for ~30minutes.

Database upgrade maintenance window for Sandbox environment

Aug <var data-var='date'>24</var>, <var data-var='time'>16:15</var> CEST Resolved - The missing data is synchronised, data in ChurnIQ is updated. Aug <var data-var='date'>23</var>, <var data-var='time'>08:02</var> CEST Identified - 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.

[Churn IQ 2.0] Service degradation

Aug <var data-var='date'>19</var>, <var data-var='time'>15:00</var> CEST Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>19</var>, <var data-var='time'>14:30</var> CEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>13</var>, <var data-var='time'>00:07</var> CEST Scheduled - As per AWS requirement, we will need to upgrade MYSQL RDS to the latest version. Upgrade maintenance window is scheduled between 14:30 to 15:00 CET on 19th Aug 2024. However, the actual RDS downtime will be around 1 minute within the maintenance window. During the RDS downtime of ~1 minute, the Core APIs will not be available, impacting normal Cleeng operations.

RDS Upgrade maintenance window

Jul <var data-var='date'>17</var>, <var data-var='time'>12:23</var> CEST Resolved - This incident has been resolved. Jul <var data-var='date'>16</var>, <var data-var='time'>14:47</var> CEST Monitoring - Because of an urgent hotfix by Looker, our Looker instance needs to be restarted. This process should take ~15 minutes and can happen anytime between 00:00 to 02:00 CET on 17th July 2024. During this 15 minutes period, dashboards won't load, and the scheduled jobs will fail.

15 minutes ChurnIQ Maintenance Window between 00:00 to 02:00 CET on 17th July 2024

Jun <var data-var='date'>27</var>, <var data-var='time'>16:00</var> CEST Resolved - Some looker dashboards were impacted between 16:00 CET 2024-06-27 to 09:30 CET 2024-06-28 resulting in not being delivered. This was because of a transition in our environment. Please note that exportable reports and segment builders were not impacted and worked as expected. The issue is already resolved.

Some Looker scheduled jobs failed causing dashboards not have been sent

May <var data-var='date'>13</var>, <var data-var='time'>09:22</var> CEST Resolved - This incident has been resolved. May <var data-var='date'>11</var>, <var data-var='time'>10:08</var> CEST Update - The issue is now fully resolved, ChurnIQ data is up to speed. May <var data-var='date'>11</var>, <var data-var='time'>09:17</var> CEST Monitoring - We are experiencing failures in our data pipeline, starting from today 1:00 CET. Due to this, the data across our reporting system (including scheduled reports) can be up to 14 hours old. The problem was already identified and fixed, the reporting data should be up-to-date again in the next few hours.

Delay in ChurnIQ data refresh

Apr <var data-var='date'>27</var>, <var data-var='time'>12:29</var> CEST Resolved - The infrastructure works as expected from 02:10 CET on 27/04/2024 Apr <var data-var='date'>27</var>, <var data-var='time'>12:28</var> CEST Investigating - At 00:45 CET on 27/04/2024, we saw a substantial growth in the traffic coming to our platform. Our Auto Scaling (ASG) kicked off and started adding more instances to the infrastructure. At 01:00, the spike was massive and the ASG could not keep up the rate of growth. This affected about 50% of traffic between 01:00 to 01:10. Between 1:10 to 1:40, the unhandled traffic reduced to 30%. We took further manual actions at 1:44 CET to scale to a larger number of instances. From 1:53 CET, the unhandled rate further improved to 5-10% and by 2:10, the infrastructure managed to handle all the incoming traffic as expected.

Is Cleeng down?

Cleeng status is UP

Lastest published events

Delays in 2FA Email Delivery

Cleeng Publisher Login Failures Due to 2FA Email Delivery Delays

Cleeng Platform Outage

Cleeng Services, Components and Regions

Recent Cleeng events

Scheduled Sandbox Maintenance – July 8, 2026

Delays in 2FA Email Delivery

Cleeng Publisher Login Failures Due to 2FA Email Delivery Delays

Cleeng Platform Outage

Core Platform - Service Degradation

ChurnIQ - Degraded Performance of Exportable Tables

Get your FREE account now,
5 monitors included!

Is Cleeng down?

Cleeng status is UP

Lastest published events

Delays in 2FA Email Delivery

Cleeng Publisher Login Failures Due to 2FA Email Delivery Delays

Cleeng Platform Outage

Cleeng Services, Components and Regions

Recent Cleeng events

Scheduled Sandbox Maintenance – July 8, 2026

Delays in 2FA Email Delivery

Cleeng Publisher Login Failures Due to 2FA Email Delivery Delays

Cleeng Platform Outage

Core Platform - Service Degradation

ChurnIQ - Degraded Performance of Exportable Tables

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!