Any scheduled server maintenance or related issues will be posted here in real time.
View Server Status
THIS IS A SCHEDULED EVENT Aug 19, 04:00 - 05:30 UTC 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.
Aug 12, 03:29 UTC Aug 11, 23:35 UTC Aug 10, 17:15 UTC
Identified - We have identified the cause of the issue, and a fix is being implemented. We will provide an update as soon as the solution is in place.
Update - We are continuing to investigate this issue. The appropriate subject matter experts are engaged. Subsequent updates around mitigation status will be posted as progress is made.
Investigating - Our team is investigating an upstream issue impacting Ubuntu deployments. This may impact the ability to install package and security updates on all Ubuntu systems.
Aug 5, 01:34 UTC Aug 4, 18:36 UTC Jul 31, 18:25 UTC Jul 31, 17:49 UTC
Resolved - At this time the upstream provider has been able to correct the issue causing packet loss on some routes from the in-maa & in-bom-2 data centers into the US region and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Update - We are continuing to work with our upstream provider to resolve the packet loss affecting some paths between the in-maa and in-bom-2 data centers and the US region. We will share further updates as progress continues.
Identified - Our team has identified the cause of packet loss to our US data centers. We are working with our upstream provider to resolve this issue and we will provide an update as soon as the solution is in place.
Investigating - Our team is investigating packet loss on some paths from the in-maa & in-bom-2 data centers into the US region. During this time, users may experience connection timeouts and errors with services traversing between India and United States regions. We will share additional updates as we have more information.
Aug 4, 08:40 UTC Aug 4, 08:03 UTC Aug 4, 03:00 UTC Jul 28, 14:09 UTC
Completed - All Linode boot failures have now been resolved and the issue affecting the Block Storage servers has also been resolved.
Update - Scheduled maintenance is currently in progress. Customers might be seeing linode boot failures where block storage volumes are attached. New volumes are also being seen stuck in creating state. We're actively working on getting these issues fixed. In case, a critical linode is not able to boot, please try detaching any block storage volume and rebooting the linode as a workaround.
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled - We will be performing maintenance on our Block Storage switches in Toronto on Tuesday, August 4th at 03:00 UTC for a duration of 4 hours. Because of our redundant switching infrastructure, we do not expect any downtime during this maintenance. However, a brief period of packet loss or increased latency may be observed.
Jul 29, 12:27 UTC Jul 28, 22:51 UTC Jul 28, 20:17 UTC Jul 28, 19:27 UTC Jul 28, 18:14 UTC
Resolved - We haven’t observed any additional host jobs performance degradation issues, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Monitoring - A fix has been implemented and we are monitoring the results.
Update - We would like to update that after additional investigation, the impact would manifest in delayed and sometimes failed host jobs, which could include many different actions on Linodes and not only impacting attaching and detaching Block Storage volumes as we mentioned in our initial update, we have updated the title to reflect the updated impact. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Identified - Our team has identified the issue affecting the Block Storage service in our data centers. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Investigating - Our team is investigating an issue affecting the Block Storage service in several data center regions. This issue largely impacts attaching and detaching Block Storage volumes. During this time, users may experience volume attach/detach hangs, timeouts and errors with this service. We will share additional updates as we have more information.