On April 15, 2026, at 16:07 UTC, we identified an issue affecting the Linode platform, where multiple hosts began experiencing Linode VM guest orchestrator service failures. This issue disrupted new Linode jobs, Linode Kubernetes Engine (LKE) scaling, and related operations. Customers may have noticed slow or incomplete processing of compute-related tasks, including delays or failures when resizing Linodes or clusters, deploying new resources, updating Cloud Firewall rules, or making other changes through the Cloud Manager or API. These symptoms resulted in sluggish or partially completed operations during the issue timeframe.
The initial investigation traced the root cause to a problematic configuration file pertaining to the Linode VM guest orchestrator service. In response, we engaged the relevant subject matter experts to place temporary restrictive measures on fleet management services, preventing further spread of the issue. The team began reverting the problematic configuration change, and submitting code reversions to restore the correct configuration file. Between approximately 17:00 and 18:07 UTC, we worked to proactively fix impacted hosts and restore job processing.
At 18:07 UTC, mitigation efforts were complete, and all hosts alerting for failed statuses had been addressed. The reverted configuration changes were pushed out to remaining compute hosts, and change propagation was verified across each data center. Additional host state tests confirmed that all necessary updates took effect. At approximately 19:40 UTC, we resumed all normal internal operations and systems. Host status monitoring continued to ensure ongoing stability. At 20:21 UTC, no further issues were identified following monitoring, and the issue was considered resolved. Work now shifts to identifying long term corrective and preventive actions. This remains a work in progress.
This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.