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

- Provider: [Akamai Cloud (Linode)](https://outages.cc/linode.md)
- Type: Incident
- State: Resolved
- Worst impact: Degraded performance
- Started: 2026-10-20 12:29 UTC
- Resolved: 2026-10-20 21:42 UTC (lasted 9 h 14 min)
- Components: 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, AP-West (Mumbai) Linode Kubernetes Engine, AP-Southeast (Sydney) Linode Kubernetes Engine, SE-STO (Stockholm) Linode Kubernetes Engine, US-SEA (Seattle) Linode Kubernetes Engine, JP-OSA (Osaka) Linode Kubernetes Engine, IN-MAA (Chennai) Linode Kubernetes Engine, ID-CGK (Jakarta) Linode Kubernetes Engine, BR-GRU (São Paulo)  Linode Kubernetes Engine, NL-AMS (Amsterdam) Linode Kubernetes Engine, ES-MAD (Madrid) Linode Kubernetes Engine, IT-MIL (Milan) Linode Kubernetes Engine, US-MIA (Miami) Linode Kubernetes Engine, US-LAX (Los Angeles) Linode Kubernetes Engine, GB-LON (London 2) Linode Kubernetes Engine, AU-MEL (Melbourne) Linode Kubernetes Engine, IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine, DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine
- Official update: https://stspg.io/10j6p4d7fwn5

## Updates from Akamai Cloud (Linode)

### postmortem, 2026-10-21 15:49 UTC

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 operatio

### resolved, 2026-10-20 21:42 UTC

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.

### identified, 2026-10-20 14:06 UTC

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.

### identified, 2026-10-20 12:34 UTC

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, 2026-10-20 12:33 UTC

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

### identified, 2026-10-20 12:29 UTC

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.