Linode favicon

Linode outage on 2026-10-15

linode.com
October 2026 15 Minor incident

Linode's status page logged two separate events on 15 October, a maintenance window on the Akamai Cloud Login service and a platform-wide patching effort for a KVM guest-to-host vulnerability. The login maintenance finished within the day, but the security patching was still open with no end time given.

Started

17:27 UTC

Duration

Lasted 14d 21h

Source

IsDown

Next time

Linode is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

What happened?

Linode's status page shows two incidents starting within twelve minutes of each other on 15 October, both tied to Akamai, which owns Linode's underlying infrastructure. The first was planned maintenance on the Akamai Cloud Login service, starting at 17:15 UTC. During that window new customer signup and account creation were disabled, while Akamai was explicit that existing customer accounts were not affected and could log in normally. That maintenance was marked resolved at 12:20 UTC the next day, a duration of 19 hours 9 minutes, with signup and account creation restored. The second incident is more serious in scope: a guest-to-host KVM escape vulnerability tracked as CVE-2026-99999, nicknamed PwnEscape. Akamai said it was aware of the vulnerability and was applying mitigations across its platform, and flagged potential customer workload impact as part of that response. Across three updates, Akamai repeated that it had not observed evidence of active exploitation on its platform. By the update at 05:07 UTC, Akamai said it had completed patching Compute hypervisors and recommended that customers upgrade Linode guest VMs with upstream kernel fixes once available, particularly for less trusted workloads run in containers or nested virtualisation. No further update had been filed after that, and the incident remains open with no resolution time given. Only one component is listed as affected, the Linode Manager and API, and no user reports were filed during the window.

Learning

This is an infrastructure-layer incident, not an application-layer one, and that distinction matters for how you read your own monitoring. A hypervisor vulnerability and the patching work around it happen below the level that an external check against your Linode-hosted endpoint can see. Your own probes might keep returning green the whole time because your VM is up and answering, while Akamai is working through phased patching across its hypervisor fleet underneath you. Akamai's own account bears this out: it reported no evidence of exploitation throughout, but still flagged potential customer workload impact as mitigations rolled out. Over the last 90 days Linode has logged 19 incidents with a median duration of 5 hours 11 minutes, and across all time it averages 7.6 a month, so this is a platform with a steady background rate of incidents worth tracking rather than a one-off. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.</learned> </invoke>

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.