THIS IS A SCHEDULED EVENT Jun <var data-var='date'>8</var>, <var data-var='time'>06:00</var> - <var data-var='time'>16:00</var> UTC May <var data-var='date'>21</var>, <var data-var='time'>14:01</var> UTC Scheduled - We will be performing maintenance on the LKE platform to provide CNI updates including security fixes. These maintenance activities begin in each data center after local business hours. A brief period of increased latency, packet loss, or connectivity interruptions to your workload may be observed as the Calico networking pods restart. If necessary, please contact our support team for assistance or more information.

Scheduled maintenance - Linode Kubernetes Engine (LKE)

May <var data-var='date'>22</var>, <var data-var='time'>13:14</var> UTC Monitoring - The issue subsided by 11:30 UTC on May 22, 2026, the impact was observed between 09:10 UTC to 11:30 UTC on May 22, 2026. We are actively monitoring to ensure that the service remains stable . If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance. May <var data-var='date'>22</var>, <var data-var='time'>12:24</var> UTC Update - We are continuing to investigate the issue May <var data-var='date'>22</var>, <var data-var='time'>11:22</var> UTC Investigating - We are investigating a service issue affecting traffic in our Paris data center. We will share additional updates as we have more information.

Service Issue - Paris (FR-PAR3)

May <var data-var='date'>20</var>, <var data-var='time'>00:27</var> UTC Resolved - We haven’t observed any additional issues with the GPU provisioning in all regions, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance. May <var data-var='date'>19</var>, <var data-var='time'>21:58</var> UTC Monitoring - At this time we have been able to correct the issues affecting GPU provisioning in all regions as of 21:27 UTC. on May 19th, 2026. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance. May <var data-var='date'>19</var>, <var data-var='time'>21:06</var> UTC Update - The issue with deployment of RTX PRO 6000 Blackwell plans appears to have started around 15:00 UTC on May 19, 2026. We are actively working to deploy an API hotfix that is expected to be rolled out within 1 hour. We apologize for the impact. May <var data-var='date'>19</var>, <var data-var='time'>19:48</var> UTC Identified - Our team is investigating an emerging service issue affecting GPU provisioning in all regions. At this time deployment of RTX PRO 6000 Blackwell plans in unavailable. We will share additional updates as we have more information.

Emerging Service Issue - GPU Deployment

May <var data-var='date'>16</var>, <var data-var='time'>01:43</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>16</var>, <var data-var='time'>01:27</var> UTC Identified - The issue has been identified and a fix has been implemented. May <var data-var='date'>16</var>, <var data-var='time'>01:06</var> UTC Update - We are continuing to investigate this issue. May <var data-var='date'>16</var>, <var data-var='time'>00:42</var> UTC Investigating - Our team is investigating an emerging service issue affecting Linodes booting across all regions. We will share additional updates as we have more information.

Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]

May <var data-var='date'>15</var>, <var data-var='time'>03:51</var> UTC Resolved - We have identified the root cause of the migration delays affecting all regions. An unexpected reboot of several internal infrastructure components at approximately 22:10 UTC on May 14 resulted in incomplete reinitialization, causing the migration queue to stall.The affected components have now been reinitialized and migrations are processing normally. The pending queue has cleared and both cold and warm migrations as well as resize jobs are confirmed moving. May <var data-var='date'>15</var>, <var data-var='time'>02:24</var> UTC Investigating - We are currently investigating an issue causing delays to both cold and live migrations globally. A number of migrations are stuck, and additional migrations are queued and pending across all regions. Customer Impact: Cold and live migrations along with linode resize may be delayed or unresponsive. We recommend avoiding initiating new migrations and resizes until this is resolved. We are actively investigating the root cause and will provide an update shortly.

Investigating - Linode VM Migration Delays (All Regions)

May <var data-var='date'>15</var>, <var data-var='time'>17:30</var> UTC Update - We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions. We will provide another update when more OS images have been updated and/or additional attack vectors are discovered. [1] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/ [2] https://www.linode.com/docs/guides/dirty-frag-mitigation/ May <var data-var='date'>13</var>, <var data-var='time'>21:02</var> UTC Investigating - Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems. As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers. As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected. [1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/

[Fragnesia] Linux Privilege Escalation Vulnerability

