Cycle is Online.
As of , the platform is reporting healthy and all services are available.
- Console
- Portal
- Compute Proxy
- DNS
- Auth
- Nexus
- Public API
- Manager
- Factory
- Monitor
Active Announcements
- No Active Announcements
Past Announcements
- No Past Announcements
Changelog
- 2026.02.03.5
More Capabilities with Storage, Better Pipeline Validation, and More Reliable Metrics.
This release brings meaningful improvements across compute, storage, and automation. Volumes can now be added or removed from virtual machines after create. iSCSI startup behavior has been improved and is far more reliable, and pipeline variables now how additional validation on syntax. Several fixes are also a part of the update, including, a race condition in bare metal provisioning, CPU/RAM and volume usage reporting, and metrics accuracy across the board.
- added
Add/Remove Virtual Machine Volumes Post-Creation
Volumes can now be added to, or removed from, virtual machines after the virtual machine has been created.
- added
Environment Limited Container Networking
Containers can now be configured with the environment-limited network setting. This allows for containers to communicate over the private network through the load balancer instead of using the discovery service directly.
- fixed
Bare Metal Provision Auth Failure
A race condition existed for the provisioning of bare metal servers when one would attempt to checkin prior to full authorization by the platform. Additionally, a newly provisioned node that fails to authorize, at start time, will now reattempt authorization up to 5 times before a reboot is required.
- fixed
iSCSI Daemon
Under some conditions, the compute service wouldn't start the iSCSI daemon when needed. This has been resolved.
- added
Pipeline Variable Validation
In pipelines, some user-supplied variables weren't being properly validated, syntactically, causing issues between pipeline steps.
- fixed
CPU/RAM Usage Metrics
The newly introduced 'Peak' metric in the portal had a calculation error that would lead to reported usage being higher than it was.
- fixed
Volume Usage
Usage calculations for local block devices are correctly surfaced following an issue in the latest release.
- added
Safer DNS Routing
Discovery will now automatically rewrite publicly resolved IPs to private IPs for any public traffic that would've left, and returned, to the same environment. In other words, if you were attempting to send traffic to "foo.bar.com" but the container serving "foo.bar.com" was a sibling container in the same environment, Cycle's discovery service will now resolve to the private IP of the load balancer -- preventing the traffic from ever leaving the private network.
- 2026.01.21.2
Storage, Routing, and Observability Improvements
This update ships a large batch of improvements, new features, and a few fixes. We’ve added support for zstd-compressed images, which means the new Docker hardened images are now building and running as expected. The SAN integration released earlier this year has been rebuilt on top of our External Volumes abstraction, making it more flexible and easier to extend. Readiness can now be defined directly on a container and will continue to evolve into a more powerful way to manage instance state at a granular level. We’ve also introduced hub-level encryption to strengthen security, fixed external volume usage reporting, added support for marking infrastructure clusters as essential or non-essential to keep dashboards focused, and simplified path-based routing through linked records.
- improvement
Load Balancer Routes
The Cycle V1 LB is now able to adjust to routing changes more efficiently, especially within environments that have 25+ public containers. In testing, this lead to a 90% reduction in most sync times.
- added
Path Matching on LINKED Records
Paths can now be attached directly to LINKED records to indicate that they should only route to the specified container when the inbound request is to that specific path. Using this pattern significantly reduces complexity, and the risk of misconfiguration, compared to creating router-specific path matching rules. Additionally, this method enables the use of deployment tags.
- added
Metrics and Events On-Disk Buffer
The compute service now creates an on-disk buffer that will be used when an event/metric cannot be sent to the platform (network outage, high load, etc). On connection reestablishment, the queued events/metrics will be submitted.
- added
Support ztsd Compressed Images
Images that have zstd compressed layers are now supported by Cycle's factory.
- improvement
Rebuilt SAN Integration
The SAN support we launched in Q3 2025 has been rebuilt into our new storage abstraction, External Volumes.
- added
Metrics / Events Egress
Per environment, events and metrics can now be pushed to an external endpoint.
- added
Readiness Check
In a container config, a readiness check can now be specified. Initially, this will just attach a ready state. A future version will utilize this for load balancer routing, DNS, and more.
- security
Hub Level Encryption
Behind the scenes, we've adopted a new security process where all configs, variables, and metadata are encrypted on a per-hub basis as opposed to a per-core basis.
- improvement
Server Deploy Modal
Improved the process of deploying infrastructure in the portal.
- added
Uptime Chart
Added a new chart to environment dashboards to show successful pings of the environment load balancer. This is done by a service outside of your infrastructure, showing that your load balancer is publicly accessible.
- fixed
External Volume Usage
External volumes (SAN, Ceph) now properly report their usage.
- added
Non-Essential Clusters
Clusters can now be marked as 'non-essential', removing them from metrics on the new dashboards. This is useful for keeping development or staging clusters from presenting on critical dashboards.
- added
Resource Level Dashboards
New dashboards have been added across the portal, showing a birds eye view of important information for environments, images, pipelines and more.
- added
External Volume Scanning
It's now possible to scan for Ceph or SAN volumes that are present on the same network after configuring an external volume integration. External volumes will be automatically created upon discovery and available for attachment to containers and VMs.
- added
DNS Record Modal
We've added an improved UI for managing DNS records
- added
Priority Events Chart
Surfaces a high-level view of priority events on the environments, clusters, and servers dashboard.
- improvement
Vultr Bare Metal OOB Support
Servers deployed on Vultr now automatically use out-of-band (OOB) networks when supported by the underlying bare metal hardware.