rewindex

CompaniesLinode (Akamai)Incidents

Linode (Akamai): Service Issue - Linode Kubernetes Engine

No impact listedStatus: postmortemeditedStarted Resolved (0 min)2 updatesstatus.linode.com (opens in new tab)

Affected components: AP-Northeast - Tokyo 2AP-Southeast - SydneyAP-South - SingaporeAP-West - MumbaiAU-MEL - MelbourneBR-GRU - São PauloCA-Central - TorontoDE-FRA-2 - Frankfurt 2ES-MAD - MadridEU-Central - FrankfurtEU-West - LondonFR-PAR - ParisGB-LON - London 2ID-CGK - JakartaIN-BOM-2 - Mumbai 2IN-MAA - ChennaiIT-MIL - MilanJP-OSA - OsakaJP-TYO-3 - Tokyo 3Linode Kubernetes EngineNL-AMS - AmsterdamSE-STO - StockholmSG-SIN-2 - Singapore 2US-Central - DallasUS-East - NewarkUS-IAD - WashingtonUS-LAX - Los AngelesUS-MIA - MiamiUS-ORD - ChicagoUS-SEA - SeattleUS-Southeast - AtlantaUS-West - Fremont

Timeline of updates

  1. resolved

    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.

  2. postmortem

    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.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on status.linode.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Linode (Akamai), started 2026-10-22 13:58 UTC, resolved after 0 min, 2 update(s); edited after publishing.

Title
Service Issue - Linode Kubernetes Engine
Vendor
Linode (Akamai)
Date
URL
https://rewindex.com/company/linode-akamai/incidents/dw5cxc8twwq5

Linode (Akamai) profileRecent Linode (Akamai) incidentsAll outages on October 22, 2026Linode (Akamai) in October 2026MarkdownJSON