- Level
- confirmed
- Worst impact
- Degraded
- Components
- 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, AP-West (Mumbai) Linode Kubernetes Engine, AP-Southeast (Sydney) Linode Kubernetes Engine, SE-STO (Stockholm) Linode Kubernetes Engine, US-SEA (Seattle) Linode Kubernetes Engine, JP-OSA (Osaka) Linode Kubernetes Engine, IN-MAA (Chennai) Linode Kubernetes Engine, ID-CGK (Jakarta) Linode Kubernetes Engine, BR-GRU (São Paulo) Linode Kubernetes Engine, NL-AMS (Amsterdam) Linode Kubernetes Engine, ES-MAD (Madrid) Linode Kubernetes Engine, IT-MIL (Milan) Linode Kubernetes Engine, US-MIA (Miami) Linode Kubernetes Engine, US-LAX (Los Angeles) Linode Kubernetes Engine, GB-LON (London 2) Linode Kubernetes Engine, AU-MEL (Melbourne) Linode Kubernetes Engine, IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine, DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine
- Regions
- apac, au, ca, eu, latam, us
- Down Index
- 52of 100
What to do
Check whether you use Akamai Cloud (Linode) US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont) Linode Kubernetes Engine, US-Southeast (Atlanta) Linode Kubernetes Engine and 27 more in apac, au, ca, eu. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d it lasted.
Anything that failed between 2026-04-16 13:20 UTC and 2026-04-17 13:30 UTC may need a replay.Subscribe to Akamai Cloud (Linode)'s feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=linode works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Akamai Cloud (Linode) 8
- investigating
Our team is investigating an emerging service issue affecting Linode Kubernetes Engine Standard and Enterprise in all regions. We will share additional updates as we have more information.
provider
- investigating
Our team continues to investigate the issue with the Linode Kubernetes Engine. Affected customers may be unable to deploy new clusters or add new nodes to a cluster. We will share additional updates as we have more information. Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
provider
- investigating
Our team continues to investigate the issue affecting the Linode Kubernetes Engine (LKE). We will share additional updates as we have more information. Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
provider
- identified
Our team has identified the issue affecting the LKE service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
provider
- identified
Our team continues to work on implementing a fix for the issue affecting the Linode Kubernetes Engine. We will continue to provide updates until a solution is in place. Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
provider
- identified
As of 15:53 UTC on April 16, 2026 we are starting to see nodes successfully provisioning, however the service is not fully back up yet. Some customers may remain impacted at this time. We are working to stabilize the service, and will provide another update within the next 30 minutes. Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
provider
- monitoring
As of 16:27 UTC on April 16, 2026 we have corrected the issues affecting the LKE service. The issue was caused by an expired certificate, which has been updated. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
provider
- resolved
We haven’t observed any additional issues with the LKE and LKE-E services, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-652a2f29a9
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-04-17 13:30 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
1d, from 2026-04-16 13:20 UTC to 2026-04-17 13:30 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont) Linode Kubernetes Engine, US-Southeast (Atlanta) Linode Kubernetes Engine and 27 more in apac, au, ca, eu.
What caused it?
Akamai Cloud (Linode) hasn't published a root cause. If it does, it shows here.
Where does this come from?
Akamai Cloud (Linode)'s official status page, https://status.linode.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.