Linode (Akamai) outage, 20 October 2026

Issue in creating new LKE Enterprise cluster across regions

Started
Resolved
20 Oct 2026, 21:42 UTC (after 9 h 13 min)
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

Is this still happening?

No. Linode (Akamai) marked this incident resolved on 20 Oct 2026, 21:42 UTC, 9 h 13 min after it began.

Right now: Linode (Akamai) reports degraded performance on some systems. (as of 26 Oct, 03:47 UTC) Live Linode (Akamai) status

Last update from Linode (Akamai)

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 compo...

21 Oct 2026, 15:49 UTC

Read the full incident on the official Linode (Akamai) status page

Similar Linode (Akamai) incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved

    Service Issue - Linode Kubernetes Engine

  2. , resolved after 2 h 11 min

    Service Issue - Linode Kubernetes Engine Enterprise (LKE-E)- IAD2 (Washington)

  3. , resolved after 1 h 37 min

    Service Issue - Linode Kubernetes Engine (IAD2)

Other recent Linode (Akamai) incidents

  1. Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)

  2. Connectivity Issue - Dallas Data Center (IPv6 Traffic to Google)

  3. Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities

  4. Customer Security Advisory: PHP Remote Code Execution Vulnerabilities

  5. Connectivity Issue - US-ORD

  6. (PwnEscape) Guest-to-Host KVM Escape [CVE-2026-99999]

  7. Maintenance - Akamai Cloud Login Service

  8. Service Issue - Cloud Manager and API

All recorded Linode (Akamai) incidents