- Level
- confirmed
- Worst impact
- Degraded
- Components
- US-East (Newark), US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas), US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont), US-West (Fremont) Linode Kubernetes Engine, US-Southeast (Atlanta), US-Southeast (Atlanta) Linode Kubernetes Engine, US-IAD (Washington), US-IAD (Washington) Linode Kubernetes Engine, US-ORD (Chicago), US-ORD (Chicago) Linode Kubernetes Engine, CA-Central (Toronto), CA-Central (Toronto) Linode Kubernetes Engine, EU-West (London), EU-West (London) Linode Kubernetes Engine, EU-Central (Frankfurt), EU-Central (Frankfurt) Linode Kubernetes Engine, FR-PAR (Paris), FR-PAR (Paris) Linode Kubernetes Engine, AP-South (Singapore), AP-South (Singapore) Linode Kubernetes Engine, AP-Northeast-2 (Tokyo 2), AP-Northeast (Tokyo 2) Linode Kubernetes Engine, AP-West (Mumbai), AP-West (Mumbai) Linode Kubernetes Engine, AP-Southeast (Sydney), AP-Southeast (Sydney) Linode Kubernetes Engine, SE-STO (Stockholm), SE-STO (Stockholm) Linode Kubernetes Engine, US-SEA (Seattle), US-SEA (Seattle) Linode Kubernetes Engine, IT-MIL (Milan), JP-OSA (Osaka) Linode Kubernetes Engine, JP-OSA (Osaka), IN-MAA (Chennai) Linode Kubernetes Engine, IN-MAA (Chennai), ID-CGK (Jakarta) Linode Kubernetes Engine, ID-CGK (Jakarta), BR-GRU (São Paulo) Linode Kubernetes Engine, BR-GRU (São Paulo), NL-AMS (Amsterdam) Linode Kubernetes Engine, NL-AMS (Amsterdam), ES-MAD (Madrid) Linode Kubernetes Engine, US-MIA (Miami), IT-MIL (Milan) Linode Kubernetes Engine, US-LAX (Los Angeles), US-MIA (Miami) Linode Kubernetes Engine, ES-MAD (Madrid), US-LAX (Los Angeles) Linode Kubernetes Engine, AU-MEL (Melbourne), GB-LON (London 2) Linode Kubernetes Engine, GB-LON (London 2), AU-MEL (Melbourne) Linode Kubernetes Engine, IN-BOM-2 (Mumbai 2), IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, DE-FRA-2 (Frankfurt 2), SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, JP-TYO-3 (Tokyo 3), JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine, ZA-JNB (Johannesburg), NZ-AKL (Auckland), CO-BOG (Bogota), US-DEN (Denver), DE-HAM (Hamburg), US-HOU (Houston), MY-KUL (Kuala Lumpur), FR-MRS (Marseille), MX-QRO (Queretaro), CL-SCL (Santiago), FR-PAR-2 (Paris 2), US-IAD-2 (Washington 2)
- Regions
- ap-northeast-2, apac, au, ca, eu, latam, us
- Down Index
- 46of 100
What to do
Check whether you use Akamai Cloud (Linode) US-East (Newark), US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas), US-Central (Dallas) Linode Kubernetes Engine and 70 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 1h 1m it lasted.
Anything that failed between 2026-05-16 00:42 UTC and 2026-05-16 01:43 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) 4
- investigating
Our team is investigating an emerging service issue affecting Linodes booting across all regions. We will share additional updates as we have more information.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
The issue has been identified and a fix has been implemented.
provider
- resolved
This incident has been resolved.
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-36cc7ecadc
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-05-16 01:43 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
1h 1m, from 2026-05-16 00:42 UTC to 2026-05-16 01:43 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named US-East (Newark), US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas), US-Central (Dallas) Linode Kubernetes Engine and 70 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.