Scheduled Maintenance

THIS IS A SCHEDULED EVENT Apr 19, 18:00 - 19:30 UTC

Mar 10, 21:16 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be undergoing scheduled maintenance between 1800 UTC to 1930 (UTC) on April 19, 2026.

During this window, running Linodes and related services will not be disrupted, but there may be brief periods of increased latency of responses or unavailability of the Linode Cloud Manager, API, and CLI.

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 may 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 may 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 brief periods 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:
For brief periods during the maintenance window, current Linode customers may not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes actions such as create, remove, boot, migrate, back up, shut down, etc across all Linode services, Kubernetes autoscaling, or management of PVCs and Nodebalancers. Interruptions expected during this window should be brief and only expected to last a few minutes, 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.

THIS IS A SCHEDULED EVENT Apr 18, 18:00 - 19:30 UTC

Mar 10, 21:14 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be undergoing scheduled maintenance between 1800 UTC to 1930 (UTC) on April 18, 2026.

During this window, running Linodes and related services will not be disrupted, but there may be brief periods of increased latency of responses or unavailability of the Linode Cloud Manager, API, and CLI.

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 may 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 may 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 brief periods 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:
For brief periods during the maintenance window, current Linode customers may not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes actions such as create, remove, boot, migrate, back up, shut down, etc across all Linode services, Kubernetes autoscaling, or management of PVCs and Nodebalancers. Interruptions expected during this window should be brief and only expected to last a few minutes, 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.

THIS IS A SCHEDULED EVENT Apr 8, 04:00 - 05:30 UTC

Mar 19, 03:21 UTC
Update - We will be undergoing scheduled maintenance during this time.

Mar 19, 03:20 UTC
Update - We will be undergoing scheduled maintenance during this time.

Mar 17, 21:58 UTC
Scheduled - Scheduled Maintenance — Cloud Manager, API, Cloud IAM and CLI

April 8, 2026
04:00 UTC – 05:30 UTC

The Linode Cloud Manager, API, Cloud IAM and CLI will be unavailable during this scheduled maintenance window.

Running Linodes and existing workloads will continue operating normally during this time. However, customers will not be able to access the Cloud Manager, interact with the API, or perform account or infrastructure management actions until maintenance is complete.

This includes actions such as creating or modifying resources, managing configurations, or accessing Support tickets through the Cloud Manager.

During this maintenance window:

- Kubernetes cluster workloads will continue running normally. However, actions that require the Linode API such as creating new clusters or scaling operations will not be available until maintenance is complete.

- New account creation and account authentication will be temporarily unavailable while the Cloud Manager is offline.

Customers who require assistance from Linode Support during this window may contact our Support team by phone:

United States: 855-454-6633
International: +1-609-380-7100

Please note that while phone support will be available, Support teams will not be able to assist with actions that require Cloud Manager or API access until maintenance is complete — this includes responding to Support tickets.

We recommend completing any time-sensitive administrative tasks before the maintenance window begins.

We will provide an update on this page once maintenance has been completed and full access to all services has been restored.

Thank you for your patience and understanding.

THIS IS A SCHEDULED EVENT Mar 24, 11:00 - 14:00 UTC

Mar 10, 04:03 UTC
Scheduled - The Cloud IAM AuthZ (which is an authorization system underlying Cloud Manager, API and CLI) will be undergoing maintenance between 11:00 UTC to 14:00 (UTC) on Tuesday, March 24th, 2026. During this window, running Linodes and related services will not be disrupted, but there may be brief periods of increased latency of responses or unavailability of the Linode Cloud Manager, API, and CLI.

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 may 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 may 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 brief periods 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:
For brief periods during the maintenance window, current Linode customers may not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes actions such as create, remove, boot, migrate, back up, shut down, etc across all Linode services. While we expect the impact period to be approximately 10 minutes cumulatively across the maintenance window, a longer impact period is possible.

This maintenance will impact the Kubernetes API. Dynamic aspects of LKE that rely on the Linode API will also be impacted, including autoscaling, recycling, rebooting, attaching/detaching PVCs, NodeBalancer 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:
The Linode Cloud Manager may be offline for brief periods 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.

Mar 20, 17:28 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our Jakarta, ID data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.

Mar 20, 16:58 UTC
Update - We are continuing to work on resolving the connectivity issue in our Jakarta, ID (id-cgk) data center. Thank you for your patience as we restore full service.

Mar 20, 16:07 UTC
Update - We are making steady progress toward full recovery of the connectivity issue at our Jakarta, ID (id-cgk) data center. Most services in Jakarta are now operational. However, some Linodes and Linode Kubernetes Engine (LKE) clusters may still be affected, especially if nodes are provisioned or attempt to provision on impacted Linodes. The dependency issues that previously affected Singapore Expansion, SP (sg-sin-2) and Melbourne, AU (au-mel) have been resolved.

We continue to work on restoring all services and appreciate your patience as we address the remaining issues. Further updates will be provided as progress continues.

Mar 20, 15:13 UTC
Update - Our teams are continuing to mitigate the connectivity issue in Jakarta, ID and are working to restore full service. We appreciate your patience as we resolve the remaining disruptions.

Mar 20, 14:23 UTC
Update - We are continuing to address the connectivity issue at our Jakarta, ID (id-cgk) data center. Most services have recovered, but some compute services in Jakarta remain affected. Due to backend dependencies, customers in the Singapore Expansion, SP (sg-sin-2) and Melbourne, AU (au-mel) data centers may also experience disruptions, particularly with Linode Kubernetes Engine (LKE) deployments. Our teams are actively working to resolve these issues and restore full service. We appreciate your patience and will share further updates as progress is made.

Mar 20, 13:31 UTC
Update - We are still working to resolve the connectivity issue at our Jakarta, ID data center. While most services are recovering, some compute services in Jakarta may still be affected. Due to backend dependencies, there may also be impacts to nearby data centers Singapore Expansion, SP (sg-sin-2) and Melbourne, AU (au-mel). Linode Kubernetes Engine (LKE) in these regions could experience disruptions because of a dependency with Jakarta, ID (id-cgk). We appreciate your patience and will provide further updates as we make progress.

Mar 20, 12:57 UTC
Identified - We are continuing to implement a fix for the connectivity issue in our Jakarta, ID data center.

Mar 20, 12:11 UTC
Update - Our team has identified the issue affecting connectivity in our Jakarta, ID data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Mar 20, 11:29 UTC
Investigating - Our team has identified the issue affecting connectivity in our Jakarta data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.