OpenUptime
Operational

Is Linode down?

Linode is up and running. Linode, now part of Akamai, rents virtual machines and storage.

Linode status on October 22, 2026: checked 01:24 UTC on the official status page. Refreshed at most every 5 minutes.

Official status page ↗Visit Linode ↗Live reports on X ↗

Last 90 days

54.78%
Estimated uptime
90 days agoToday

Worked out from the incidents Linode reported, so it is an estimate and not a measurement.

Linode reliability, last 90 days

9Incidents reported
0Full outages
2 h 53 minTypical duration
4 d 4 hLongest incident

Last incident: “Issue in creating new LKE Enterprise cluster across regions”, yesterday.

Customer Security Advisory: PHP Remote Code Execution Vulnerabilities

identified
identified2026-10-21 17:41 UTC

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.

investigating2026-10-21 14:44 UTC

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.

(PwnEscape) Guest-to-Host KVM Escape [CVE-2026-99999]

identified
identified2026-10-17 05:07 UTC

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.

identified2026-10-16 08:53 UTC

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.

identified2026-10-15 17:27 UTC

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.

Components

US-East (Newark)Operational
Linode.comOperational
US-East (Newark) Block StorageOperational
US-East (Newark) NodeBalancersOperational
US-East (Newark) BackupsOperational
US-East (Newark) Object StorageOperational
US-East (Newark) Linode Kubernetes EngineOperational
US-East (Newark)Operational
Akamai Cloud Pulse (ACLP) - AlertsOperational
Cloud Manager and APIOperational
US-Central (Dallas)Operational
US-Central (Dallas) Block StorageOperational
US-Central (Dallas) NodeBalancersOperational
US-Central (Dallas) BackupsOperational
US-Central (Dallas) Linode Kubernetes EngineOperational
US-Southeast (Atlanta) Object StorageOperational
US-Central (Dallas)Operational
Akamai Cloud Pulse (ACLP) - LogsOperational
US-West (Fremont)Operational
Hosted DNS ServiceOperational
US-West (Fremont) Block StorageOperational
US-West (Fremont) NodeBalancersOperational
US-West (Fremont) BackupsOperational
US-West (Fremont) Linode Kubernetes EngineOperational
US-IAD (Washington) Object StorageOperational
US-West (Fremont)Operational
Akamai Cloud Pulse (ACLP) - MetricsOperational
US-Southeast (Atlanta)Operational
US-Southeast (Atlanta) NodeBalancersOperational
US-Southeast (Atlanta) BackupsOperational
LongviewOperational
US-Southeast (Atlanta) Block StorageOperational
US-Southeast (Atlanta) Linode Kubernetes EngineOperational
US-ORD (Chicago) Object StorageOperational
US-Southeast (Atlanta)Operational
EU-Central (Frankfurt) Object StorageOperational
Managed DatabasesOperational
US-IAD (Washington)Operational
US-IAD (Washington) BackupsOperational
US-IAD (Washington) Block StorageOperational
US-IAD (Washington) NodeBalancersOperational
US-IAD (Washington) Linode Kubernetes EngineOperational
US-IAD (Washington)Operational
AP-South (Singapore) Object StorageOperational
US-ORD (Chicago)Operational
US-ORD (Chicago) BackupsOperational
US-ORD (Chicago) Block StorageOperational
US-ORD (Chicago) NodeBalancersOperational
US-ORD (Chicago) Linode Kubernetes EngineOperational
US-ORD (Chicago)Operational
CA-Central (Toronto)Operational
CA-Central (Toronto) Block StorageOperational
CA-Central (Toronto) NodeBalancersOperational
CA-Central (Toronto) BackupsOperational
CA-Central (Toronto) Linode Kubernetes EngineOperational
FR-PAR (Paris) Object StorageOperational
CA-Central (Toronto)Operational
EU-West (London)Operational
EU-West (London) Block StorageOperational
EU-West (London) NodeBalancersOperational
EU-West (London) BackupsOperational
EU-West (London) Linode Kubernetes EngineOperational
SE-STO (Stockholm) Object StorageOperational
EU-West (London)Operational
EU-Central (Frankfurt)Operational
EU-Central (Frankfurt) Block StorageOperational
EU-Central (Frankfurt) NodeBalancersOperational
EU-Central (Frankfurt) BackupsOperational
EU-Central (Frankfurt) Linode Kubernetes EngineOperational
US-SEA (Seattle) Object StorageOperational
EU-Central (Frankfurt)Operational
FR-PAR (Paris)Operational
FR-PAR (Paris) BackupsOperational
FR-PAR (Paris) Block StorageOperational
FR-PAR (Paris) NodeBalancersOperational
FR-PAR (Paris) Linode Kubernetes EngineOperational
JP-OSA (Osaka) Object StorageOperational
FR-PAR (Paris)Operational
AP-South (Singapore)Operational
AP-South (Singapore) Block StorageOperational
AP-South (Singapore) NodeBalancersOperational
AP-South (Singapore) BackupsOperational
AP-South (Singapore) Linode Kubernetes EngineOperational
IN-MAA (Chennai) Object StorageOperational
AP-South (Singapore)Operational
AP-Northeast-2 (Tokyo 2)Operational
AP-Northeast-2 (Tokyo 2) NodeBalancersOperational
AP-Northeast-2 (Tokyo 2) BackupsOperational
AP-Northeast-2 (Tokyo 2) Block StorageOperational
AP-Northeast (Tokyo 2) Linode Kubernetes EngineOperational
ID-CGK (Jakarta) Object StorageOperational
AP-Northeast-2 (Tokyo 2)Operational
AP-West (Mumbai)Operational
AP-West (Mumbai) Block StorageOperational
AP-West (Mumbai) NodeBalancersOperational
AP-West (Mumbai) BackupsOperational
AP-West (Mumbai) Linode Kubernetes EngineOperational
BR-GRU (Sao Paulo) Object StorageOperational
AP-West (Mumbai)Operational
AP-Southeast (Sydney)Operational
AP-Southeast (Sydney) NodeBalancersOperational
AP-Southeast (Sydney) BackupsOperational
AP-Southeast (Sydney) Linode Kubernetes EngineOperational
AP-Southeast (Sydney) Block StorageOperational
ES-MAD (Madrid) Object StorageOperational
AP-Southeast (Sydney)Operational
SE-STO (Stockholm)Operational
SE-STO (Stockholm) BackupsOperational
SE-STO (Stockholm) Block StorageOperational
SE-STO (Stockholm) NodeBalancersOperational
SE-STO (Stockholm) Linode Kubernetes EngineOperational
SE-STO (Stockholm)Operational
US-SEA (Seattle)Operational
US-SEA (Seattle) BackupsOperational
US-SEA (Seattle) Block StorageOperational
US-SEA (Seattle) NodeBalancersOperational
US-SEA (Seattle) Linode Kubernetes EngineOperational
US-SEA (Seattle)Operational
IT-MIL (Milan)Operational
JP-OSA (Osaka) BackupsOperational
JP-OSA (Osaka) Block StorageOperational
JP-OSA (Osaka) NodeBalancersOperational
JP-OSA (Osaka) Linode Kubernetes EngineOperational
GB-LON (London 2)Operational
IT-MIL (Milan)Operational
JP-OSA (Osaka)Operational
IN-MAA (Chennai) BackupsOperational
IN-MAA (Chennai) Block StorageOperational
IN-MAA (Chennai) NodeBalancersOperational
IN-MAA (Chennai) Linode Kubernetes EngineOperational
AU-MEL (Melbourne)Operational
JP-OSA (Osaka)Operational
IN-MAA (Chennai)Operational
ID-CGK (Jakarta) Linode Kubernetes EngineOperational
BR-GRU (São Paulo) BackupsOperational
BR-GRU (São Paulo) Block StorageOperational
BR-GRU (São Paulo) NodeBalancersOperational
NL-AMS (Amsterdam) Object StorageOperational
IN-MAA (Chennai)Operational
ID-CGK (Jakarta)Operational
NL-AMS (Amsterdam) BackupsOperational
NL-AMS (Amsterdam) Block StorageOperational
NL-AMS (Amsterdam) NodeBalancersOperational
IT-MIL (Milan) Object StorageOperational
BR-GRU (São Paulo) Linode Kubernetes EngineOperational
ID-CGK (Jakarta)Operational
BR-GRU (São Paulo)Operational
ES-MAD (Madrid) BackupsOperational
ES-MAD (Madrid) Block StorageOperational
ES-MAD (Madrid) NodeBalancersOperational
US-MIA (Miami) Object StorageOperational
NL-AMS (Amsterdam) Linode Kubernetes EngineOperational
BR-GRU (São Paulo)Operational
NL-AMS (Amsterdam)Operational
IT-MIL (Milan) BackupsOperational
IT-MIL (Milan) Block StorageOperational
IT-MIL (Milan) NodeBalancersOperational
US-LAX (Los Angeles) Object StorageOperational
ES-MAD (Madrid) Linode Kubernetes EngineOperational
NL-AMS (Amsterdam)Operational
US-MIA (Miami)Operational
US-MIA (Miami) BackupsOperational
US-MIA (Miami) Block StorageOperational
US-MIA (Miami) NodeBalancersOperational
GB-LON (London 2) Object StorageOperational
IT-MIL (Milan) Linode Kubernetes EngineOperational
US-MIA (Miami)Operational
US-LAX (Los Angeles)Operational
ID-CGK (Jakarta) BackupsOperational
ID-CGK (Jakarta) Block StorageOperational
ID-CGK (Jakarta) NodeBalancersOperational
AU-MEL (Melbourne) Object StorageOperational
US-MIA (Miami) Linode Kubernetes EngineOperational
US-LAX (Los Angeles)Operational
ES-MAD (Madrid)Operational
US-LAX (Los Angeles) BackupsOperational
US-LAX (Los Angeles) Block StorageOperational
US-LAX (Los Angeles) NodeBalancersOperational
IN-BOM-2 (Mumbai 2) Object StorageOperational
US-LAX (Los Angeles) Linode Kubernetes EngineOperational
ES-MAD (Madrid)Operational
AU-MEL (Melbourne)Operational
GB-LON (London 2) BackupsOperational
GB-LON (London 2) Block StorageOperational
GB-LON (London 2) NodeBalancersOperational
DE-FRA-2 (Frankfurt 2) Object StorageOperational
GB-LON (London 2) Linode Kubernetes EngineOperational
AU-MEL (Melbourne)Operational
GB-LON (London 2)Operational
AU-MEL (Melbourne) BackupsOperational
AU-MEL (Melbourne) Block StorageOperational
AU-MEL (Melbourne) NodeBalancersOperational
SG-SIN-2 (Singapore 2) Object StorageOperational
AU-MEL (Melbourne) Linode Kubernetes EngineOperational
GB-LON (London 2)Operational
IN-BOM-2 (Mumbai 2)Operational
IN-BOM-2 (Mumbai 2) BackupsOperational
IN-BOM-2 (Mumbai 2) Block StorageOperational
IN-BOM-2 (Mumbai 2) NodeBalancersOperational
JP-TYO-3 (Tokyo 3) Object StorageOperational
IN-BOM-2 (Mumbai 2) Linode Kubernetes EngineOperational
IN-BOM-2 (Mumbai 2)Operational
SG-SIN-2 (Singapore 2)Operational
DE-FRA-2 (Frankfurt 2) BackupsOperational
DE-FRA-2 (Frankfurt 2) Block StorageOperational
DE-FRA-2 (Frankfurt 2) NodeBalancersOperational
DE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineOperational
SG-SIN-2 (Singapore 2)Operational
DE-FRA-2 (Frankfurt 2)Operational
SG-SIN-2 (Singapore 2) BackupsOperational
SG-SIN-2 (Singapore 2) Block StorageOperational
SG-SIN-2 (Singapore 2) NodeBalancersOperational
SG-SIN-2 (Singapore 2) Linode Kubernetes EngineOperational
DE-FRA-2 (Frankfurt 2)Operational
JP-TYO-3 (Tokyo 3)Operational
JP-TYO-3 (Tokyo) BackupsOperational
JP-TYO-3 (Tokyo 3) Block StorageOperational
JP-TYO-3 (Tokyo 3) NodeBalancersOperational
JP-TYO-3 (Tokyo 3) Linode Kubernetes EngineOperational
JP-TYO-3 (Tokyo 3)Operational
ZA-JNB (Johannesburg)Operational
ZA-JNB (Johannesburg)Operational
NZ-AKL (Auckland)Operational
NZ-AKL (Auckland)Operational
CO-BOG (Bogota)Operational
CO-BOG (Bogota)Operational
US-DEN (Denver)Operational
US-DEN (Denver)Operational
DE-HAM (Hamburg)Operational
DE-HAM (Hamburg)Operational
US-HOU (Houston)Operational
US-HOU (Houston)Operational
MY-KUL (Kuala Lumpur)Operational
MY-KUL (Kuala Lumpur)Operational
FR-MRS (Marseille)Operational
FR-MRS (Marseille)Operational
MX-QRO (Queretaro)Operational
MX-QRO (Queretaro)Operational
CL-SCL (Santiago)Operational
CL-SCL (Santiago)Operational
FR-PAR-2 (Paris 2)Operational
US-IAD-2 (Washington 2)Operational

