Looking for an update now? Check the current status, or follow Linode for future changes.
83%of 53 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
82.8%
29
5
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
October 2026
Issue in creating new LKE Enterprise cluster across regions.
Our team has identified the issue affecting the LKE Enterprise service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
identified
We are currently investigating an issue affecting the provisioning of new LKE Enterprise (LKE-E) clusters across all regions. Affected clusters may experience nodes that successfully reach a "Ready" state, but system critical components may fail to start properly, preventing workloads from running.
identified
We are continuing to work on a fix for this issue.
identified
We are currently investigating an issue affecting the provisioning of new LKE Enterprise (LKE-E) clusters across all regions. Affected clusters may experience nodes that successfully reach a "Ready" state, but system critical components may fail to start properly, preventing workloads from running.
Akamai has completed patching Compute hypervisors for the known vulnerabilities related to CVE-2026-99999, also referred to as “PwnEscape”, and we have not identified any exploitation on the Akamai platform.
We recommend that customers upgrade Linode guest VMs using kernels from upstream OS vendors as those become available, especially for cases where less trusted workloads are being run within containers or nested virtualization. We are in the process of preparing images containing fixes from upstream vendors.
identified
We have not identified any exploitation on the Akamai platform so far. As of now, our subject matter experts are continuing to work on patching server sets in phases across the Akamai platform. We are actively monitoring our platform while we perform the mitigation actions.
identified
Akamai is aware of the recently published Guest-to-Host KVM Escape (CVE-2026-99999) vulnerability. Our teams have proactively identified its potential impact and are actively applying mitigations across our platform and infrastructure. There is potential for customer workload impact as a part of our platform response to this vulnerability. At this time, we have not observed evidence of this vulnerability being actively exploited on our platform. We will provide updates as additional information becomes available.
At this time we have been able to correct the issue affecting the Cloud Manager logins. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to receive verification codes please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a>, call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com.
identified
Our team has identified the issue affecting Cloud Manager logins, where customers may not receive verification codes in some scenarios. We are working quickly to implement a fix and will provide an update as soon as the solution is in place.
Service Issue - Object Storage - US-Southeast (Atlanta)
At this time we have been able to correct the issues affecting the Object Storage service. 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.
investigating
Our team is investigating an issue affecting the Object Storage for the US-Southeast (Atlanta) region. During this time, users may experience connection timeouts and errors with this service.
Our team is investigating a service issue that affects the Cloud Manager (https://cloud.linode.com/) and API. During that time, some users may experience issues when attempting to access these systems. We will share additional updates as we have more information.
Our team is investigating an emerging service issue intermittently affecting Cloud Manager and API. We will share additional updates as we have more information.
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.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
Our team is investigating a service issue that affects the Cloud Manager (https://cloud.linode.com/) and API. During that time, some users may experience issues when attempting to access these systems. We will share additional updates as we have more information.
We are currently deploying a fix for this issue in phases, which will take several months to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
identified
We are currently deploying a fix for this issue in phases, which will take several months to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
identified
We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
identified
We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
identified
We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
identified
We are currently deploying a fix for this issue in phases, which will take several days to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
identified
We are currently deploying a fix for this issue in phases, which will take several days to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
identified
We are continuing to test the fix before initiating the rollout. Further updates regarding the status of the mitigation efforts will be provided as progress is made.
identified
We are continuing to test the fix before initiating the rollout. Further updates regarding the status of the mitigation efforts will be provided as progress is made.
identified
We have successfully identified a solution to address the issue at hand. We are currently in the testing phase prior to initiating the rollout of the fix. Further updates regarding the status of the mitigation efforts will be provided as progress is made.
identified
We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.
identified
We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.
identified
We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.
identified
Our team has identified the issue affecting booting up GPU and VPU plans. 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 booting up GPU plans. We will share additional updates as we have more information.
Legacy Incident Archive
52 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
Emerging Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]
Source not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix has been implemented.
investigating
We are continuing to investigate this issue.
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.
Investigating - Linode VM Migration Delays (All Regions)
Source not attested
Last archived state: resolved
View archived record details
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.
[Fragnesia] Linux Privilege Escalation Vulnerability
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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] h...
investigating
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] h...
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 ...
Connectivity Issue - NL-AMS
minorSource not attested
Last archived state: resolved
View archived record details
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.
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 - AP-West (Mumbai) and IN-MAA (Chennai)
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work with our service provider on a fix for this issue.
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.
investigating
We are continuing to investigate the issue with our service provider. We will share additional updates as we have more information.
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.
[DirtyFrag] Linux Privilege Escalation Vulnerability
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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] h...
investigating
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] h...
investigating
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.
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 distribu...
(Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
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 custom...
April 2026
Object Storage Key creation and validation failing with error 403 in multiple data centers
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
Our team is investigating an issue affecting the Object Storage service. During this time, users may experience connection timeouts and errors with this service.
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.
Service Issue - Connectivity Issues - Chennai (IN-MAA)
minorSource not attested
Last archived state: resolved
View archived record details
identified
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 p...
identified
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 ...
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 - Linode Kubernetes Engine (LKE)
minorSource not attested
Last archived state: resolved
View archived record details
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.
identified
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.
identified
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.
identified
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.
identified
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.
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.
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.
