Cleeng Outage History
21 incidents recorded over the last 365 days, 19 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Cleeng Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 22, 2026 | PHP security vulnerabilities: Cleeng updateOn October 20, 2026, details of two critical vulnerabilities in PHP, known as PHP2shell, were made public. These vulnerabilities could allow an attacker to run code remotely on affected systems. Further information is… | 0 min | Resolved |
| Sep 30, 2026 | Core Platform - Incident ResolvedBetween 12:55 and 13:15 CET, a platform update caused a technical issue in our core services. During this time, some subscribers may have had trouble accessing their content or seen errors when logging in. Our team… | 0 min | Resolved |
| Sep 26, 2026 | Delayed reporting data and scheduled exportsThe connection between the two data sources was resolved around 4:50 in the morning. Everything is working as expected now. | 8h 5m | Resolved |
| Sep 9, 2026 | Scheduled Cleeng Dashboard MaintenanceThe scheduled maintenance has been completed. Thank you for your patience and understanding. | 2h 0m | Scheduled |
| Sep 8, 2026 | ChurnIQ - Cleeng Dashboard Sandbox environmentThe issue has now been resolved, and the Cleeng Dashboard in Sandbox is accessible again. Thank you for your patience and understanding. | 1h 11m | Resolved |
| Sep 4, 2026 | Service degradation of Core APIAn infrastructure degradation affected the Core APIs between 01:32 and 02:05 CEST. Publishers and their customers may have experienced increased response times or rejected API requests during this period. All other… | -592 min | Resolved |
| Aug 20, 2026 | Service Platform DegradationAugust 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 fully operational and functioning as expected. The end… | 0 min | Resolved |
| Aug 11, 2026 | Delayed Data RefreshThe reporting data is fully refreshed. All data pipelines are working as expected. | 43 min | Resolved |
| Jul 28, 2026 | Checkout Service InterruptionThe Cleeng Checkout and Widgets are fully operational in production. The issue has been resolved, and payment processing is functioning normally. The fix was implemented at 10:14:50 CEST, and no further occurrences have… | 19h 4m | Resolved |
| Jul 16, 2026 | Checkout & Widgets - Service DegradationThe AWS CloudFront issue has been resolved, and Cleeng Hosted Widgets are fully operational in production. Registrations, account creation, and payment processing have been restored. | 1h 11m | Resolved |
| Jul 8, 2026 | Scheduled Sandbox Maintenance – July 8, 2026The Sandbox environment migration is completed and working as usual. Please feel free to use it normally from now on. | 10h 0m | Scheduled |
| Jun 24, 2026 | Delays in 2FA Email DeliveryThe 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… | 4h 20m | Resolved |
| Jun 23, 2026 | Cleeng Publisher Login Failures Due to 2FA Email Delivery DelaysMandrill 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. | 3h 5m | Resolved |
| Jun 23, 2026 | Cleeng Platform OutageBetween 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… | 0 min | Resolved |
| Apr 3, 2026 | Core Platform - Service DegradationThe 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… | 28 min | Resolved |
| Apr 1, 2026 | ChurnIQ - Degraded Performance of Exportable TablesThe fix is deployed, exportable reports should now work as expected. | 3h 5m | Resolved |
| Mar 27, 2026 | ChurnIQ - Subscription Reporting Irregularity – ResolvedWe 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… | 0 min | Resolved |
| Mar 6, 2026 | Cleeng Reporting Data refresh is delayed.Data pipelines operating normally | 3h 20m | Resolved |
| Dec 16, 2025 | ChurnIQ - Snowflake OutageThis incident has been resolved. | 8h 14m | Resolved |
| Nov 18, 2025 | CloudFlare global outageThis incident has been resolved. | 6h 28m | Resolved |
| Nov 13, 2025 | Cleeng Sandbox environment unavailableCleeng 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. | 0 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Cleeng incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Cleeng Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Cleeng acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Cleeng outage in this window ran 19h 4m, against a mean recovery of 3h 34m. If you depend on Cleeng in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.