Companies / Linode (Akamai) / incidents

Linode (Akamai): Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]

Affected components: AP-West (Mumbai) Linode Kubernetes EngineLinode Kubernetes Engine - AP-West (Mumbai) Linode Kubernetes EngineGB-LON (London 2)Regions - GB-LON (London 2)FR-PAR (Paris)Regions - FR-PAR (Paris)Linode Kubernetes Engine - US-Southeast (Atlanta) Linode Kubernetes EngineUS-Southeast (Atlanta) Linode Kubernetes EngineAU-MEL (Melbourne)Regions - AU-MEL (Melbourne)Regions - US-DEN (Denver)US-DEN (Denver)CL-SCL (Santiago)Regions - CL-SCL (Santiago)Regions - US-ORD (Chicago)US-ORD (Chicago)Regions - US-HOU (Houston)US-HOU (Houston)Regions - SE-STO (Stockholm)SE-STO (Stockholm)JP-TYO-3 (Tokyo 3) Linode Kubernetes EngineLinode Kubernetes Engine - JP-TYO-3 (Tokyo 3) Linode Kubernetes EngineRegions - US-SEA (Seattle)US-SEA (Seattle)Linode Kubernetes Engine - NL-AMS (Amsterdam) Linode Kubernetes EngineNL-AMS (Amsterdam) Linode Kubernetes EngineIN-MAA (Chennai) Linode Kubernetes EngineLinode Kubernetes Engine - IN-MAA (Chennai) Linode Kubernetes EngineFR-PAR (Paris) Linode Kubernetes EngineLinode Kubernetes Engine - FR-PAR (Paris) Linode Kubernetes EngineAU-MEL (Melbourne) Linode Kubernetes EngineLinode Kubernetes Engine - AU-MEL (Melbourne) Linode Kubernetes EngineJP-OSA (Osaka)Regions - JP-OSA (Osaka)Regions - US-LAX (Los Angeles)US-LAX (Los Angeles)NL-AMS (Amsterdam)Regions - NL-AMS (Amsterdam)IN-BOM-2 (Mumbai 2)Regions - IN-BOM-2 (Mumbai 2)BR-GRU (São Paulo) Linode Kubernetes EngineLinode Kubernetes Engine - BR-GRU (São Paulo) Linode Kubernetes EngineAP-Northeast-2 (Tokyo 2)Regions - AP-Northeast-2 (Tokyo 2)IT-MIL (Milan)Regions - IT-MIL (Milan)CO-BOG (Bogota)Regions - CO-BOG (Bogota)GB-LON (London 2) Linode Kubernetes EngineLinode Kubernetes Engine - GB-LON (London 2) Linode Kubernetes EngineDE-HAM (Hamburg)Regions - DE-HAM (Hamburg)Linode Kubernetes Engine - US-East (Newark) Linode Kubernetes EngineUS-East (Newark) Linode Kubernetes EngineEU-Central (Frankfurt)Regions - EU-Central (Frankfurt)DE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineLinode Kubernetes Engine - DE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineAP-West (Mumbai)Regions - AP-West (Mumbai)JP-TYO-3 (Tokyo 3)Regions - JP-TYO-3 (Tokyo 3)Linode Kubernetes Engine - US-ORD (Chicago) Linode Kubernetes EngineUS-ORD (Chicago) Linode Kubernetes EngineEU-Central (Frankfurt) Linode Kubernetes EngineLinode Kubernetes Engine - EU-Central (Frankfurt) Linode Kubernetes EngineFR-PAR-2 (Paris 2)Regions - FR-PAR-2 (Paris 2)AP-Northeast (Tokyo 2) Linode Kubernetes EngineLinode Kubernetes Engine - AP-Northeast (Tokyo 2) Linode Kubernetes EngineLinode Kubernetes Engine - US-Central (Dallas) Linode Kubernetes EngineUS-Central (Dallas) Linode Kubernetes EngineNZ-AKL (Auckland)Regions - NZ-AKL (Auckland)Regions - US-IAD (Washington)US-IAD (Washington)DE-FRA-2 (Frankfurt 2)Regions - DE-FRA-2 (Frankfurt 2)Linode Kubernetes Engine - SE-STO (Stockholm) Linode Kubernetes EngineSE-STO (Stockholm) Linode Kubernetes EngineLinode Kubernetes Engine - US-LAX (Los Angeles) Linode Kubernetes EngineUS-LAX (Los Angeles) Linode Kubernetes EngineEU-West (London)Regions - EU-West (London)IN-MAA (Chennai)Regions - IN-MAA (Chennai)ID-CGK (Jakarta)Regions - ID-CGK (Jakarta)MX-QRO (Queretaro)Regions - MX-QRO (Queretaro)AP-Southeast (Sydney)Regions - AP-Southeast (Sydney)IN-BOM-2 (Mumbai 2) Linode Kubernetes EngineLinode Kubernetes Engine - IN-BOM-2 (Mumbai 2) Linode Kubernetes EngineIT-MIL (Milan) Linode Kubernetes EngineLinode Kubernetes Engine - IT-MIL (Milan) Linode Kubernetes EngineAP-Southeast (Sydney) Linode Kubernetes EngineLinode Kubernetes Engine - AP-Southeast (Sydney) Linode Kubernetes EngineEU-West (London) Linode Kubernetes EngineLinode Kubernetes Engine - EU-West (London) Linode Kubernetes EngineID-CGK (Jakarta) Linode Kubernetes EngineLinode Kubernetes Engine - ID-CGK (Jakarta) Linode Kubernetes EngineRegions - US-MIA (Miami)US-MIA (Miami)CA-Central (Toronto)Regions - CA-Central (Toronto)FR-MRS (Marseille)Regions - FR-MRS (Marseille)Regions - US-Central (Dallas)US-Central (Dallas)CA-Central (Toronto) Linode Kubernetes EngineLinode Kubernetes Engine - CA-Central (Toronto) Linode Kubernetes EngineRegions - US-Southeast (Atlanta)US-Southeast (Atlanta)Linode Kubernetes Engine - US-SEA (Seattle) Linode Kubernetes EngineUS-SEA (Seattle) Linode Kubernetes EngineRegions - ZA-JNB (Johannesburg)ZA-JNB (Johannesburg)Regions - US-West (Fremont)US-West (Fremont)Regions - US-East (Newark)US-East (Newark)ES-MAD (Madrid) Linode Kubernetes EngineLinode Kubernetes Engine - ES-MAD (Madrid) Linode Kubernetes EngineES-MAD (Madrid)Regions - ES-MAD (Madrid)Linode Kubernetes Engine - SG-SIN-2 (Singapore 2) Linode Kubernetes EngineSG-SIN-2 (Singapore 2) Linode Kubernetes EngineRegions - SG-SIN-2 (Singapore 2)SG-SIN-2 (Singapore 2)AP-South (Singapore) Linode Kubernetes EngineLinode Kubernetes Engine - AP-South (Singapore) Linode Kubernetes EngineRegions - US-IAD-2 (Washington 2)US-IAD-2 (Washington 2)Linode Kubernetes Engine - US-IAD (Washington) Linode Kubernetes EngineUS-IAD (Washington) Linode Kubernetes EngineLinode Kubernetes Engine - US-West (Fremont) Linode Kubernetes EngineUS-West (Fremont) Linode Kubernetes EngineJP-OSA (Osaka) Linode Kubernetes EngineLinode Kubernetes Engine - JP-OSA (Osaka) Linode Kubernetes EngineLinode Kubernetes Engine - US-MIA (Miami) Linode Kubernetes EngineUS-MIA (Miami) Linode Kubernetes EngineAP-South (Singapore)Regions - AP-South (Singapore)MY-KUL (Kuala Lumpur)Regions - MY-KUL (Kuala Lumpur)BR-GRU (São Paulo)Regions - BR-GRU (São Paulo)

