On March 9, 2026, at 20:02 UTC, we identified an issue impacting Dedicated CPU plan Linodes, resulting in boot failures and resource allocation errors across multiple data centers. The problem was first reported by a customer who was unable to boot a newly provisioned Dedicated CPU Linode. We began investigating the issue on March 10, 2026, and escalated it internally on March 17, 2026, after receiving additional reports. By April 14, 2026, the incident had affected 35 Dedicated CPU plan hosts across seven data centers, including Amsterdam, London, Madrid, Atlanta, Chicago, Seattle, Washington, D.C., and Osaka. The issue was traced to a known software defect that caused validation failures during the boot process, leading to insufficient resource errors and preventing fallback allocations.
Subject matter experts identified a missing configuration file as the root cause of the Dedicated Linode plan issues. To address this, we implemented a workaround script and began developing a long-term platform fix. We also introduced proactive alerting to detect similar issues in the future and updated our runbook with clear mitigation steps. Temporary monitoring will remain in place until the permanent fix is deployed. The permanent platform fix is scheduled for release by the end of May as part of our regular software update cycle.
With the workaround script, runbook updates, and proactive alerting in place, we mitigated the broader customer impact by 14:42 UTC on April 16, 2026. If customers experience similar issues before the May platform release, we encourage them to contact Akamai Compute Support for assistance.
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.