Customer Security Advisory: CVE-2026-98432
Akamai Cloud (Linode) reports a security advisory for CVE-2026-98432. The current state is investigating. Akamai advises customers to apply OS updates from their upstream provider as soon as those updates become available.
State
Investigating
Started
2 d ago
2026-10-30 18:10 UTC
Ongoing for
2 days
Worst impact
Notice
Timeline
1 updateInvestigating
2 days 100%
Updates
Times in UTCAs posted by Akamai Cloud (Linode)
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.
Akamai Cloud (Linode) in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
89
Median duration
5 h 43 min
This incident
9.7× the median
Other Akamai Cloud (Linode) incidents
All incidentsAkamai Cloud (Linode)·Connectivity Issue - IN-MAA and IN-BOM-2
Connectivity does not work for services in the IN-MAA (Chennai) and IN-BOM-2 (Mumbai 2) data centers. Akamai Cloud reports that the incident is resolved. The outage lasted 3 hours and 12 minutes.
Akamai Cloud (Linode)·Service Issue - US-Southeast (Atlanta)
Akamai Cloud (Linode) reports degraded service in the US-Southeast (Atlanta) region. The affected components are the US-Southeast (Atlanta) region and Regions - US-Southeast (Atlanta). Akamai Cloud is investigating the issue.
Akamai Cloud (Linode)·Service Issue - Block Storage (BR-GRU)
Block Storage does not work in the BR-GRU (São Paulo) region. Akamai Cloud (Linode) reports that a fix is in place and the provider monitors the result. The issue started on 28 October 2026.
Akamai Cloud (Linode)·Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)
Connectivity between the ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) regions is degraded. Akamai Cloud reports that monitoring is in progress. The start time was 25 October 2026.
Akamai Cloud (Linode)·Connectivity Issue - Dallas Data Center (IPv6 Traffic to Google)
This issue is considered resolved.
Follow Akamai Cloud (Linode)
Your coding agent knows when Akamai Cloud (Linode) is down, and tells you when a failure is theirs, not yours. You can also get Akamai Cloud (Linode) incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "linode" and tell me if Akamai Cloud (Linode) has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=linode/feed subscribe https://outages.live/feed.xml?providers=linodeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane