Linode Status

Postmortem: 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.

Resolved: We haven't observed any additional issues with the Cloud Manager or API, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Monitoring: At this time we have been able to correct the issue affecting the Cloud Manager and API. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].

Identified: We are continuing to implement a fix, and we will provide an update as soon as the solution is in place.

Identified: Our team has identified the issue affecting the Cloud Manager and API. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. During this time, customers may be unable to create new Linodes, make changes to Cloud Firewalls, initiate migrations or resize operations. LKE autoscaling may also be delayed during this time.

Postmortem: 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.

Resolved: We haven't observed any additional issues with the Dedicated CPU offering, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Identified: We have identified a fix for the issue affecting the Dedicated CPU offering and are currently testing it. We expect to include the fix in the next software release that is expected to happen by the end of May. Our investigation shows that approximately 0.2% of hosts were impacted by this issue. In the meantime, a workaround is available by contacting support. We will provide additional updates as we approach the deployment date.

Identified: Our team has identified the issue affecting the Dedicated CPU offering. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is investigating a service issue that affects the Dedicated CPU offering. Some users may experience failed Linode boots, errors related to insufficient resource allocation, unsuccessful migrations of Dedicated CPU plans or scaling of LKE clusters, and difficulty deploying or scaling workloads that require Dedicated CPU resources. We will share additional updates as we have more information.

Postmortem: 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.

Resolved: We haven't observed any additional issues with the Dedicated CPU offering, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Identified: We have identified a fix for the issue affecting the Dedicated CPU offering and are currently testing it. We expect to include the fix in the next software release that is expected to happen by the end of May. Our investigation shows that approximately 0.2% of hosts were impacted by this issue. In the meantime, a workaround is available by contacting support. We will provide additional updates as we approach the deployment date.

Identified: Our team has identified the issue affecting the Dedicated CPU offering. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is investigating a service issue that affects the Dedicated CPU offering. Some users may experience failed Linode boots, errors related to insufficient resource allocation, unsuccessful migrations of Dedicated CPU plans or scaling of LKE clusters, and difficulty deploying or scaling workloads that require Dedicated CPU resources. We will share additional updates as we have more information.

Postmortem: 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.

Resolved: We haven't observed any additional issues with the Dedicated CPU offering, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Identified: We have identified a fix for the issue affecting the Dedicated CPU offering and are currently testing it. We expect to include the fix in the next software release that is expected to happen by the end of May. Our investigation shows that approximately 0.2% of hosts were impacted by this issue. In the meantime, a workaround is available by contacting support. We will provide additional updates as we approach the deployment date.

Identified: Our team has identified the issue affecting the Dedicated CPU offering. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is investigating a service issue that affects the Dedicated CPU offering. Some users may experience failed Linode boots, errors related to insufficient resource allocation, unsuccessful migrations of Dedicated CPU plans or scaling of LKE clusters, and difficulty deploying or scaling workloads that require Dedicated CPU resources. We will share additional updates as we have more information.

Postmortem: 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.

Resolved: We haven't observed any additional issues with the Dedicated CPU offering, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Identified: We have identified a fix for the issue affecting the Dedicated CPU offering and are currently testing it. We expect to include the fix in the next software release that is expected to happen by the end of May. Our investigation shows that approximately 0.2% of hosts were impacted by this issue. In the meantime, a workaround is available by contacting support. We will provide additional updates as we approach the deployment date.

Identified: Our team has identified the issue affecting the Dedicated CPU offering. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is investigating a service issue that affects the Dedicated CPU offering. Some users may experience failed Linode boots, errors related to insufficient resource allocation, unsuccessful migrations of Dedicated CPU plans or scaling of LKE clusters, and difficulty deploying or scaling workloads that require Dedicated CPU resources. We will share additional updates as we have more information.

Postmortem: 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.

Resolved: We haven't observed any additional issues with the Dedicated CPU offering, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Identified: We have identified a fix for the issue affecting the Dedicated CPU offering and are currently testing it. We expect to include the fix in the next software release that is expected to happen by the end of May. Our investigation shows that approximately 0.2% of hosts were impacted by this issue. In the meantime, a workaround is available by contacting support. We will provide additional updates as we approach the deployment date.

Identified: Our team has identified the issue affecting the Dedicated CPU offering. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is investigating a service issue that affects the Dedicated CPU offering. Some users may experience failed Linode boots, errors related to insufficient resource allocation, unsuccessful migrations of Dedicated CPU plans or scaling of LKE clusters, and difficulty deploying or scaling workloads that require Dedicated CPU resources. We will share additional updates as we have more information.

Postmortem: 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.

Resolved: We haven't observed any additional issues with the Dedicated CPU offering, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Identified: We have identified a fix for the issue affecting the Dedicated CPU offering and are currently testing it. We expect to include the fix in the next software release that is expected to happen by the end of May. Our investigation shows that approximately 0.2% of hosts were impacted by this issue. In the meantime, a workaround is available by contacting support. We will provide additional updates as we approach the deployment date.

Identified: Our team has identified the issue affecting the Dedicated CPU offering. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is investigating a service issue that affects the Dedicated CPU offering. Some users may experience failed Linode boots, errors related to insufficient resource allocation, unsuccessful migrations of Dedicated CPU plans or scaling of LKE clusters, and difficulty deploying or scaling workloads that require Dedicated CPU resources. We will share additional updates as we have more information.

Postmortem: 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.

Resolved: We haven't observed any additional issues with the Dedicated CPU offering, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Identified: We have identified a fix for the issue affecting the Dedicated CPU offering and are currently testing it. We expect to include the fix in the next software release that is expected to happen by the end of May. Our investigation shows that approximately 0.2% of hosts were impacted by this issue. In the meantime, a workaround is available by contacting support. We will provide additional updates as we approach the deployment date.

Identified: Our team has identified the issue affecting the Dedicated CPU offering. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is investigating a service issue that affects the Dedicated CPU offering. Some users may experience failed Linode boots, errors related to insufficient resource allocation, unsuccessful migrations of Dedicated CPU plans or scaling of LKE clusters, and difficulty deploying or scaling workloads that require Dedicated CPU resources. We will share additional updates as we have more information.

Postmortem: 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.

Resolved: We haven't observed any additional issues with the Dedicated CPU offering, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Identified: We have identified a fix for the issue affecting the Dedicated CPU offering and are currently testing it. We expect to include the fix in the next software release that is expected to happen by the end of May. Our investigation shows that approximately 0.2% of hosts were impacted by this issue. In the meantime, a workaround is available by contacting support. We will provide additional updates as we approach the deployment date.

Identified: Our team has identified the issue affecting the Dedicated CPU offering. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: Our team is investigating a service issue that affects the Dedicated CPU offering. Some users may experience failed Linode boots, errors related to insufficient resource allocation, unsuccessful migrations of Dedicated CPU plans or scaling of LKE clusters, and difficulty deploying or scaling workloads that require Dedicated CPU resources. We will share additional updates as we have more information.

Postmortem: On April 20, 2026, approximately between 11:05 UTC and 13:10 UTC, Frankfurt (DE-FRA-2) data center experienced degraded connectivity and performance issues for Compute services, including Linode and Object Storage. During this time, customers in the Frankfurt region may have experienced packet loss or connectivity issues

Initially, we suspected ongoing power maintenance at the datacenter to be the cause; however, this was later determined not to be impacting. Further investigation revealed the connectivity issues were affecting certain compute hosts within the site, as well as host job completion issues site wide. Akamai identified incorrect route advertisements coming from a host within the datacenter, which contributed to the disruption. The affected host was identified and isolated, which mitigated the issue and restored service stability.

We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence.

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.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are continuing to investigate this issue.

Investigating: Our team is investigating an emerging service issue impacting connectivity in Frankfurt (DE-FRA-2). We will share additional updates as we have more information.