Linode incident
Issue in creating new LKE Enterprise cluster across regions.
Linode experienced a minor incident on October 20, 2026 affecting US-East (Newark) Linode Kubernetes Engine and US-Central (Dallas) Linode Kubernetes Engine and 1 more component, lasting 9h 13m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 20, 2026, 12:29 PM 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 Oct 20, 2026, 12:33 PM UTC
We are continuing to work on a fix for this issue.
- identified Oct 20, 2026, 12:34 PM 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 Oct 20, 2026, 02:06 PM 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.
- resolved Oct 20, 2026, 09:42 PM 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.