Recent incidents

Issue in creating new LKE Enterprise cluster across regions

Degraded

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.

Connectivity Issue - US-ORD

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

Maintenance - Akamai Cloud Login Service

The maintenance has been completed. New customer signup and account creation are fully restored.

Service Issue - Cloud Manager and API

Degraded

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.

Service Issue - Object Storage - US-Southeast (Atlanta)

Degraded

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 open a Support ticket for assistance.

Questions

Is Linode down right now?

Linode’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.

When was Linode last down?

The most recent incident Linode reported was “Issue in creating new LKE Enterprise cluster across regions”, yesterday (2026-10-20 12:29 UTC). None of its incidents in the last 90 days were a full outage.

Which parts of Linode are tracked here?

Linode reports 242 components on its status page, including US-East (Newark), Linode.com, US-East (Newark) Block Storage, US-East (Newark) NodeBalancers, US-East (Newark) Backups. Each is checked again whenever this page refreshes.

What should I do if Linode is down?

Pause deploys that depend on it, queue or retry failed jobs once it recovers, and check whether a mirror or cache can cover the gap.

Cloud Manager won't open — are my Linodes still up?

Yes. 'Cloud Manager and API' is one component; each region's compute, block storage, NodeBalancers and LKE are separate rows.

Object Storage failing in one region only?

That's how Akamai/Linode report it — storage is listed per region (e.g. 'US-East (Newark) Object Storage'), so an issue there does not apply to buckets in other regions.

How do I tell if Linode is down for everyone or only for me?

If the status above is operational but Linode still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.

How can I get alerted when my own site goes down?

OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.