Linode

Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. 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” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” 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/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/

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/

Our team is investigating an emerging service issue affecting booting up GPU plans. We will share additional updates as we have more information.

Our team is investigating an emerging service issue affecting networking in US-MIA (Miami). We will share additional updates as we have more information.

Our team is investigating an issue affecting the Longview service. During this time, users may experience "waiting for data" in cloud manager and might not see the expected metrics. We will share additional updates as we have more information.

Our team is investigating an emerging service issue affecting Linode Migrations in all regions. Migrations might be slow or pending for long time. We will share additional updates as we have more information.

We are currently investigating an emerging service issue affecting LKE Enterprise clusters across all regions. During this time, users may experience failures when deploying new clusters or upgrading existing ones. Our team is working to resolve this, and we will provide updates here as they become available.

Our team is investigating an upstream emerging service issue affecting our Support phone line due to problems with an upstream provider. We will share additional updates as we have more information. If you are having difficulty reaching us over the phone during this time, please reach us through a ticket.

Our team is investigating an issue affecting the Block Storage service in our Newark, US data center. During this time, users may experience connection timeouts, latency and errors with this service. We will share additional updates as we have more information.

Our team has identified issues with the Community Site (https://www.linode.com/community/questions/). During this time, the page has been moved under maintenance mode. We will share additional updates as we have more information.

Starting at around 10:07 UTC on May 29, 2026, Object Storage in London became unavailable. Affected customers were unable to access Object Storage during this time, and may have seen 500 or similar errors. This occurred as the result of an issue with a planned router upgrade. The router has since been brought back online, and we can confirm that the issue was mitigated at 10:19 UTC on May 29, 2026 and is no longer occurring. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence. If you continue to experience problems, please open a Support ticket for assistance.

We are investigating a service issue affecting traffic in our Paris data center. We will share additional updates as we have more information.

Our team is investigating an emerging service issue affecting GPU provisioning in all regions. At this time deployment of RTX PRO 6000 Blackwell plans in unavailable. We will share additional updates as we have more information.