Timeline of updates

1. investigating2026-05-16 00:42 UTC

   Our team is investigating an emerging service issue affecting Linodes booting across all regions. We will share additional updates as we have more information.

2. investigating2026-05-16 01:06 UTC

   We are continuing to investigate this issue.

3. identified2026-05-16 01:27 UTC

   The issue has been identified and a fix has been implemented.

4. resolved2026-05-16 01:43 UTC

   This incident has been resolved.

5. postmortem2026-05-20 19:15 UTC

   On May 15, 2026, at 18:18 UTC, we identified an issue impacting the deployment of Linodes that relied on StackScripts \(including all newly created Linode Kubernetes Engine \(LKE\) and \(LKE-E\) nodes\), resulting in deployment failures. These deployment failures resulted in Linodes created with StackScripts to be unbootable and LKE autoscaling or recycling activity to fail. Subject matter experts determined that the cause of the issue was the removal of a credential parser during a recent update on compute hosts. This credential parser is used in the process of decoding StackScripts and its removal caused Linode deployments relying on StackScripts to fail. With the issue identified, we began to test a rollback at 01:10 UTC on May 16, 2026  and a reduction in failures was noted at 01:20 UTC. We mitigated the broader customer impact by  01:30 UTC on May 16, 2026. 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.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Linode (Akamai) profile · Recent Linode (Akamai) incidents · Markdown · JSON