May <var data-var='date'>13</var>, <var data-var='time'>14:37</var> UTC Resolved - We haven’t observed any additional connectivity issues in our NL-AMS data center, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance. May <var data-var='date'>13</var>, <var data-var='time'>10:44</var> UTC Monitoring - At this time we have been able to confirm that no customers should be impacted by the issues affecting connectivity in our NL-AMS data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance. May <var data-var='date'>13</var>, <var data-var='time'>09:42</var> UTC Investigating - Our team is investigating an issue affecting connectivity in our NL-AMS 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.

Connectivity Issue - NL-AMS

May <var data-var='date'>13</var>, <var data-var='time'>01:02</var> UTC Resolved - This incident has been resolved. While we continue to monitor the upstream provider's progress on their underlying connectivity issue, our services are now stable on alternative paths. May <var data-var='date'>12</var>, <var data-var='time'>22:47</var> UTC Update - We are continuing to work with our service provider on a fix for this issue. May <var data-var='date'>12</var>, <var data-var='time'>19:52</var> UTC Identified - Our third-party service provider has identified the issue affecting connectivity in our AP-West (Mumbai) and IN-MAA (Chennai) data centers, and a fix is being implemented. We will provide an update as soon as the solution is in place. May <var data-var='date'>12</var>, <var data-var='time'>17:54</var> UTC Update - We are continuing to investigate the issue with our service provider. We will share additional updates as we have more information. May <var data-var='date'>12</var>, <var data-var='time'>17:12</var> UTC Investigating - Our team is investigating an issue affecting connectivity in our AP-West (Mumbai) and IN-MAA (Chennai) data centers. During this time, users may experience intermittent connection timeouts and errors for all services deployed in these data centers. We will share additional updates as we have more information.

Connectivity Issue - AP-West (Mumbai) and IN-MAA (Chennai)

May <var data-var='date'>12</var>, <var data-var='time'>23:15</var> UTC Resolved - Our team became aware of an issue affecting the Cloud Pulse Metrics for Managed Databases (ACLP Metrics) for two short periods on May 12 and May 14, 2026, and a fix has been applied. We haven’t observed any additional issues with the ACLP Metrics service, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

Service Issue - ACLP Logs

May <var data-var='date'>15</var>, <var data-var='time'>17:28</var> UTC Update - We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions. We will provide another update when more OS images have been updated and/or additional attack vectors are discovered. [1] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/ [2] https://www.linode.com/docs/guides/dirty-frag-mitigation/ May <var data-var='date'> 9</var>, <var data-var='time'>14:40</var> UTC Update - We have updated our latest Linode kernel to version 7.0.5, which contains the upstream fix from kernel.org for the DirtyFrag vulnerabilities as well as the previous fixes for the recent CopyFail vulnerability. This kernel is available in Cloud Manager and we recommend customers using the Linode-compiled kernel update their configurations to this kernel. We are in parallel tracking the upstream Linux distributions and will provide another update when fixed versions have been released. May <var data-var='date'> 8</var>, <var data-var='time'>13:40</var> UTC Investigating - Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems. As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers. As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected. [1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/

[DirtyFrag] Linux Privilege Escalation Vulnerability

May <var data-var='date'> 5</var>, <var data-var='time'>22:19</var> UTC Resolved - We have completed our investigation and response to the “Copy Fail” Linux kernel local privilege escalation vulnerability (CVE-2026-31431). We have published a documentation article with detailed guidance on available mitigations and recommended actions for affected systems. Customers can find more information and step-by-step instructions here: https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/ We encourage all customers to review the article and apply the appropriate mitigations to their environments. If you have questions or need assistance, please contact us at 855-454-6633 (+1-609-380-7100 Intl.) or email support@linode.com for assistance. May <var data-var='date'> 1</var>, <var data-var='time'>17:52</var> UTC Update - We are continuing to investigate this issue. May <var data-var='date'> 1</var>, <var data-var='time'>17:51</var> UTC Investigating - Akamai is aware of the recently disclosed “Copy Fail” vulnerability (CVE-2026-31431). We are assessing the issue and are working to address it across our product portfolio and internal systems. While we have not observed any related malicious exploits targeting our infrastructure, Akamai continuously works to reduce risks and enhance our security posture. We are taking both immediate and longer-term steps to mitigate potential impacts and help ensure the continued confidence of our customers. Per our Shared Security Model[1], customers are responsible for making sure their service’s installed applications and code are securely configured and patched. Given the nature of this vulnerability, it should be assumed that all virtual machines running Linux are at-risk until patched. We will be publishing more details as patches are incorporated into the base images that we supply, but we strongly recommend customers deploy mitigations on all instances. Furthermore, the nature of the vulnerability suggests that container escapes are possible, so customers allowing untrusted workloads to execute in their containers may need to take additional steps to secure their containerized workloads. We will provide further information regarding our posture and recommended actions for Akamai Compute customers who may be affected. [1] https://www.akamai.com/legal/security

(Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]

May <var data-var='date'> 4</var>, <var data-var='time'>15:00</var> UTC Completed - The scheduled maintenance has been completed. May <var data-var='date'> 4</var>, <var data-var='time'>13:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'> 1</var>, <var data-var='time'>06:42</var> UTC Scheduled - On Monday, May 4th from 13:00 to 15:00 UTC, we will be performing network maintenance in our OSA region. While we do not expect any downtime, a brief period of increased latency or packet loss may occur during this window.

Emergency Network Maintenance - OSA

May <var data-var='date'> 4</var>, <var data-var='time'>03:43</var> UTC Resolved - The network component has been replaced. The incident is now resolved. Apr <var data-var='date'>29</var>, <var data-var='time'>22:13</var> UTC Update - We were able to identify a solution which resulted in additional capacity for the Chennai, IN region and did not experience any degradation over the peak hours on April 29, 2026, we anticipate this to be the case going forward, but will continue providing updates until we successfully replace the impacted network component. The replacement of the network component has been briefly delayed. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. Apr <var data-var='date'>28</var>, <var data-var='time'>21:35</var> UTC Update - Our team has identified the issue affecting connectivity in our Chennai (IN-MAA) data center as a degraded network component and are working to expedite replacement as quickly as possible. At this time there is no customer impact, but due to lessened capacity as a result of this hardware degradation, we do expect intermittent delays or timeouts during peak traffic hours in the Chennai (IN-MAA) region. The current ETA for replacing this hardware is end of day on April 29, 2026. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. Apr <var data-var='date'>28</var>, <var data-var='time'>17:17</var> UTC Identified - Our team is investigating an emerging service issue affecting the network and connectivity in our Chennai (IN-MAA) data center. Customers may see intermittent delays and timeouts during peak traffic hours in the region. If you are seeing impact that may be related, please <a href="https://cloud.linode.com/support/tickets?dialogOpen=true">open a Support Ticket</a>.

Service Issue - Connectivity Issues - Chennai (IN-MAA)

Apr <var data-var='date'>30</var>, <var data-var='time'>15:00</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>30</var>, <var data-var='time'>13:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>28</var>, <var data-var='time'>15:44</var> UTC Scheduled - On Thursday, April 30th from 13:00 to 15:00 UTC, we will be performing network maintenance in our AU-MEL region. While we do not expect any downtime, a brief period of increased latency or packet loss may occur during this window.

Emergency Network Maintenance - AU-MEL

Apr <var data-var='date'>29</var>, <var data-var='time'>19:19</var> UTC Resolved - We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance. Apr <var data-var='date'>29</var>, <var data-var='time'>12:41</var> UTC Update - We are continuing to investigate this issue. Apr <var data-var='date'>29</var>, <var data-var='time'>11:42</var> UTC Update - We are continuing to investigate this issue. Apr <var data-var='date'>29</var>, <var data-var='time'>10:30</var> UTC Update - Our team is investigating an issue affecting the Object Storage service. During this time, users may experience connection timeouts and errors with this service. Apr <var data-var='date'>29</var>, <var data-var='time'>09:22</var> UTC Investigating - We are aware that some customers have been experiencing 403 (InvalidAccessKeyId) errors when attempting to access object storage, beginning yesterday evening. We will share additional updates as we have more information.

Object Storage Key creation and validation failing with error 403 in multiple data centers

