Issue in creating new LKE Enterprise cluster across regions.
View the provider incident record →Current answer
Linode experienced a minor incident: Issue in creating new LKE Enterprise cluster across regions.. The provider currently marks this incident Identified.
Looking for an update now? Check the current status, or follow Linode for future changes.
Incident Lifecycle
Affected 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
Incident Timeline
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.
Oct 20, 2026 at 12:34 PM UTC
Identified
We are continuing to work on a fix for this issue.
Oct 20, 2026 at 12:33 PM UTC
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.
Oct 20, 2026 at 12:29 PM UTC
Was your business affected by this Linode outage?
Follow Linode and route available status alerts to email or a team channel.