- Level
- confirmed
- Worst impact
- Degraded
- Components
- US-East (Newark), Linode.com, US-East (Newark) Block Storage, US-East (Newark) NodeBalancers, US-East (Newark) Backups, US-East (Newark) Object Storage, US-East (Newark) Linode Kubernetes Engine, US-East (Newark), Cloud Manager and API, US-Central (Dallas), US-Central (Dallas) Block Storage, US-Central (Dallas) NodeBalancers, US-Central (Dallas) Backups, US-Central (Dallas) Linode Kubernetes Engine, US-Southeast (Atlanta) Object Storage, US-Central (Dallas), Akamai Cloud Pulse (ACLP) - Logs, US-West (Fremont), Hosted DNS Service, US-West (Fremont) Block Storage, US-West (Fremont) NodeBalancers, US-West (Fremont) Backups, US-West (Fremont) Linode Kubernetes Engine, US-IAD (Washington) Object Storage, US-West (Fremont), US-Southeast (Atlanta), US-Southeast (Atlanta) NodeBalancers, US-Southeast (Atlanta) Backups, Longview, US-Southeast (Atlanta) Block Storage, US-Southeast (Atlanta) Linode Kubernetes Engine, US-ORD (Chicago) Object Storage, US-Southeast (Atlanta), EU-Central (Frankfurt) Object Storage, Managed Databases, US-IAD (Washington), US-IAD (Washington) Backups, US-IAD (Washington) Block Storage, US-IAD (Washington) NodeBalancers, US-IAD (Washington) Linode Kubernetes Engine, US-IAD (Washington), AP-South (Singapore) Object Storage, US-ORD (Chicago), US-ORD (Chicago) Backups, US-ORD (Chicago) Block Storage, US-ORD (Chicago) NodeBalancers, US-ORD (Chicago) Linode Kubernetes Engine, US-ORD (Chicago), CA-Central (Toronto), CA-Central (Toronto) Block Storage, CA-Central (Toronto) NodeBalancers, CA-Central (Toronto) Backups, CA-Central (Toronto) Linode Kubernetes Engine, FR-PAR (Paris) Object Storage, CA-Central (Toronto), EU-West (London), EU-West (London) Block Storage, EU-West (London) NodeBalancers, EU-West (London) Backups, EU-West (London) Linode Kubernetes Engine, SE-STO (Stockholm) Object Storage, EU-West (London), EU-Central (Frankfurt), EU-Central (Frankfurt) Block Storage, EU-Central (Frankfurt) NodeBalancers, EU-Central (Frankfurt) Backups, EU-Central (Frankfurt) Linode Kubernetes Engine, US-SEA (Seattle) Object Storage, EU-Central (Frankfurt), FR-PAR (Paris), FR-PAR (Paris) Backups, FR-PAR (Paris) Block Storage, FR-PAR (Paris) NodeBalancers, FR-PAR (Paris) Linode Kubernetes Engine, JP-OSA (Osaka) Object Storage, FR-PAR (Paris), AP-South (Singapore), AP-South (Singapore) Block Storage, AP-South (Singapore) NodeBalancers, AP-South (Singapore) Backups, AP-South (Singapore) Linode Kubernetes Engine, IN-MAA (Chennai) Object Storage, AP-South (Singapore), AP-Northeast-2 (Tokyo 2), AP-Northeast-2 (Tokyo 2) NodeBalancers, AP-Northeast-2 (Tokyo 2) Backups, AP-Northeast-2 (Tokyo 2) Block Storage, AP-Northeast (Tokyo 2) Linode Kubernetes Engine, ID-CGK (Jakarta) Object Storage, AP-Northeast-2 (Tokyo 2), AP-West (Mumbai), AP-West (Mumbai) Block Storage, AP-West (Mumbai) NodeBalancers, AP-West (Mumbai) Backups, AP-West (Mumbai) Linode Kubernetes Engine, BR-GRU (Sao Paulo) Object Storage, AP-West (Mumbai), AP-Southeast (Sydney), AP-Southeast (Sydney) NodeBalancers, AP-Southeast (Sydney) Backups, AP-Southeast (Sydney) Linode Kubernetes Engine, AP-Southeast (Sydney) Block Storage, ES-MAD (Madrid) Object Storage, AP-Southeast (Sydney), SE-STO (Stockholm), SE-STO (Stockholm) Backups, SE-STO (Stockholm) Block Storage, SE-STO (Stockholm) NodeBalancers, SE-STO (Stockholm) Linode Kubernetes Engine, SE-STO (Stockholm), US-SEA (Seattle), US-SEA (Seattle) Backups, US-SEA (Seattle) Block Storage, US-SEA (Seattle) NodeBalancers, US-SEA (Seattle) Linode Kubernetes Engine, US-SEA (Seattle), IT-MIL (Milan), JP-OSA (Osaka) Backups, JP-OSA (Osaka) Block Storage, JP-OSA (Osaka) NodeBalancers, JP-OSA (Osaka) Linode Kubernetes Engine, GB-LON (London 2), IT-MIL (Milan), JP-OSA (Osaka), IN-MAA (Chennai) Backups, IN-MAA (Chennai) Block Storage, IN-MAA (Chennai) NodeBalancers, IN-MAA (Chennai) Linode Kubernetes Engine, AU-MEL (Melbourne), JP-OSA (Osaka), IN-MAA (Chennai), ID-CGK (Jakarta) Linode Kubernetes Engine, BR-GRU (São Paulo) Backups, BR-GRU (São Paulo) Block Storage, BR-GRU (São Paulo) NodeBalancers, NL-AMS (Amsterdam) Object Storage, IN-MAA (Chennai), ID-CGK (Jakarta), NL-AMS (Amsterdam) Backups, NL-AMS (Amsterdam) Block Storage, NL-AMS (Amsterdam) NodeBalancers, IT-MIL (Milan) Object Storage, BR-GRU (São Paulo) Linode Kubernetes Engine, ID-CGK (Jakarta), BR-GRU (São Paulo), ES-MAD (Madrid) Backups, ES-MAD (Madrid) Block Storage, ES-MAD (Madrid) NodeBalancers, US-MIA (Miami) Object Storage, NL-AMS (Amsterdam) Linode Kubernetes Engine, BR-GRU (São Paulo), NL-AMS (Amsterdam), IT-MIL (Milan) Backups, IT-MIL (Milan) Block Storage, IT-MIL (Milan) NodeBalancers, US-LAX (Los Angeles) Object Storage, ES-MAD (Madrid) Linode Kubernetes Engine, NL-AMS (Amsterdam), US-MIA (Miami), US-MIA (Miami) Backups, US-MIA (Miami) Block Storage, US-MIA (Miami) NodeBalancers, GB-LON (London 2) Object Storage, IT-MIL (Milan) Linode Kubernetes Engine, US-MIA (Miami), US-LAX (Los Angeles), ID-CGK (Jakarta) Backups, ID-CGK (Jakarta) Block Storage, ID-CGK (Jakarta) NodeBalancers, AU-MEL (Melbourne) Object Storage, US-MIA (Miami) Linode Kubernetes Engine, US-LAX (Los Angeles), ES-MAD (Madrid), US-LAX (Los Angeles) Backups, US-LAX (Los Angeles) Block Storage, US-LAX (Los Angeles) NodeBalancers, IN-BOM-2 (Mumbai 2) Object Storage, US-LAX (Los Angeles) Linode Kubernetes Engine, ES-MAD (Madrid), AU-MEL (Melbourne), GB-LON (London 2) Backups, GB-LON (London 2) Block Storage, GB-LON (London 2) NodeBalancers, DE-FRA-2 (Frankfurt 2) Object Storage, GB-LON (London 2) Linode Kubernetes Engine, AU-MEL (Melbourne), GB-LON (London 2), AU-MEL (Melbourne) Backups, AU-MEL (Melbourne) Block Storage, AU-MEL (Melbourne) NodeBalancers, SG-SIN-2 (Singapore 2) Object Storage, AU-MEL (Melbourne) Linode Kubernetes Engine, GB-LON (London 2), IN-BOM-2 (Mumbai 2), IN-BOM-2 (Mumbai 2) Backups, IN-BOM-2 (Mumbai 2) Block Storage, IN-BOM-2 (Mumbai 2) NodeBalancers, JP-TYO-3 (Tokyo 3) Object Storage, IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine, IN-BOM-2 (Mumbai 2), SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2) Backups, DE-FRA-2 (Frankfurt 2) Block Storage, DE-FRA-2 (Frankfurt 2) NodeBalancers, DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2), DE-FRA-2 (Frankfurt 2), SG-SIN-2 (Singapore 2) Backups, SG-SIN-2 (Singapore 2) Block Storage, SG-SIN-2 (Singapore 2) NodeBalancers, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine, DE-FRA-2 (Frankfurt 2), JP-TYO-3 (Tokyo 3), JP-TYO-3 (Tokyo) Backups, JP-TYO-3 (Tokyo 3) Block Storage, JP-TYO-3 (Tokyo 3) NodeBalancers, JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine, JP-TYO-3 (Tokyo 3), ZA-JNB (Johannesburg), ZA-JNB (Johannesburg), NZ-AKL (Auckland), NZ-AKL (Auckland), CO-BOG (Bogota), CO-BOG (Bogota), US-DEN (Denver), US-DEN (Denver), DE-HAM (Hamburg), DE-HAM (Hamburg), US-HOU (Houston), US-HOU (Houston), MY-KUL (Kuala Lumpur), MY-KUL (Kuala Lumpur), FR-MRS (Marseille), FR-MRS (Marseille), MX-QRO (Queretaro), MX-QRO (Queretaro), CL-SCL (Santiago), 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
- 52of 100
What to do
Check whether you use Akamai Cloud (Linode) US-East (Newark), Linode.com, US-East (Newark) Block Storage, US-East (Newark) NodeBalancers and 236 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 59d 1h it lasted.
Anything that failed between 2026-05-08 13:40 UTC and 2026-07-06 14:41 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) 5
- investigating
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems. As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers. As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected. [1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
provider
- investigating
We have updated our latest Linode kernel to version 7.0.5, which contains the upstream fix from kernel.org for the DirtyFrag vulnerabilities as well as the previous fixes for the recent CopyFail vulnerability. This kernel is available in Cloud Manager and we recommend customers using the Linode-compiled kernel update their configurations to this kernel. We are in parallel tracking the upstream Linux distributions and will provide another update when fixed versions have been released.
provider
- investigating
We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions. We will provide another update when more OS images have been updated and/or additional attack vectors are discovered. [1] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/ [2] https://www.linode.com/docs/guides/dirty-frag-mitigation/
provider
- investigating
We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions. We will provide another update when more OS images have been updated and/or additional attack vectors are discovered. [1] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/ [2] https://www.linode.com/docs/guides/dirty-frag-mitigation/
provider
- resolved
We have completed our investigation and response to the "DirtyFrag" (CVE-2026-43500, CVE-2026-43284) and "Fragnesia" (CVE-2026-46300) vulnerabilities. We have published documentation articles with detailed guidance on available mitigations and recommended actions for affected systems. Customers can find more information and step-by-step instructions here: https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/ https://www.linode.com/docs/guides/dirty-frag-mitigation/ We encourage all customers to review the article and apply the appropriate mitigations to their environments. If you have questions or need assistance, please contact us at 855-454-6633 (+1-609-380-7100 Intl.) or email support@linode.com 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-635bee3e0f
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-07-06 14:41 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
59d 1h, from 2026-05-08 13:40 UTC to 2026-07-06 14:41 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named US-East (Newark), Linode.com, US-East (Newark) Block Storage, US-East (Newark) NodeBalancers and 236 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.