Linode incident

Service Issue - Linode Kubernetes Engine

Minor Resolved View vendor source →

Linode experienced a minor incident on November 18, 2025 affecting US-East (Newark) Linode Kubernetes Engine and US-Central (Dallas) Linode Kubernetes Engine and 1 more component, lasting 2h 56m. The incident has been resolved; the full update timeline is below.

Started
Nov 18, 2025, 07:02 AM UTC
Resolved
Nov 18, 2025, 09:58 AM UTC
Duration
2h 56m
Detected by Pingoru
Nov 18, 2025, 07:02 AM UTC

Affected components

US-East (Newark) Linode Kubernetes EngineUS-Central (Dallas) Linode Kubernetes EngineUS-West (Fremont) Linode Kubernetes EngineUS-Southeast (Atlanta) Linode Kubernetes EngineUS-IAD (Washington) Linode Kubernetes EngineUS-ORD (Chicago) Linode Kubernetes EngineCA-Central (Toronto) Linode Kubernetes EngineEU-West (London) Linode Kubernetes EngineEU-Central (Frankfurt) Linode Kubernetes EngineFR-PAR (Paris) Linode Kubernetes Engine

Update timeline

  1. investigating Nov 18, 2025, 07:02 AM UTC

    Our team is investigating an emerging issue affecting certain workloads on Linode Kubernetes Engine (LKE). A recent platform update may be contributing to unexpected resource-limit behavior for some customer pods, potentially leading to degraded performance or connection-related errors. We are actively assessing the impact and working toward a mitigation. Further updates will be shared as soon as more information is available.

  2. identified Nov 18, 2025, 07:59 AM UTC

    Our team has identified a patch fix that will correct the unexpected resource-limit behavior. We are currently reviewing the patch fix for release and deployment. Further updates will be shared as soon as more information is available.

  3. identified Nov 18, 2025, 09:14 AM UTC

    Our team is deploying the patch fix that was determined previously. Further updates will be shared post deploying the fix.

  4. resolved Nov 18, 2025, 09:58 AM UTC

    Our team deployed a fix and we haven’t observed any additional issues with the LKE service, and will now consider this incident resolved. We do recommend recycling the new nodes that were created post 4:00 UTC today. If you continue to experience problems, please open a Support ticket for assistance.