Cleeng logo

Is Cleeng Down?

SaaSLive status, outages, and incident history

No. Cleeng is up right now.

Every monitored Cleeng system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment Cleeng breaks

Cleeng is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Cleeng status page
How we know: the official Cleeng status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Cleeng Status Summary

As of 11:55 UTC on 9 November 2026, Cleeng is operational. PulsAPI checked Cleeng's official status page and found 7 of 7 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Cleeng, counting degraded performance as up. The latest incident, "PHP security vulnerabilities: Cleeng update", was on Oct 22, 2026 and lasted 0 min.

Cite as: PulsAPI, “Cleeng status”, checked 9 November 2026, 11:55 UTC. https://www.pulsapi.com/services/cleeng

Cleeng Component Status

The main Cleeng systems on this page. All 7 are operational right now.

7operational
API
Operational
Checkout & Other Widgets
Operational
ChurnIQ
Operational

4 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Developers Portal, Help Center, Sandbox, Website.

See all of them free

Component statuses may change independently during partial outages.

Recent Cleeng Outages & Incidents

Incident history from the official Cleeng status page, including resolution updates.

PHP security vulnerabilities: Cleeng updateResolved Oct 22, 2026 · 0 minResolved

On 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 available in the PHP security announcement (https://www.php.net/archive/2026.php#2026-10-20-1) Our engineering team responded quickly and applied the patches to all our systems as soon as the patches were released. Our services kept running normally throughout, with no downtime or impact for our customers. We also reviewed our traffic for the whole of October 2026 and found no evidence of suspicious activity or misuse linked to these vulnerabilities. We’ll keep monitoring and will post here if anything changes. We recommend that you also check whether your own systems or third-party services use PHP, and apply the latest security updates from PHP and your software providers.

Core Platform - Incident ResolvedResolved Sep 30, 2026 · 0 minResolved

Between 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 fixed the issue quickly, and everything has been running normally since 13:15 CET. We're reviewing our update process so this doesn't happen again and we apologize for any inconvenience.

Delayed reporting data and scheduled exportsResolved Sep 26, 2026 · 8h 5mResolved

The connection between the two data sources was resolved around 4:50 in the morning. Everything is working as expected now. --- [2026-09-26T02:52:57.290+02:00] (identified) A connection error between transctional database and reporting datalake in our data pipeline is preventing operational data from reaching our reporting environment. Affected: • Only reporting data is impacted. ChurnIQ dashboards are not refreshed since 00:30 CET • Scheduled 6-hourly data exports may be delayed Not affected: • Sign-up, checkout, payments, entitlements and the Core API are operating normally. Cleeng operational platform works normally. • All transactions continue to be recorded correctly in the platform Data is not being lost or corrupt. Once the connection is restored, the backlog will be processed and dashboards and exports will catch up automatically. Support team of the vendor that supports the pipeline is working to restore the connection.

Cleeng Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Cleeng incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 3 days with incidentsNov 9

Going further back: Cleeng uptime by month and every recorded Cleeng outage.

Live Cleeng Outage Reports

Problems reported by engineers using Cleeng. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Cleeng problems reported yet.

Something wrong with Cleeng on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Cleeng

Is Cleeng down? Cleeng reports live availability for 7 components at status.cleeng.com, among them API, Checkout & Other Widgets and ChurnIQ. Track Cleeng outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Cleeng uptime at 100.00%. Response times, incident history, and SLA tracking for Cleeng are available on the PulsAPI dashboard.

Cleeng Status FAQ

Is Cleeng down right now?

The verdict at the top of this page comes from the latest poll of the official Cleeng status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Cleeng is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Cleeng recovers.

How do I check Cleeng uptime history?

PulsAPI tracks Cleeng uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Cleeng changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Cleeng outages?

PulsAPI reads the official Cleeng status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Cleeng components?

Yes. PulsAPI monitors 7 individual Cleeng components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Cleeng goes down?

Yes. Create a free account and subscribe to Cleeng: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Cleeng to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Cleeng problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Cleeng?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Cleeng plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Cleeng with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services