What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Linode now? Check the current status

Affected services

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

Updates (5)

May 20, 2026, 07:15 PM
Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]
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
Linode ↗
May 16, 2026, 01:43 AM
Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]
This incident has been resolved.
Linode ↗
May 16, 2026, 01:27 AM
Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]
The issue has been identified and a fix has been implemented.
Linode ↗
May 16, 2026, 01:06 AM
Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]
We are continuing to investigate this issue.
Linode ↗
May 16, 2026, 12:42 AM
Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]
Our team is investigating an emerging service issue affecting Linodes booting across all regions. We will share additional updates as we have more information.
Linode ↗

What to do next

Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
Watch the provider going forward. Follow Linode's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.