Linode Status

Postmortem: Starting around 19:15 UTC on March 12, 2026, customers were unable to create Linode Kubernetes Engine for Enterprise (LKE-E) clusters and unable to perform administrative tasks such as LKE-E version upgrades, Control Plane ACL changes, etc., in the Osaka data center (JP-OSA). The creation process was stalled indefinitely when attempting to deploy LKE-E clusters in this data center. Akamai’s investigation revealed that the issue started following a phased rollout of the LKE software release in the Osaka data center.
Akamai deployed a software fix to mitigate the impact. The impact was mitigated around 01:55 UTC on March 13, 2026. The clusters that were created during the impacted window resumed their creation.
Our subject matter experts will continue to investigate the root cause and will take appropriate preventive actions. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence.
This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

Resolved: We haven’t observed any additional issues with the LKE service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting the LKE service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Investigating: We are continuing to investigate this issue.

Investigating: Our team is investigating an emerging service issue affecting the deployment of new LKE Enterprise Clusters in JP, OSA (Osaka). We will share additional updates as we have more information.

Postmortem: Beginning at 18:09 UTC on March 9, 2026, approximately 25% of Compute hosts in our IAD3 (Washington DC) data center experienced degraded network connectivity due to the application of an updated routing configuration intended to improve network performance. This updated router configuration was extensively tested and has been running in production in another region for several weeks without any issues. An investigation revealed that application of this change inadvertently caused loss of connectivity to these host due to a network configuration specific to the IAD3 data center. 

‌

This resulted in loss of access and control of Linodes and clusters hosted on those machines until the issue was mitigated. Mitigation steps took longer than expected due to the specific networking nature of the issue and degradation of internal service visibility to impacted devices, which required additional planning to effectively apply a rollback to the prior configuration. 

‌

We were able to successfully rollback the routing configuration and mitigate impact at 21:16 UTC on March 9, 2026. To prevent a reoccurrence of this issue, we are developing a new routing configuration deployment plan that avoids the identified failure modes and others inferred from our observations.

‌

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Resolved: We haven’t observed any additional connectivity issues in our IAD (Washington, DC) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our IAD (Washington, DC) 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 has identified the issue affecting connectivity in our IAD (Washington, DC) data center. 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 emerging service issue affecting compute hosts in IAD (Washington, DC). We will share additional updates as we have more information.

Postmortem: On March 3, 2026, at approximately 20:00 UTC,, a cron job responsible for email notifications from Cloud Manager began failing due to timeouts. As the job exceeded the request timeout interval, it repeatedly failed and restarted, causing the process to resume from the beginning of its queue each time. This resulted in customers receiving multiple duplicate email notifications and some delay in those notifications. 

This issue only affected event-based notification emails related to host jobs such as VM shutdowns, startups, deletions, or deployments. Other notification emails set up by the customer, such as CPU usage thresholds, and the host jobs themselves remained unaffected. To address the issue, the cron job was temporarily stopped, associated services were restarted, and a processing limit was introduced to control the number of records handled per run. These actions stabilized the system, and the incident was considered mitigated at approximately 19:00 UTC on March 4, 2026.

After mitigation of the root cause, a backlog of approximately 2 million pending events had to be processed, which caused further delays in notification delivery over the following days for some customers. The system worked through this backlog and gradually returned to normal processing. As of March 10, 2026, the backlog has been cleared and notification emails are being delivered as expected.

Since this incident, we have already tested and implemented additional cron job optimizations to ensure consistent performance. We are committed to making continuous improvements to make our systems better and prevent recurrence.

This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Resolved: Our team has identified that the issue affecting the Cloud Manager and API is related to a previously communicated incident from March 4, 2026 (https://status.linode.com/incidents/yzlp8ykymmhm). Today's issue was caused by the backlog of notifications that accumulated due to the previous incident, and it has cleared now. We haven't observed any additional issues with the Cloud Manager or API, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected] for assistance.

Investigating: We are continuing to investigate this issue. As a workaround, customers can login to https://cloud.linode.com/ and manually check the notifications until the issue is mitigated. Subsequent updates will be posted as progress is made.

Investigating: We are continuing to investigate this issue. The appropriate subject matter experts are engaged. Subsequent updates will be posted as progress is made.

Investigating: Our team is investigating an emerging issue where some customers are receiving delayed event notification or notification emails for activities performed on Cloud Manager. We will share additional updates as we have more information.

Resolved: We haven’t observed any additional connectivity issues in our Washington data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Identified: Our team has identified the issue affecting connectivity in our Washington data center. 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 has identified the issue affecting connectivity in our Washington data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: We are continuing to investigate the issue. We will share additional updates as we have more information.

Investigating: Our team is investigating an emerging service issue affecting networking in our Washington, DC location (US-IAD). We will share additional updates as we have more information.