# Akamai Cloud (Linode): Service Issue - Linode Kubernetes Engine

- Provider: [Akamai Cloud (Linode)](https://outages.cc/linode.md)
- Type: Incident
- State: Resolved
- Worst impact: Operational
- Started: 2026-10-22 13:58 UTC
- Resolved: 2026-10-22 13:58 UTC (lasted 1 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/t6ft3ldxfwhw

## Updates from Akamai Cloud (Linode)

### postmortem, 2026-10-22 16:00 UTC

On October 22, 2026, starting around 11:10 UTC, a new Debian Kubernetes image was made available. The metadata for that image included malformed data, which resulted in Linode provisioning failures on LKE clusters due to validation errors. Akamai immediately began investigating the issue and working to correct it. We corrected the malformed data at 12:50 UTC on October 22, 2026 and service was restored. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

### resolved, 2026-10-22 13:58 UTC

Our team identified an issue affecting the Linode Kubernetes Engine (LKE). During the impact timeframe (~11:10-12:50 UTC), new worker nodes were unable to provision. We have been able to correct the issues affecting the LKE service and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.