Issue in creating new LKE Enterprise cluster across regions

Summary

Issue in creating new LKE Enterprise cluster across regions

Starting October 17, 2026, customers were unable to create new Linode Kubernetes Engine-Enterprise \(LKE-E\) clusters globally. The impact was limited to newly provisioned LKE-E clusters, while the existing clusters, ongoing customer workloads, and cluster scaling remained fully functional and were unaffected throughout the event. Investigation revealed that the impact occurred after Linode Virtual Private Cloud \(VPC\) subnet IDs crossed 1,000,000 \(one million\), following growth on October 17, 2026. Due to a software logic flaw, the Cloud Controller Manager parsed these 7-digit IDs into scientific notation instead of raw integers, rendering the IDs invalid and causing required core components to remain pending on newly created clusters. To mitigate the issue, Akamai deployed a fix to enforce strict integer formatting and patched existing custom resources to restore the affected clusters. Akamai’s internal testing confirmed that the newly provisioned test clusters were fully operational. With the successful testing, Akamai deployed the fix across the platform, and the impact was considered mitigated at around 19:49 UTC on October 20, 2026. Akamai is working on the root cause and will take appropriate preventive actions. We apologize for the impact and thank you for your patience and continued support. This summary reflects our current understanding of the incident based on available details. Our investigation remains ongoing, and findings may be updated as further information is reviewed.

• Started

  Oct 20, 2026 · 12:29 PM

• Resolved

  Oct 20, 2026 · 9:42 PM

• Duration

  9h 13m

• Severity

  Minor

• ◆

  Identified

  Oct 20 · 12:29 PM Linode

  We are currently investigating an issue affecting the provisioning of new LKE Enterprise (LKE-E) clusters across all regions. Affected clusters may experience nodes that successfully reach a "Ready" state, but system critical components may fail to start properly, preventing workloads from running.

• ◆

  Identified

  Oct 20 · 12:33 PM Linode

  We are continuing to work on a fix for this issue.

• ◆

  Identified

  Oct 20 · 12:34 PM Linode

  We are currently investigating an issue affecting the provisioning of new LKE Enterprise (LKE-E) clusters across all regions. Affected clusters may experience nodes that successfully reach a "Ready" state, but system critical components may fail to start properly, preventing workloads from running.

• ◆

  Identified

  Oct 20 · 2:06 PM Linode

  Our team has identified the issue affecting the LKE Enterprise service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

• ✓

  Resolved

  Oct 20 · 9:42 PM Linode

  We haven’t observed any additional issues with the LKE service, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

• ✓

  Postmortem

  Oct 21 · 3:49 PM Linode

  Starting October 17, 2026, customers were unable to create new Linode Kubernetes Engine-Enterprise \(LKE-E\) clusters globally. The impact was limited to newly provisioned LKE-E clusters, while the existing clusters, ongoing customer workloads, and cluster scaling remained fully functional and were unaffected throughout the event. Investigation revealed that the impact occurred after Linode Virtual Private Cloud \(VPC\) subnet IDs crossed 1,000,000 \(one million\), following growth on October 17, 2026. Due to a software logic flaw, the Cloud Controller Manager parsed these 7-digit IDs into scientific notation instead of raw integers, rendering the IDs invalid and causing required core components to remain pending on newly created clusters. To mitigate the issue, Akamai deployed a fix to enforce strict integer formatting and patched existing custom resources to restore the affected clusters. Akamai’s internal testing confirmed that the newly provisioned test clusters were fully operational. With the successful testing, Akamai deployed the fix across the platform, and the impact was considered mitigated at around 19:49 UTC on October 20, 2026. Akamai is working on the root cause and will take appropriate preventive actions. We apologize for the impact and thank you for your patience and continued support. This summary reflects our current understanding of the incident based on available details. Our investigation remains ongoing, and findings may be updated as further information is reviewed.