rewindex

CompaniesLinode (Akamai)Incidents

Linode (Akamai): Issue in creating new LKE Enterprise cluster across regions

MinorStatus: postmortemeditedStarted Resolved (9.2 h)6 updatesstspg.io (opens in new tab)

Affected components: AP-West (Mumbai) Linode Kubernetes EngineLinode Kubernetes Engine - AP-West (Mumbai) Linode Kubernetes EngineLinode Kubernetes Engine - US-Southeast (Atlanta) Linode Kubernetes EngineUS-Southeast (Atlanta) Linode Kubernetes EngineJP-TYO-3 (Tokyo 3) Linode Kubernetes EngineLinode Kubernetes Engine - JP-TYO-3 (Tokyo 3) Linode Kubernetes EngineLinode Kubernetes Engine - NL-AMS (Amsterdam) Linode Kubernetes EngineNL-AMS (Amsterdam) Linode Kubernetes EngineIN-MAA (Chennai) Linode Kubernetes EngineLinode Kubernetes Engine - IN-MAA (Chennai) Linode Kubernetes EngineFR-PAR (Paris) Linode Kubernetes EngineLinode Kubernetes Engine - FR-PAR (Paris) Linode Kubernetes EngineAU-MEL (Melbourne) Linode Kubernetes EngineLinode Kubernetes Engine - AU-MEL (Melbourne) Linode Kubernetes EngineBR-GRU (São Paulo) Linode Kubernetes EngineLinode Kubernetes Engine - BR-GRU (São Paulo) Linode Kubernetes EngineGB-LON (London 2) Linode Kubernetes EngineLinode Kubernetes Engine - GB-LON (London 2) Linode Kubernetes EngineLinode Kubernetes Engine - US-East (Newark) Linode Kubernetes EngineUS-East (Newark) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineLinode Kubernetes Engine - DE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineLinode Kubernetes Engine - US-ORD (Chicago) Linode Kubernetes EngineUS-ORD (Chicago) Linode Kubernetes EngineEU-Central (Frankfurt) Linode Kubernetes EngineLinode Kubernetes Engine - EU-Central (Frankfurt) Linode Kubernetes EngineAP-Northeast (Tokyo 2) Linode Kubernetes EngineLinode Kubernetes Engine - AP-Northeast (Tokyo 2) Linode Kubernetes EngineLinode Kubernetes Engine - US-Central (Dallas) Linode Kubernetes EngineUS-Central (Dallas) Linode Kubernetes EngineLinode Kubernetes Engine - SE-STO (Stockholm) Linode Kubernetes EngineSE-STO (Stockholm) Linode Kubernetes EngineLinode Kubernetes Engine - US-LAX (Los Angeles) Linode Kubernetes EngineUS-LAX (Los Angeles) Linode Kubernetes EngineIN-BOM-2 (Mumbai 2) Linode Kubernetes EngineLinode Kubernetes Engine - IN-BOM-2 (Mumbai 2) Linode Kubernetes EngineIT-MIL (Milan) Linode Kubernetes EngineLinode Kubernetes Engine - IT-MIL (Milan) Linode Kubernetes EngineAP-Southeast (Sydney) Linode Kubernetes EngineLinode Kubernetes Engine - AP-Southeast (Sydney) Linode Kubernetes EngineEU-West (London) Linode Kubernetes EngineLinode Kubernetes Engine - EU-West (London) Linode Kubernetes EngineID-CGK (Jakarta) Linode Kubernetes EngineLinode Kubernetes Engine - ID-CGK (Jakarta) Linode Kubernetes EngineCA-Central (Toronto) Linode Kubernetes EngineLinode Kubernetes Engine - CA-Central (Toronto) Linode Kubernetes EngineLinode Kubernetes Engine - US-SEA (Seattle) Linode Kubernetes EngineUS-SEA (Seattle) Linode Kubernetes EngineES-MAD (Madrid) Linode Kubernetes EngineLinode Kubernetes Engine - ES-MAD (Madrid) Linode Kubernetes EngineLinode Kubernetes Engine - SG-SIN-2 (Singapore 2) Linode Kubernetes EngineSG-SIN-2 (Singapore 2) Linode Kubernetes EngineAP-South (Singapore) Linode Kubernetes EngineLinode Kubernetes Engine - AP-South (Singapore) Linode Kubernetes EngineLinode Kubernetes Engine - US-IAD (Washington) Linode Kubernetes EngineUS-IAD (Washington) Linode Kubernetes EngineLinode Kubernetes Engine - US-West (Fremont) Linode Kubernetes EngineUS-West (Fremont) Linode Kubernetes EngineJP-OSA (Osaka) Linode Kubernetes EngineLinode Kubernetes Engine - JP-OSA (Osaka) Linode Kubernetes EngineLinode Kubernetes Engine - US-MIA (Miami) Linode Kubernetes EngineUS-MIA (Miami) Linode Kubernetes Engine

Timeline of updates

  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 (opens in new tab) 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 information is reviewed.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Linode (Akamai), started 2026-10-20 12:29 UTC, resolved after 9.2 h, 6 update(s); edited after publishing.

Title
Issue in creating new LKE Enterprise cluster across regions
Vendor
Linode (Akamai)
Date
URL
https://rewindex.com/company/linode-akamai/incidents/jy76zdym8jb4

Linode (Akamai) profileRecent Linode (Akamai) incidentsAll outages on October 20, 2026Linode (Akamai) in October 2026MarkdownJSON