Akamai Linode outage, October 2026: Service Issue - Linode Kubernetes Engine
Akamai Linode reported and resolved an incident: Service Issue - Linode Kubernetes Engine. It lasted 1 minute.
OKResolved
From Akamai Linode's official status page, in their words.
What happened
- Started
- Resolved
- Duration
- 1 minute
- Impact
- none
- 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
- Investigating
- Identifiednot posted
- Monitoringnot posted
- Resolved
Why it happened
Akamai Linode has not given a cause in its updates. We never guess one.
How it was resolved
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.
Timeline
Oldest first, from the first notice to the resolution. From Akamai Linode's official status page, in their words.
- 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.
- 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.
What this means for a business (and what to check now)
- Retry anything that failed during the 1 minute.
- Enter any payments, bookings or jobs you took another way.
- If a deadline fell inside the window, keep this page as your record of the outage.
The full guide: what to do when a service you rely on is down
Other Akamai Linode incidents
- Connectivity Issue - FR-PAR-2 (Paris 2), resolved after 2.8 hours
- Connectivity Issue - IN-MAA and IN-BOM-2, resolved after 3.2 hours
- Service Issue - US-Southeast (Atlanta), open, investigating
- Customer Security Advisory: CVE-2026-98432, open, investigating
- Service Issue - Block Storage (BR-GRU), open, monitoring
Hear about the next Akamai Linode incident as it starts
Free email alerts when the official status changes, with what to do while it is down.