Live status · checked every 15 minutes
Is Akamai Linode down right now?
Linode, now Akamai Cloud Computing, offers virtual servers, Kubernetes and object storage.
Live reader reports
Is Akamai Linode down for you?
Tap what's not working, or tell us it works. Reports are anonymous, one per visitor.
No reports in the last 24 hours. Be the first to tell other readers what you're seeing.
Akamai Linode not working for you?
- Check the region or product you use on the official status page: many incidents only hit one region.
- Test your site from another network, or with an online "check website" tool, to rule out your own connection.
- Read the exact error code in your logs: 5xx errors point to the provider, 4xx errors usually to your setup.
- Retry deployments and API calls with backoff instead of hammering the service.
Akamai Linode outage history
Last 30 daysFixed Service Issue - Cloud Manager and API
Affected: Cloud Manager and API
-
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.
-
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.
Fixed Customer Security Advisory: OpenSSH Password Authentication Bypass Vulnerability [CVE-2026-123158]
Affected: Linode.com
-
Akamai is aware of the password authentication bypass vulnerability affecting certain Linux systems using musl libc that was recently mitigated by an urgent OpenSSH update. Since Alpine Linux is specifically called out as being affected, we wanted to assure customers that Linode’s Alpine images are not affected by this vulnerability. Linodes using password-less provisioning do not have password authentication enabled by default unless customers change this configuration option in sshd_config after launch, while linodes launched using a password do not have any unlocked user accounts with a password hash set to ‘*’. However, we would like to use this opportunity as a reminder for customers to consider disabling password authentication permanently in favor of more secure mechanisms such as SSH keys or SSH CA certificates.
Fixed Emerging Host Issue
Affected: Linode.com
-
We have implemented a fix, and after a period of monitoring, we can confirm that this incident is resolved as of 14:09 UTC on November 5, 2026. If you are still experiencing additional issues, please open a Support ticket for assistance.
-
The issue affecting Linode migrations and booting for some hosts across all regions has been identified and a fix is being implemented. We will continue to share updates as more information becomes available.
-
We are currently investigating issues affecting Linode migrations and booting for some hosts across all regions. Our team is actively working on a resolution. We will share additional updates as we have more information.
Fixed Connectivity Issue - FR-PAR-2 (Paris 2)
Affected: FR-PAR-2 (Paris 2), Regions - FR-PAR-2 (Paris 2)
-
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.
-
We are continuing to investigate the issue.
-
Our team is investigating an issue affecting connectivity in our FR-PAR-2 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.
Fixed Connectivity Issue - IN-MAA and IN-BOM-2
Affected: IN-MAA (Chennai), IN-BOM-2 (Mumbai 2), Regions - IN-MAA (Chennai), Regions - IN-BOM-2 (Mumbai 2)
-
This incident has been resolved.
-
A fix has been implemented and we are monitoring the results.
-
Our team is investigating an issue affecting connectivity in our IN-MAA (Chennai) and IN-BOM-2 (Mumbai 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.
Fixed Customer Security Advisory: CVE-2026-98432
Affected: Customer Security Advisory, Customer Service, Documentation and Community - Customer Security Advisory
-
We continue to monitor our systems and track upstream OS providers’ security releases; as of November 9, 2026, the majority of upstream vendors have provided updated kernel packages that include fixes for this vulnerability, and we recommend customers apply those updates to their Linodes. Customers using the Linode provided kernel are likewise advised to deploy the latest version as indicated on our kernels page. By applying IPv4 network rules to both public and VPC interfaces, we have already eliminated the immediate remote attack vector, addressing the root vulnerability rather than just the MPTCP exploit. We remain committed to improving our systems and reducing the risk of similar issues in the future.
-
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.
-
We are in the process of deploying mitigations for the underlying known attack vector while we continue to analyze any other possible impact. Customers are strongly advised to apply OS updates from their upstream provider to their workloads as soon as those become available. At this time, we have no evidence of this vulnerability being exploited on the Akamai Compute platform.
-
We are continuing to investigate this issue. The appropriate subject matter experts are engaged. Subsequent updates around mitigation status will be posted as progress is made.
-
Akamai is aware of the recently published remote code execution CVE-2026-98432. We are actively investigating and taking the appropriate mitigation actions, while we continue to monitor our platform in parallel. If you have questions or are experiencing an impact due to this issue, please reach out to us in a ticket at https://cloud.linode.com/support.
Ongoing Service Issue - Block Storage (BR-GRU)
Affected: BR-GRU (São Paulo) Block Storage, Block Storage - BR-GRU (São Paulo) Block Storage
-
A fix has been implemented and we are monitoring the results.
-
Our team is investigating an issue affecting the Block Storage service in our BR-GRU (São Paulo) data center. During this time, Block Storage volume creation, deletion and cloning may fail. We will share additional updates as we have more information.
Fixed Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)
Affected: ID-CGK (Jakarta), SG-SIN-2 (Singapore 2), Regions - ID-CGK (Jakarta), Regions - SG-SIN-2 (Singapore 2)
-
Starting around 07:00 UTC on October 24, 2026, an issue affecting connectivity between our ID-CGK \(Jakarta\) and SG-SIN-2 \(Singapore 2\) was identified. The investigation revealed that the issue was caused by an undersea cable cut affecting the international link capacity, which would have resulted in connection timeouts and/or errors for services deployed in these data centers. To mitigate the immediate impact while the undersea cable was being repaired, we removed the affected links from production traffic and limited the link capacity; network stability was restored following these actions. The impact was fully mitigated at 17:50 UTC on November 13, 2026, once the undersea cable repairs were finished and all previous changes were reverted. We apologize for the impact and thank you for your patience and continued support. If you have further questions, please contact us at 855-454-6633 \(\+1-609-380-7100 Intl.\), or send an email to [support@linode.com](mailto:support@linode.com) for assistance. 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.
-
We haven’t observed any additional connectivity issues in our ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) data centers, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
-
We will continue to monitor to ensure that the impact has been fully mitigated. Further updates will be provided as we make progress.
-
We are continuing to monitor for any further issues.
-
At this time, we have been able to correct the issues affecting connectivity between our ID-CGK (Jakarta) and SG-SIN-2 (Singapore 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.
-
We are continuing to investigate this issue. We will share additional updates as we have more information.
-
Our team is investigating an issue affecting connectivity between our ID-CGK (Jakarta) and SG-SIN-2 (Singapore 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.
Fixed Connectivity Issue - Dallas Data Center (IPv6 Traffic to Google)
Affected: US-Central (Dallas), Regions - US-Central (Dallas)
-
This issue is considered resolved.
-
This was identified to be an upstream issue and should be resolved at this time, we will continue to monitor to ensure things remain stable.
-
Our team is currently investigating a connectivity issue in our Dallas data center. This is strictly affecting traffic routed via IPv6 to Google and its associated products, which may cause intermittent connection timeouts. We will post further updates as soon as more information becomes available.
Fixed Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities
Affected: Customer Security Advisory, Customer Service, Documentation and Community - Customer Security Advisory
-
Akamai has completed its investigation of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479). We have not identified any impact to Akamai’s platform or infrastructure. If you run a vulnerable version of NGINX Open Source or NGINX Plus on a Linode instance, follow F5/NGINX guidance and apply the available patches. No further updates are planned for this notice.
-
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.
Fixed Service Issue - Linode Kubernetes Engine
Affected: US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont) Linode Kubernetes Engine, US-Southeast (Atlanta) Linode Kubernetes Engine, US-IAD (Washington) Linode Kubernetes Engine, US-ORD (Chicago) Linode Kubernetes Engine, CA-Central (Toronto) Linode K...
-
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.
-
Our team identified an issue affecting the Linode Kubernetes Engine (LKE). During the impact timeframe (~11:10-12:50 UTC), new worker nodes were unable to provision. We have been able to correct the issues affecting the LKE service and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Fixed Customer Security Advisory: PHP Remote Code Execution Vulnerabilities
-
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](https://www.akamai.com/blog/security-research/critical-remote-code-execution-vulnerabilities-php-core). 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.
-
Akamai has completed its assessment of the recently published PHP remote code execution vulnerabilities (CVE-2026-109618 and CVE-2026-109619) across our platform and infrastructure, and mitigation efforts are complete. Cloud Infrastructure Speed Tests will remain offline in the near term. We plan to bring them back online in the near future. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We appreciate your patience while our teams completed this work.
-
Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, our Cloud Infrastructure Speed Tests will be unavailable. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We will provide updates as additional information becomes available.
-
Updated Guidance after assessment: Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, our Cloud Infrastructure Speed Tests will be unavailable. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We will provide updates as additional information becomes available.
-
Akamai is aware of the recently published (CVE-2026-109618 and CVE-2026-109619) vulnerabilities and our teams are actively investigating its potential impact across our platform and infrastructure. As a part of ongoing mitigation efforts, some Quick Deploy Apps, speed test pages, and parts of the website may be unavailable. If you are running a vulnerable version of PHP on a Linode instance, we recommend following guidance from the upstream vendor (PHP) and applying upstream patches as they become available. We will provide updates as additional information becomes available.
Frequently asked questions
Is Akamai Linode down right now?
No. As of 20:15 UTC on 19 November 2026, Akamai Linode is working normally. If it is not working for you, try the checklist on this page.
When was the last Akamai Linode outage?
The last incident was "Service Issue - Cloud Manager and API" on 17 November 2026, fixed after 15 minutes 33 seconds.
Why is Akamai Linode not working for me?
If this page shows no problem and few readers report one, the cause is usually local: your connection, a VPN or firewall, an outdated app or a sign-in problem. Work through the checklist above, then report it here so other readers can see it.
Unofficial status page. Teczpert is not affiliated with Akamai Linode. Status data comes from the official status page and is checked every 15 minutes; reports come from readers. Official source: status.linode.com.