Akamai Linode outage, October 2026: Issue in creating new LKE Enterprise cluster across regions

Akamai Linode reported and resolved an incident: Issue in creating new LKE Enterprise cluster across regions. It lasted 9.2 hours.

Resolved

From Akamai Linode's official status page, in their words.

What happened

Started
Resolved
Duration
9.2 hours
Impact
minor
Affected
US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont) Linode Kubernetes Engine, US-Southeast (Atlanta) Linode Kubernetes Engine, US-IAD (Washington) Linode Kubernetes Engine, US-ORD (Chicago) Linode Kubernetes Engine, CA-Central (Toronto) Linode Kubernetes Engine, EU-West (London) Linode Kubernetes Engine, EU-Central (Frankfurt) Linode Kubernetes Engine, FR-PAR (Paris) Linode Kubernetes Engine, AP-South (Singapore) Linode Kubernetes Engine, AP-Northeast (Tokyo 2) Linode Kubernetes Engine
  1. Investigating
  2. Identified
  3. Monitoringnot posted
  4. Resolved

Why it happened

Akamai Linode has not given a cause in its updates. We never guess one.

How it was resolved

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 informati

Akamai Linode's closing update

This incident on the Akamai Linode status page

Timeline

Oldest first, from the first notice to the resolution. From Akamai Linode's official status page, in their words.

  1. identified

    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.

  2. identified

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

  3. identified

    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.

  4. identified

    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.

  5. resolved

    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 open a Support ticket for assistance.

  6. postmortem

    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 informati

What this means for a business (and what to check now)

  • Retry anything that failed during the 9.2 hours.
  • Enter any payments, bookings or jobs you took another way.
  • If a deadline fell inside the window, keep this page as your record of the outage.

The full guide: what to do when a service you rely on is down

Other Akamai Linode incidents

Hear about the next Akamai Linode incident as it starts

Free email alerts when the official status changes, with what to do while it is down.

Watch Akamai Linode