Apr <var data-var='date'>28</var>, <var data-var='time'>15:16</var> UTC Resolved - We haven’t observed any additional issues with the LKE and NodeBalancer services and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance. Apr <var data-var='date'>24</var>, <var data-var='time'>23:53</var> UTC Monitoring - At this time we have been able to correct the issues affecting the NodeBalancer service at 23:36 UTC on April 24, 2026. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a ticket</a> with our Support Team. Apr <var data-var='date'>24</var>, <var data-var='time'>23:06</var> UTC Update - We are continuing work to apply the identified fix the issue affecting the LKE and newly updated/created NodeBalancer configurations and we will provide an update as soon as the solution is in place. Apr <var data-var='date'>24</var>, <var data-var='time'>22:07</var> UTC Update - We are continuing work to apply the identified fix the issue affecting the LKE and newly updated/created NodeBalancer configurations and we will provide an update as soon as the solution is in place. Apr <var data-var='date'>24</var>, <var data-var='time'>21:46</var> UTC Update - Our team has identified the issue affecting the LKE and newly updated/created NodeBalancer configurations. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. Apr <var data-var='date'>24</var>, <var data-var='time'>20:48</var> UTC Update - Our team has identified that due to this issue, customers may also experience issues creating new nodebalancers. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. Apr <var data-var='date'>24</var>, <var data-var='time'>20:19</var> UTC Identified - Our team has identified the issue affecting the LKE service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. Apr <var data-var='date'>24</var>, <var data-var='time'>19:27</var> UTC Investigating - Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine (LKE) service across multiple regions. We will share additional updates as we have more information.

Service Issue - Linode Kubernetes Engine (LKE)

Apr <var data-var='date'>22</var>, <var data-var='time'>05:30</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>22</var>, <var data-var='time'>04:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>19</var>, <var data-var='time'>03:21</var> UTC Update - We will be undergoing scheduled maintenance during this time. Mar <var data-var='date'>19</var>, <var data-var='time'>03:20</var> UTC Update - We will be undergoing scheduled maintenance during this time. Mar <var data-var='date'>17</var>, <var data-var='time'>21:58</var> UTC Scheduled - Scheduled Maintenance — Cloud Manager, API, Cloud IAM and CLI April 22, 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.

Scheduled Maintenance – Cloud Manager, API, Cloud IAM and CLI

Apr <var data-var='date'>21</var>, <var data-var='time'>01:08</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>20</var>, <var data-var='time'>13:57</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>20</var>, <var data-var='time'>12:25</var> UTC Update - We are continuing to investigate this issue. Apr <var data-var='date'>20</var>, <var data-var='time'>11:49</var> UTC Investigating - Our team is investigating an emerging service issue impacting connectivity in Frankfurt (DE-FRA-2). We will share additional updates as we have more information.

Emerging Service Issue - Connectivity issues in Frankfurt (DE-FRA-2)

Apr <var data-var='date'>19</var>, <var data-var='time'>19:30</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>19</var>, <var data-var='time'>18:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>10</var>, <var data-var='time'>21:16</var> 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.

Maintenance for Linode Cloud Manager, API, and CLI

Apr <var data-var='date'>18</var>, <var data-var='time'>19:30</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>18</var>, <var data-var='time'>18:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>10</var>, <var data-var='time'>21:14</var> 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.

Apr <var data-var='date'>17</var>, <var data-var='time'>13:30</var> UTC Resolved - We haven’t observed any additional issues with the LKE and LKE-E services, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance. Apr <var data-var='date'>16</var>, <var data-var='time'>16:53</var> UTC Monitoring - As of 16:27 UTC on April 16, 2026 we have corrected the issues affecting the LKE service. The issue was caused by an expired certificate, which has been updated. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance. Apr <var data-var='date'>16</var>, <var data-var='time'>16:09</var> UTC Update - As of 15:53 UTC on April 16, 2026 we are starting to see nodes successfully provisioning, however the service is not fully back up yet. Some customers may remain impacted at this time. We are working to stabilize the service, and will provide another update within the next 30 minutes. Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI Apr <var data-var='date'>16</var>, <var data-var='time'>15:40</var> UTC Update - Our team continues to work on implementing a fix for the issue affecting the Linode Kubernetes Engine. We will continue to provide updates until a solution is in place. Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI Apr <var data-var='date'>16</var>, <var data-var='time'>15:10</var> UTC Identified - Our team has identified the issue affecting the LKE service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI Apr <var data-var='date'>16</var>, <var data-var='time'>14:41</var> UTC Update - Our team continues to investigate the issue affecting the Linode Kubernetes Engine (LKE). We will share additional updates as we have more information. Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI Apr <var data-var='date'>16</var>, <var data-var='time'>14:12</var> UTC Update - Our team continues to investigate the issue with the Linode Kubernetes Engine. Affected customers may be unable to deploy new clusters or add new nodes to a cluster. We will share additional updates as we have more information. Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI Apr <var data-var='date'>16</var>, <var data-var='time'>13:20</var> UTC Investigating - Our team is investigating an emerging service issue affecting Linode Kubernetes Engine Standard and Enterprise in all regions. We will share additional updates as we have more information.

