- Level
- confirmed
- Worst impact
- Degraded
- Components
- US-East (Newark) NodeBalancers, US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) NodeBalancers, US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont) NodeBalancers, US-West (Fremont) Linode Kubernetes Engine, US-Southeast (Atlanta) NodeBalancers, US-Southeast (Atlanta) Linode Kubernetes Engine, US-IAD (Washington) NodeBalancers, US-IAD (Washington) Linode Kubernetes Engine, US-ORD (Chicago) NodeBalancers, US-ORD (Chicago) Linode Kubernetes Engine, CA-Central (Toronto) NodeBalancers, CA-Central (Toronto) Linode Kubernetes Engine, EU-West (London) NodeBalancers, EU-West (London) Linode Kubernetes Engine, EU-Central (Frankfurt) NodeBalancers, EU-Central (Frankfurt) Linode Kubernetes Engine, FR-PAR (Paris) NodeBalancers, FR-PAR (Paris) Linode Kubernetes Engine, AP-South (Singapore) NodeBalancers, AP-South (Singapore) Linode Kubernetes Engine, AP-Northeast-2 (Tokyo 2) NodeBalancers, AP-Northeast (Tokyo 2) Linode Kubernetes Engine, AP-West (Mumbai) NodeBalancers, AP-West (Mumbai) Linode Kubernetes Engine, AP-Southeast (Sydney) NodeBalancers, AP-Southeast (Sydney) Linode Kubernetes Engine, SE-STO (Stockholm) NodeBalancers, SE-STO (Stockholm) Linode Kubernetes Engine, US-SEA (Seattle) NodeBalancers, US-SEA (Seattle) Linode Kubernetes Engine, JP-OSA (Osaka) NodeBalancers, JP-OSA (Osaka) Linode Kubernetes Engine, IN-MAA (Chennai) NodeBalancers, IN-MAA (Chennai) Linode Kubernetes Engine, ID-CGK (Jakarta) Linode Kubernetes Engine, BR-GRU (São Paulo) NodeBalancers, NL-AMS (Amsterdam) NodeBalancers, BR-GRU (São Paulo) Linode Kubernetes Engine, ES-MAD (Madrid) NodeBalancers, NL-AMS (Amsterdam) Linode Kubernetes Engine, IT-MIL (Milan) NodeBalancers, ES-MAD (Madrid) Linode Kubernetes Engine, US-MIA (Miami) NodeBalancers, IT-MIL (Milan) Linode Kubernetes Engine, ID-CGK (Jakarta) NodeBalancers, US-MIA (Miami) Linode Kubernetes Engine, US-LAX (Los Angeles) NodeBalancers, US-LAX (Los Angeles) Linode Kubernetes Engine, GB-LON (London 2) NodeBalancers, GB-LON (London 2) Linode Kubernetes Engine, AU-MEL (Melbourne) NodeBalancers, AU-MEL (Melbourne) Linode Kubernetes Engine, IN-BOM-2 (Mumbai 2) NodeBalancers, IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine, DE-FRA-2 (Frankfurt 2) NodeBalancers, DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2) NodeBalancers, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, JP-TYO-3 (Tokyo 3) NodeBalancers, JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine
- Regions
- ap-northeast-2, apac, au, ca, eu, latam, us
- Down Index
- 52of 100
What to do
Check whether you use Akamai Cloud (Linode) US-East (Newark) NodeBalancers, US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) NodeBalancers, US-Central (Dallas) Linode Kubernetes Engine and 58 more in ap-northeast-2, apac, au, ca. 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 3d 19h it lasted.
Anything that failed between 2026-04-24 19:27 UTC and 2026-04-28 15:16 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 the Linode Kubernetes Engine (LKE) service across multiple regions. We will share additional updates as we have more information.
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.
provider
- identified
Our team has identified that due to this issue, customers may also experience issues creating new nodebalancers. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
provider
- identified
Our team has identified the issue affecting the LKE and newly updated/created NodeBalancer configurations. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
provider
- identified
We are continuing work to apply the identified fix the issue affecting the LKE and newly updated/created NodeBalancer configurations and we will provide an update as soon as the solution is in place.
provider
- identified
We are continuing work to apply the identified fix the issue affecting the LKE and newly updated/created NodeBalancer configurations and we will provide an update as soon as the solution is in place.
provider
- monitoring
At this time we have been able to correct the issues affecting the NodeBalancer service at 23:36 UTC on April 24, 2026. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a ticket with our Support Team.
provider
- resolved
We haven’t observed any additional issues with the LKE and NodeBalancer 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-d1b24ceb49
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-04-28 15:16 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
3d 19h, from 2026-04-24 19:27 UTC to 2026-04-28 15:16 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named US-East (Newark) NodeBalancers, US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) NodeBalancers, US-Central (Dallas) Linode Kubernetes Engine and 58 more in ap-northeast-2, apac, au, ca.
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.