Scheduled Maintenance

Jul 9, 14:53 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 04:00 UTC and 05:30 UTC on August 19, 2026. During this window, running Linodes and related services will not be disrupted, but account management access and Support tickets will be unavailable.

Please ensure that you complete critical or important jobs in the Cloud Manager or API before the maintenance window. We will update this status page once this event is complete and Linode customers have full access to all Linode services.

Customers who need assistance from Linode Support during this time will need to call 855-454-6633 (+1-609-380-7100 outside of the United States) to contact our Support team. Please note that our Support team will not be able to assist with issues related to the Cloud Manager or API, authenticate users to their accounts, or respond to Support tickets for the duration of the maintenance window. As soon as our Support team regains access, we will answer tickets in the order they are received.

Impacts on Current Linode Customers:
Current Linode customers will not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes Create, Remove, Boot, Migrate, Back Up, Shut Down, etc.

The scheduled maintenance will impact the Kubernetes API. Dynamic aspects of LKE that rely on the Linode API will also be impacted, to include items such as autoscaling, recycling, rebooting, attaching/detaching PVCs, Node Balancer provisioning, as well as the ability to create new clusters. Cluster nodes and running workloads will not be affected.

Impacts on Users Trying to Create Linode Accounts / Awaiting Account Authentication:
While the Linode Cloud Manager is offline during the maintenance period, we are unable to accept requests for new accounts or authenticate accounts for users awaiting full account access.

Thank you for your patience and understanding.

Jul 9, 17:49 UTC
Monitoring - At this time we have been able to correct the issue affecting the Cloud Manager logins. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com.

Jul 9, 17:24 UTC
Update - We are continuing to investigate this issue. We will provide an update within the next 30 minutes.

Jul 9, 16:57 UTC
Investigating - Our team is investigating an emerging service issue affecting Cloud Manager logins. We will share additional updates as we have more information.

Jun 30, 00:02 UTC
Update - We are continuing to monitor for any further issues.

Jun 26, 21:13 UTC
Monitoring - We have not observed a recurrence of the issue affecting the Cloud Pulse Metrics (ACLP Metrics) for several hours. Our team will continue to monitor the service closely while we investigate the underlying cause. If you continue to experience problems, please open a Support ticket for assistance.

Jun 26, 20:04 UTC
Update - We are continuing to investigate this issue.

Jun 26, 19:08 UTC
Update - We are continuing to investigate this issue. We will provide further updates as we have more information.

Jun 26, 18:19 UTC
Update - We are continuing to investigate this issue. We will share additional updates as we have more information.

Jun 26, 17:35 UTC
Investigating - Our team is investigating an issue affecting the Cloud Pulse Metrics (ACLP Metrics), specifically impacting Managed Database Metrics reporting. The issue appears to be intermittent. We will share additional updates as we have more information.

Jul 6, 18:04 UTC
Investigating - Our team is investigating an emerging service issue affecting Managed Databases across all regions. Customers may experience latency when provisioning new databases or deleting existing ones. There is no observed impact to the performance or availability of active, running databases at this time. We will provide updates as more information becomes available.

Jun 5, 20:24 UTC
Update - 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/

May 15, 17:30 UTC
Update - 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/

May 13, 21:02 UTC
Investigating - 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/