正常

Linode 是不是挂了?

Linode 运行正常。 Linode(现属 Akamai)出租虚拟机与存储。

2026年10月22日的 Linode 状态:01:24 UTC 读取自官方状态页,最多每 5 分钟刷新一次。

近 90 天

54.78%
估算可用率
90 天前今天

根据 Linode 公布的事件推算,属于估算,不是实测值。

Linode 近 90 天稳定性

9报告事件数
0完全中断
2 h 53 min典型时长
4 d 4 h最长事件

最近一次事件:“Issue in creating new LKE Enterprise cluster across regions”,昨天。

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.

组件

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

近期事件

Issue in creating new LKE Enterprise cluster across regions

降级

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

降级

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)

降级

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.

常见问题

Linode 现在是不是挂了?

Linode 官方状态页显示:All Systems Operational。本页每次打开时会重新读取,最多每 5 分钟一次。

Linode 上一次故障是什么时候?

Linode 最近一次报告的事件是“Issue in creating new LKE Enterprise cluster across regions”,发生在昨天(2026-10-20 12:29 UTC)。近 90 天的事件中没有完全中断。

这里跟踪了 Linode 的哪些部分?

Linode 的状态页列出 242 个组件,包括 US-East (Newark), Linode.com, US-East (Newark) Block Storage, US-East (Newark) NodeBalancers, US-East (Newark) Backups。每次页面刷新都会重新读取。

Linode 挂了我该怎么办?

暂停依赖它的部署,等恢复后重试或补跑失败的任务,并看看镜像或缓存能否临时顶上。

Cloud Manager 打不开,我的 Linode 还在吗?

在。Cloud Manager and API 只是一个组件;各区域的计算、块存储、NodeBalancer 和 LKE 都是独立行。

只有一个区域的 Object Storage 出问题?

Akamai/Linode 就是这么上报的——对象存储按区域单列(如 US-East (Newark) Object Storage),一个区域的问题不涉及其他区域的 bucket。

怎么判断 Linode 是所有人都打不开,还是只有我这边有问题?

如果上面显示运行正常但 Linode 对你仍然不可用,问题多半在你这边:换个网络、清除缓存,或检查自己的网络连接。如果显示降级或故障,说明其他人也受到影响。

我自己的网站挂了,怎么第一时间收到通知?

OpenUptime 每分钟检查一次你的网站,一旦无响应就通过 Slack、Telegram、邮件或 Webhook 告警。它是开源的,可以免费开始使用。