checked Nov 4, 2026 12:20 PM UTC · Linode's official status page
Linode is up and running.
All components operational
Get email updates for the reported Linode status changes you choose. Follow your other dependencies in the same workspace.
30-day free trial, no card needed. First-time customers; continued monitoring requires a paid subscription.
18 reports published by Linode in the last 30 days · 5 still open
When Linode breaks, it is typically resolved in 18h 26m — median across 7 resolved incidents over 30 days.
resolvedNov 2 · 20:53 UTC
We haven’t observed any additional connectivity issues in our FR-PAR-2 data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Reported by Linode on their status page.
resolvedNov 1 · 19:52 UTC
This incident has been resolved.
Reported by Linode on their status page.
investigatingOct 31 · 20:17 UTC
We are continuing to investigate the issue. We will share additional details as soon as we have them.
Reported by Linode on their status page.
investigatingNov 2 · 10:55 UTC
While we continue to deploy kernel patches across our infrastructure, we have also deployed network rules that drop IPv4 packets with optional headers on public and VPC interfaces. This eliminates the immediate remote attack vector and protects our infrastructure as well as customer workloads without impacting performance or functionality, and notably is not limited to only focusing on the MPTCP exploit, but the underlying vulnerability. We continue to track upstream OS provider security releases and will make updated distributions available to customers as they are released. Customers using the Linode provided kernel are likewise advised to deploy the latest version when it becomes available as well.
Reported by Linode on their status page.
monitoringOct 28 · 20:18 UTC
A fix has been implemented and we are monitoring the results.
Reported by Linode on their status page.
monitoringOct 29 · 09:16 UTC
We will continue to monitor to ensure that the impact has been fully mitigated. Further updates will be provided as we make progress.
Reported by Linode on their status page.
resolvedOct 23 · 20:38 UTC
This issue is considered resolved.
Reported by Linode on their status page.
investigatingOct 22 · 20:08 UTC
Akamai is aware of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479), and our teams are actively investigating their potential impact across our platform and infrastructure. F5 has released out-of-band security patches addressing three critical severity vulnerabilities in NGINX Open Source and NGINX Plus. These vulnerabilities may allow unauthenticated attackers to trigger heap buffer overflows, which could cause a denial of service or potential remote code execution if ASLR is bypassed. If you are running a vulnerable version of NGINX Open Source or NGINX Plus on a Linode instance, we recommend following guidance from F5/NGINX and applying available patches. We will provide updates as additional information becomes available.
Reported by Linode on their status page.
postmortemOct 22 · 16:00 UTC
On October 22, 2026, starting around 11:10 UTC, a new Debian Kubernetes image was made available. The metadata for that image included malformed data, which resulted in Linode provisioning failures on LKE clusters due to validation errors. Akamai immediately began investigating the issue and working to correct it. We corrected the malformed data at 12:50 UTC on October 22, 2026 and service was restored. 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.
Reported by Linode on their status page.
postmortemOct 29 · 08:40 UTC
On October 10, 2026, Akamai became aware of two zero-day remote code execution (RCE) vulnerabilities affecting the PHP core engine, tracked as CVE-2026-109618 and CVE-2026-109619. Akamai began a platform-wide investigation, and deployed global Web Application Firewall (WAF) mitigation rules on October 21, 2026, and carried out remediation protocols across potentially impacted infrastructure.
At this time, Akamai has observed no evidence that these vulnerabilities impacted core Akamai products, API calls, or the Akamai Control Center (ACC). The potential scope included PHP Core, Linode Speed Test Services, and Quick Deploy Marketplace applications. As a precaution, Akamai temporarily disabled Cloud Infrastructure Speed Tests while teams isolated and rebuilt related systems.
Akamai deployed protective WAF rules across the Akamai edge platform to inspect and mitigate potential exploitation attempts. Marketplace application templates were also updated so new Linode Compute Marketplace deployments automatically use patched PHP packages. The existing customer-managed instances running vulnerable PHP versions require customer action to apply the latest official security updates from the upstream PHP project.
Customers using Akamai App & API Protector or Kona Site Defender should confirm that default protective rule sets are active. Customers running PHP on Linode compute instances or other self-managed infrastructure should update PHP packages as soon as possible. The external asset scans confirmed that Akamai production environments remained secured and protected.
Akamai's public security notice is available here.
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.
Reported by Linode on their status page.
postmortemOct 21 · 15:49 UTC
Starting October 17, 2026, customers were unable to create new Linode Kubernetes Engine-Enterprise \(LKE-E\) clusters globally. The impact was limited to newly provisioned LKE-E clusters, while the existing clusters, ongoing customer workloads, and cluster scaling remained fully functional and were unaffected throughout the event. Investigation revealed that the impact occurred after Linode Virtual Private Cloud \(VPC\) subnet IDs crossed 1,000,000 \(one million\), following growth on October 17, 2026. Due to a software logic flaw, the Cloud Controller Manager parsed these 7-digit IDs into scientific notation instead of raw integers, rendering the IDs invalid and causing required core components to remain pending on newly created clusters. To mitigate the issue, Akamai deployed a fix to enforce strict integer formatting and patched existing custom resources to restore the affected clusters. Akamai’s internal testing confirmed that the newly provisioned test clusters were fully operational. With the successful testing, Akamai deployed the fix across the platform, and the impact was considered mitigated at around 19:49 UTC on October 20, 2026. Akamai is working on the root cause and will take appropriate preventive actions. We apologize for the impact and thank you for your patience and continued support. This summary reflects our current understanding of the incident based on available details. Our investigation remains ongoing, and findings may be updated as further information is reviewed.
Reported by Linode on their status page.
postmortemOct 26 · 19:33 UTC
Beginning at approximately 14:23 UTC on October 19, 2026, as part of a planned internal maintenance, we migrated too many of the same routing resources at the same time. This resulted in route instability in certain network segments until the migration completed and routes were adopted and converged at 14:55 UTC on October 19, 2026. To prevent this issue from reoccurring, we are modifying our maintenance planning process to ensure that critical components are taken offline in a phased manner that doesn’t introduce customer impact. 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.
Reported by Linode on their status page.
resolvedOct 30 · 15:06 UTC
We have completed our investigation and response to the “PwnEscape” Guest-to-Host Escape vulnerability (CVE-2026-99999). We have published a documentation article with detailed guidance on available mitigations and recommended actions for affected systems: https://www.akamai.com/cloud/guides/cve-2026-99999-pwnescape-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 open a Support ticket, or contact us at 855-454-6633 (+1-609-380-7100 Intl.) / support@linode.com.
Reported by Linode on their status page.
resolvedOct 16 · 12:20 UTC
The maintenance has been completed. New customer signup and account creation are fully restored.
Reported by Linode on their status page.
resolvedOct 13 · 08:03 UTC
We haven't observed any additional issues with the Cloud Manager logins, and will now consider this incident resolved. If you continue to experience issues receiving verification codes, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.
Reported by Linode on their status page.
CompletedOct 7 · 16:00 UTC
The scheduled maintenance has been completed.
Reported by Linode on their status page.
CompletedOct 7 · 13:00 UTC
The scheduled maintenance has been completed.
Reported by Linode on their status page.
resolvedOct 8 · 21:26 UTC
We haven’t observed any additional issues with GPU plans, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Reported by Linode on their status page.