Linode Kubernetes Engine Standard and Enterprise provisioning failures in all regions

Apr <var data-var='date'>16</var>, <var data-var='time'>19:32</var> UTC Resolved - We haven't observed any additional issues with the Dedicated CPU offering, 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 support@linode.com for assistance. Apr <var data-var='date'>15</var>, <var data-var='time'>22:40</var> UTC Update - We have identified a fix for the issue affecting the Dedicated CPU offering and are currently testing it. We expect to include the fix in the next software release that is expected to happen by the end of May. Our investigation shows that approximately 0.2% of hosts were impacted by this issue. In the meantime, a workaround is available by contacting support. We will provide additional updates as we approach the deployment date. Apr <var data-var='date'>14</var>, <var data-var='time'>20:45</var> UTC Identified - Our team has identified the issue affecting the Dedicated CPU offering. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. Apr <var data-var='date'>14</var>, <var data-var='time'>18:33</var> UTC Investigating - Our team is investigating a service issue that affects the Dedicated CPU offering. Some users may experience failed Linode boots, errors related to insufficient resource allocation, unsuccessful migrations of Dedicated CPU plans or scaling of LKE clusters, and difficulty deploying or scaling workloads that require Dedicated CPU resources. We will share additional updates as we have more information.

Service Issue - Dedicated CPU - Several Regions

Apr <var data-var='date'>15</var>, <var data-var='time'>20:21</var> UTC Resolved - 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 support@linode.com for assistance. Apr <var data-var='date'>15</var>, <var data-var='time'>18:35</var> UTC Monitoring - At this time we have been able to correct the issue affecting the Cloud Manager and API. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a>, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com. Apr <var data-var='date'>15</var>, <var data-var='time'>18:28</var> UTC Update - We are continuing to implement a fix, and we will provide an update as soon as the solution is in place. Apr <var data-var='date'>15</var>, <var data-var='time'>16:57</var> UTC Identified - Our team has identified the issue affecting the Cloud Manager and API. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. During this time, customers may be unable to create new Linodes, make changes to Cloud Firewalls, initiate migrations or resize operations. LKE autoscaling may also be delayed during this time.

Service Issue - Cloud Manager and API

Apr <var data-var='date'>14</var>, <var data-var='time'>07:30</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>14</var>, <var data-var='time'>05:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'> 9</var>, <var data-var='time'>08:22</var> UTC Scheduled - We will be performing scheduled maintenance on our servers responsible for Cloud Manager Analytics in Dallas starting at 05:30 UTC on April 14th, 2026. The maintenance period is expected to last 2 hours ending 07:30 UTC, April 14th, 2026. While existing graphs will continue to be displayed normally, please be aware that a slight delay in graph updates may be observed during the process.

Scheduled maintenance- Cloud Manager Analytics

Apr <var data-var='date'>13</var>, <var data-var='time'>16:00</var> UTC Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>13</var>, <var data-var='time'>14:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>13</var>, <var data-var='time'>14:00</var> UTC Scheduled - On Monday, April 13, 2026, starting at 2:00 PM UTC, We will be performing planned maintenance on the Linode Support Ticketing System. There is no expected downtime.

Is Linode down?

Linode status is UP

Lastest published events

Service Issue - Paris (FR-PAR3)

Emerging Service Issue - GPU Deployment

[Fragnesia] Linux Privilege Escalation Vulnerability

Linode Services, Components and Regions

Recent Linode events

Scheduled maintenance - Linode Kubernetes Engine (LKE)

Service Issue - Paris (FR-PAR3)

Emerging Service Issue - GPU Deployment

Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]

Investigating - Linode VM Migration Delays (All Regions)

[Fragnesia] Linux Privilege Escalation Vulnerability

Get your FREE account now,
5 monitors included!

Is Linode down?

Linode status is UP

Lastest published events

Service Issue - Paris (FR-PAR3)

Emerging Service Issue - GPU Deployment

[Fragnesia] Linux Privilege Escalation Vulnerability

Linode Services, Components and Regions

Recent Linode events

Scheduled maintenance - Linode Kubernetes Engine (LKE)

Service Issue - Paris (FR-PAR3)

Emerging Service Issue - GPU Deployment

Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]

Investigating - Linode VM Migration Delays (All Regions)

[Fragnesia] Linux Privilege Escalation Vulnerability

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!