CloudLinux Status

Migration notice: xmlrpc.cln.cloudlinux.com

Monitoring - The host xmlrpc.cln.cloudlinux.com has been migrated to a new server (previously 107.155.119.76). This migration shouldn't cause any service disruption.

However, systems with custom entries in the /etc/hosts file may need a brief review to ensure smooth license validation and repository access. i.e.:

107.155.119.76 xmlrpc.cln.cloudlinux.com

If a custom entry like the one above exists, removing it will allow the system to automatically use the updated configuration.

Related article:
https://cloudlinux.zendesk.com/hc/en-us/articles/24012714742044-Issue-with-xmlrpc-cln-cloudlinux-com-old-server
Dec 03, 2025 - 18:47 UTC

About This Site

Welcome to CloudLinux status page. Here you can see if there are any ongoing issues with the CloudLinux network or other services.

CloudLinux OS Components Operational

Alt-PHP Operational

CageFS Operational

MySQL Governor Operational

EasyApache4 PHP packages Operational

CloudLinux Kernel Operational

Mod_lsapi Operational

PHP Selector Operational

Python Selector Operational

Ruby Selector Operational

Node.js Selector Operational

CloudLinux Network Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Feb 4, 2026

No incidents reported today.

Feb 3, 2026

No incidents reported.

Feb 2, 2026

No incidents reported.

Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026

No incidents reported.

Jan 29, 2026

No incidents reported.

Jan 28, 2026

No incidents reported.

Jan 27, 2026

KernelCare NFS Freeze on CL8/EL8

Resolved - A KernelCare adaptation of the CVE-2025-39697 NFS patch introduced a locking regression. Specifically, the patch caused the same spinlock to be acquired twice within a single execution path:

- nfs_page_group_lock
- nfs_page_group_sync_on_bit

This resulted in a deadlock that left kernel threads stuck in the D state. Once triggered, the patch could not be safely unloaded, and affected systems either froze indefinitely or rebooted due to hung task watchdogs.

Why this happened:

The issue was caused by a non-trivial adaptation of the upstream NFS CVE fix rather than a direct backport. This adaptation significantly altered the runtime execution flow and locking behavior in NFS write paths, introducing a double acquisition of the same spinlock under active NFS workloads.

The deadlock only manifested at runtime when NFS client activity was present after the live patch was applied, which made the issue difficult to detect through static code review alone.

We apologize for the inconvenience. A fixed patchset is now available across all feeds.

We also checked with our development team for alternatives to rebooting systems where NFS processes are already stuck. Unfortunately, a reboot remains the only viable recovery option in this scenario.

If no processes are present in the D state, patching should proceed normally.
Jan 27, 11:49 UTC

Monitoring - The fixed patches are now available in the main feed. Root Cause Analysis will be available soon.
Jan 26, 10:44 UTC

Identified - The core issue was identified and fixed. New patches are currently available in the testing feed. More updates will be provided soon.
Jan 23, 09:35 UTC

Update - We've established that enterprise users that are using ePortal - are not affected by this incident.
Jan 21, 12:21 UTC

Investigating - We have received at least 3 tickets about NFS-related issues in CL8.
We have blocked the most recent CL8 release, and we're going to do it for all recent EL8 distros.

We're currently trying to identify the full scope, so more release rollbacks may be required.
Please do not try to forcibly unapply patches, if possible.
Jan 21, 12:11 UTC

Jan 26, 2026

Jan 25, 2026

No incidents reported.

Jan 24, 2026

No incidents reported.

Jan 23, 2026

Jan 22, 2026

No incidents reported.

Jan 21, 2026