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

- Impact (vendor’s label): none
- Status: postmortem
- Started: 2026-05-16 00:42 UTC · Resolved: 2026-05-16 01:43 UTC · Duration: 1.0 h
- Updates: 5 · Affected components: AP-West (Mumbai) Linode Kubernetes Engine, Linode Kubernetes Engine - AP-West (Mumbai) Linode Kubernetes Engine, GB-LON (London 2), Regions - GB-LON (London 2), FR-PAR (Paris), Regions - FR-PAR (Paris), Linode Kubernetes Engine - US-Southeast (Atlanta) Linode Kubernetes Engine, US-Southeast (Atlanta) Linode Kubernetes Engine, AU-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 Engine, Linode Kubernetes Engine - JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine, Regions - US-SEA (Seattle), US-SEA (Seattle), Linode Kubernetes Engine - NL-AMS (Amsterdam) Linode Kubernetes Engine, NL-AMS (Amsterdam) Linode Kubernetes Engine, IN-MAA (Chennai) Linode Kubernetes Engine, Linode Kubernetes Engine - IN-MAA (Chennai) Linode Kubernetes Engine, FR-PAR (Paris) Linode Kubernetes Engine, Linode Kubernetes Engine - FR-PAR (Paris) Linode Kubernetes Engine, AU-MEL (Melbourne) Linode Kubernetes Engine, Linode Kubernetes Engine - AU-MEL (Melbourne) Linode Kubernetes Engine, JP-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 Engine, Linode Kubernetes Engine - BR-GRU (São Paulo)  Linode Kubernetes Engine, AP-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 Engine, Linode Kubernetes Engine - GB-LON (London 2) Linode Kubernetes Engine, DE-HAM (Hamburg), Regions - DE-HAM (Hamburg), Linode Kubernetes Engine - US-East (Newark) Linode Kubernetes Engine, US-East (Newark) Linode Kubernetes Engine, EU-Central (Frankfurt), Regions - EU-Central (Frankfurt), DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, Linode Kubernetes Engine - DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, AP-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 Engine, US-ORD (Chicago) Linode Kubernetes Engine, EU-Central (Frankfurt) Linode Kubernetes Engine, Linode Kubernetes Engine - EU-Central (Frankfurt) Linode Kubernetes Engine, FR-PAR-2 (Paris 2), Regions - FR-PAR-2 (Paris 2), AP-Northeast (Tokyo 2) Linode Kubernetes Engine, Linode Kubernetes Engine - AP-Northeast (Tokyo 2) Linode Kubernetes Engine, Linode Kubernetes Engine - US-Central (Dallas) Linode Kubernetes Engine, US-Central (Dallas) Linode Kubernetes Engine, NZ-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 Engine, SE-STO (Stockholm) Linode Kubernetes Engine, Linode Kubernetes Engine - US-LAX (Los Angeles) Linode Kubernetes Engine, US-LAX (Los Angeles) Linode Kubernetes Engine, EU-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 Engine, Linode Kubernetes Engine - IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine, IT-MIL (Milan) Linode Kubernetes Engine, Linode Kubernetes Engine - IT-MIL (Milan) Linode Kubernetes Engine, AP-Southeast (Sydney) Linode Kubernetes Engine, Linode Kubernetes Engine - AP-Southeast (Sydney) Linode Kubernetes Engine, EU-West (London) Linode Kubernetes Engine, Linode Kubernetes Engine - EU-West (London) Linode Kubernetes Engine, ID-CGK (Jakarta) Linode Kubernetes Engine, Linode Kubernetes Engine - ID-CGK (Jakarta) Linode Kubernetes Engine, Regions - 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 Engine, Linode Kubernetes Engine - CA-Central (Toronto) Linode Kubernetes Engine, Regions - US-Southeast (Atlanta), US-Southeast (Atlanta), Linode Kubernetes Engine - US-SEA (Seattle) Linode Kubernetes Engine, US-SEA (Seattle) Linode Kubernetes Engine, Regions - 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 Engine, Linode Kubernetes Engine - ES-MAD (Madrid) Linode Kubernetes Engine, ES-MAD (Madrid), Regions - ES-MAD (Madrid), Linode Kubernetes Engine - SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, Regions - SG-SIN-2 (Singapore 2), SG-SIN-2 (Singapore 2), AP-South (Singapore) Linode Kubernetes Engine, Linode Kubernetes Engine - AP-South (Singapore) Linode Kubernetes Engine, Regions - US-IAD-2 (Washington 2), US-IAD-2 (Washington 2), Linode Kubernetes Engine - US-IAD (Washington) Linode Kubernetes Engine, US-IAD (Washington) Linode Kubernetes Engine, Linode Kubernetes Engine - US-West (Fremont) Linode Kubernetes Engine, US-West (Fremont) Linode Kubernetes Engine, JP-OSA (Osaka) Linode Kubernetes Engine, Linode Kubernetes Engine - JP-OSA (Osaka) Linode Kubernetes Engine, Linode Kubernetes Engine - US-MIA (Miami) Linode Kubernetes Engine, US-MIA (Miami) Linode Kubernetes Engine, AP-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)
- [Vendor status page: https://stspg.io/1ch8htmrzqgx](https://stspg.io/1ch8htmrzqgx)
- [Company: Linode (Akamai)](https://rewindex.com/company/linode-akamai.md)

## Timeline of updates

- **investigating** 2026-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.
- **investigating** 2026-05-16 01:06 UTC: We are continuing to investigate this issue.
- **identified** 2026-05-16 01:27 UTC: The issue has been identified and a fix has been implemented.
- **resolved** 2026-05-16 01:43 UTC: This incident has been resolved.
- **postmortem** 2026-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.


---
Canonical: https://rewindex.com/company/linode-akamai/incidents/dj3h400zlydn · Markdown: https://rewindex.com/company/linode-akamai/incidents/dj3h400zlydn.md · JSON: https://rewindex.com/api/v1/companies/linode-akamai/incidents/dj3h400zlydn · Generated 2026-10-18T09:59:43.242Z
