Linode, now operating under the Akamai brand, has been working through a security advisory for CVE-2026-98432 since 18:10 UTC on 30 October. This is not a service outage in the usual sense: it is a disclosed remote code execution vulnerability affecting the platform, and the incident is still open as updates continue. No fault with your own workload is implied by this record.
Started
18:10 UTC
Duration
Lasted 10d 3h
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?
Akamai opened this advisory at 18:10 UTC, saying it was aware of CVE-2026-98432, a remote code execution vulnerability, and was investigating mitigation while monitoring the platform. At 21:18 UTC it posted a holding update, saying subject matter experts were engaged and that mitigation status would follow as progress was made. By 01:55 UTC the following day, Akamai said it was deploying mitigations for the known attack vector and advised customers to apply OS updates from their upstream provider as they become available, while stating it had no evidence of exploitation on the Compute platform at that time. The 10:55 UTC update is the most detailed so far: Akamai says it has deployed network rules dropping IPv4 packets with optional headers on public and VPC interfaces, which it describes as closing the immediate remote attack vector without affecting performance, and that kernel patches are still being rolled out across infrastructure. There is no component list attached to this advisory, because the issue is being tracked as a platform-wide security matter rather than a regional or service-specific fault. No user reports were filed during this window on this record. Four updates have been published across roughly 17 hours, all under the "investigating" status, meaning Akamai has not yet declared the matter resolved. This is a single incident, not several, and it remains open as of the last update at 10:55 UTC. Everything here comes from Akamai's own advisory text; there is no independent post-mortem to check it against yet.
Learning
This is a case where the failure, if it materialises, would happen at the infrastructure and kernel level, not inside your application, so pinging your own endpoints tells you nothing about whether the underlying attack vector is closed. Akamai's mitigation involves network-level packet filtering and kernel patching across its Compute platform, work that sits entirely below anything your own uptime checks can see. A vulnerability advisory like this can run for many hours with "investigating" as the only status, even once concrete mitigations are in place, because the vendor is being cautious about declaring the matter closed. Over the past 90 days Linode has logged 27 incidents with a median duration of 6 hours 31 minutes, so a 17-hour open window on a security advisory is already running long by that baseline. Your own monitoring will keep showing green as long as your instances respond, and that is a correct reading of your half of the stack. UptimeRobot's tracking of Linode's own status feed is what tells you the provider is still working an open security issue, so you are not left guessing which side of the fence the problem sits on.