Any scheduled server maintenance or related issues will be posted here in real time.
View Server Status
THIS IS A SCHEDULED EVENT Apr 18, 11:00 - 23:00 UTC Feb 17, 16:58 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be undergoing scheduled maintenance between 11:00 UTC to 23:00 (UTC) on Saturday, 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. 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.
THIS IS A SCHEDULED EVENT Mar 21, 11:00 - 23:00 UTC Feb 17, 16:55 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be undergoing scheduled maintenance between 11:00 UTC to 23:00 (UTC) on Saturday, March 21th, 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.
Feb 27, 21:01 UTC Feb 27, 20:18 UTC
Resolved - We haven’t observed any additional connectivity issues in our Singapore data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Investigating - Our team is investigating an issue affecting connectivity in our Singapore data center starting at approximately 1905 UTC, February 27, 2026. 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.
Feb 28, 17:43 UTC Feb 28, 12:16 UTC Feb 28, 11:11 UTC Feb 27, 21:34 UTC Feb 27, 21:00 UTC
Monitoring - We have taken mitigation steps and escalated to our third-party service provider in our Mumbai, IN (in-mum) data center, who confirmed the impact was caused due to ongoing restoration activities on their cable system during that period, which has been completed.; based on current observations as of 13:40 UTC on February 28, 2026, the service is resuming normal operations. We will continue to monitor to ensure that the impact has been fully mitigated.
Investigating - At this time we have been able to apply mitigation actions that improve the experience for customers connecting to our Mumbai, IN (in-mum) data center. In the meantime, we are actively investigating the issue with our third-party and will share additional updates as we have more information. If you are experiencing issues, please open a Support ticket for assistance.
Identified - We are aware of an ongoing reoccurrence of this issue starting from 09:17 UTC on February 28, 2026, which may cause degraded networking performance and packet loss with multiple Akamai services in the Mumbai, IN region.
Our team is investigating and we will share additional updates as we have more information. If you are experiencing issues, please open a Support ticket for assistance.
Monitoring - At this time we have been able to correct the issues affecting connectivity in our Mumbai, IN (in-mum) 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.
Investigating - Our team is investigating an issue affecting connectivity in our Mumbai, IN (in-mum) 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.
Feb 27, 19:45 UTC Feb 27, 15:48 UTC Feb 27, 14:35 UTC Feb 27, 13:38 UTC
Resolved - We haven’t observed any additional connectivity issues in our Chennai, IN (in-maa) and Mumbai Expansion, IN (in-bom-2) data centers, 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 monitor for any further issues.
Monitoring - At this time we have been able to correct the issues affecting connectivity in our Chennai, IN (in-maa) and Mumbai Expansion, IN (in-bom-2) data centers. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Investigating - Our team is investigating an issue affecting connectivity in our Chennai, IN (in-maa) and Mumbai Expansion, IN (in-bom-2) data centers 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.