Scheduled Maintenance

THIS IS A SCHEDULED EVENT Jun 4, 02:00 - 05:00 UTC

Apr 23, 18:18 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 05:00 UTC on Tuesday, June 4th, 2024. During this window, running Linodes and related services will not be disrupted, but account management access and Support tickets will be unavailable.

Additionally, the Linode Image service in all regions will become unavailable starting at 01:00 UTC until 05:00 UTC on Tuesday, June 4th, 2024. Image creation and image restoration will not be available during this time.

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.

THIS IS A SCHEDULED EVENT May 14, 02:00 - 03:00 UTC

Apr 23, 18:39 UTC
Scheduled - We will be performing maintenance on our database infrastructure, starting at 02:00 UTC on Tuesday, May 14th, 2024, expected to last 1 hour (until 03:00 UTC, Tuesday, May 14th, 2024). During this period, Cloud Manager and the Linode API should continue to function without interruption, but there is a small possibility that for a few minutes at a time, an action may fail, in which case please retry the action again a few minutes later.

THIS IS A SCHEDULED EVENT May 8, 02:00 - 05:00 UTC

Apr 23, 18:13 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 05:00 UTC on Wednesday, May 8th, 2024. During this window, running Linodes and related services will not be disrupted, but account management access and Support tickets will be unavailable.

Additionally, the Linode Image service in all regions will become unavailable starting at 01:00 UTC until 05:00 UTC on Wednesday, May 8th, 2024. Image creation and image restoration will not be available during this time.

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.

THIS IS A SCHEDULED EVENT May 1, 20:00 - 23:00 UTC

Apr 22, 20:27 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-West (Mumbai) data center from 20:00 (UTC) until 23:00 (UTC) on Wednesday, May 1st. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.

Apr 26, 05:07 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our Miami 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.

Apr 26, 04:48 UTC
Identified - Our team has identified the issue affecting connectivity in our Miami data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Apr 26, 03:37 UTC
Investigating - Our team is investigating an issue affecting connectivity in our Miami data center. During this time, users may experience intermittent connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information.