Linode (Akamai) outage, 22 October 2026
Service Issue - Linode Kubernetes Engine
- Started
- Resolved
- 22 Oct 2026, 13:58 UTC
- Impact
- Not stated
- Affected
- 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
Is this still happening?
No. Linode (Akamai) marked this incident resolved on 22 Oct 2026, 13:58 UTC.
Right now: Linode (Akamai) reports degraded performance on some systems. (as of 26 Oct, 03:45 UTC) Live Linode (Akamai) status
Last update from Linode (Akamai)
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.
Read the full incident on the official Linode (Akamai) status page
Similar Linode (Akamai) incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.
-
, resolved after 9 h 13 min
-
, resolved after 2 h 11 min
Service Issue - Linode Kubernetes Engine Enterprise (LKE-E)- IAD2 (Washington)
-
, resolved after 1 h 37 min
-
, resolved
Service Issue - Linode Kubernetes Engine Enterprise (LKE-E) - Seattle (SEA1)