All Systems Operational.
All services are reporting healthy across every core.
Aggregated across 10 monitored services across all cores.
Regional Health.
Real-time availability across every Cycle core. Each core operates independently with isolated control planes, DNS, build systems, and application instances.
north america
Cycle's auth service provides user authentication and access to the portal and APIs.
The compute proxy service routes requests between the central platform and client servers.
Cycle's console service. Provides SSH access to containers in a safe and centralized manner.
Cycle's Domain Name Service. Provides routing for domains pointed to Cycle's nameservers.
Cycle's factory service builds container images during stack imports.
Job scheduling and delegator for Cycle services.
Monitors server and environment metrics, and does public ping uptime monitoring for load balancers
Communication mesh for Cycle's core services.
The portal provides a user friendly interface for managing containers and infrastructure.
Cycle's public API enables both users and the portal to interact with the platform.
Recent Activity.
Maintenance windows and incident reports from the last 30 days.
Latest Kernel Vulnerability Patched In Cycle OS
Another major kernel vulnerability, known as "Dirty Frag" (CVE-2026-43284) was announced hours ago before the embargo had been lifted. Shortly after, a new kernel patch was released that resolved it. About 30 minutes later, CycleOS was patched and now includes protection against this vulnerability. This vulnerability, similar to the 'Copy Fail' vulnerability from a few days ago, allows an unprivileged user to gain root privileges on a host, including elevated access breaking out of a container. Cycle's core infrastructure has been upgraded, and our factories and other services are secured. As before, we strongly urge customers to restart their nodes to get the patched OS build. We've added a new option in our latest release this morning for provider servers, 'Soft Restart'. Instead of using the provider API, it issues a reboot via CycleOS and is a safer option than a 'hard reboot', while still ensuring you get the latest OS build. As always, please contact us via Slack if you have any questions about the vulnerability, our how to safely reboot your nodes.
Core Infrastructure Update - Factories Will Restart
In light of several recent kernel vulnerabilities, such as the permission-elevating 'copy fail' (CVE-2026-31431) vulnerability, we've patched CycleOS to the latest Linux kernel, 6.12.85, released on April 30th. We will begin updating our core infrastructure, including our factory services, which will be temporarily offline for a few minutes. This announcement will be up for a couple days, but all of our core infrastructure will be up to date on May 2nd. We strongly urge customers to upgrade to the latest version of CycleOS as soon as possible. This can be done by restarting your server via the Cycle UI by going to Servers > Select the server > Settings Tab > Click the 'Advanced' dropdown in the 'Controls' panel on the right side, and click 'Restart Server'. This will stop all containers, restart the node, and bring all containers back online. To minimize or avoid downtime, ensure that any servers that can run in High Availability are doing so, and restart one server at a time. If you have any questions, please reach out to our team via Slack or support@cycle.io. Thank you!
As of 14:20 GMT, all Cycle core infrastructure has been patched, and image/stack builds should be resuming. We don't expect any further disruption to service at this time.