Akamai Cloud (Linode) did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-22 20:08 UTC. This page shows the end time when Akamai Cloud (Linode) marks it resolved.

How do I get alerts for Akamai Cloud (Linode)?

Subscribe to the Akamai Cloud (Linode) live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Akamai Cloud (Linode). outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

Akamai Cloud (Linode)Incident · 2026-10-22 20:08 UTC

Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities

Q: What happened?

Akamai Cloud (Linode) reported "Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities" on its status page at 2026-10-22 20:08 UTC. Akamai Cloud (Linode) reports a security advisory for F5/NGINX vulnerabilities CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479. Akamai Cloud (Linode) is investigating the possible impact on its platform and infrastructure. Akamai Cloud (Linode) states that users who run a vulnerable version of NGINX Open Source or NGINX Plus on a Linode instance can apply the patches from F5/NGINX.

NoticeOfficial update

Akamai Cloud (Linode) reports a security advisory for F5/NGINX vulnerabilities CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479. Akamai Cloud (Linode) is investigating the possible impact on its platform and infrastructure. Akamai Cloud (Linode) states that users who run a vulnerable version of NGINX Open Source or NGINX Plus on a Linode instance can apply the patches from F5/NGINX.

State

Investigating

Started

10 d ago

2026-10-22 20:08 UTC

Ongoing for

10 days

Worst impact

Notice

Timeline

1 update

Oct 22Oct 25Oct 27Oct 30Nov 2

NoticeUpdate postedDates in UTC

Investigating

10 days 100%

Updates

Times in UTC

As posted by Akamai Cloud (Linode)

Investigating2026-11-01 08:39 UTC

Akamai is aware of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479), and our teams are actively investigating their potential impact across our platform and infrastructure. F5 has released out-of-band security patches addressing three critical severity vulnerabilities in NGINX Open Source and NGINX Plus. These vulnerabilities may allow unauthenticated attackers to trigger heap buffer overflows, which could cause a denial of service or potential remote code execution if ASLR is bypassed. If you are running a vulnerable version of NGINX Open Source or NGINX Plus on a Linode instance, we recommend following guidance from F5/NGINX and applying available patches. We will provide updates as additional information becomes available.

Akamai Cloud (Linode) in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

5 h 43 min

This incident

43× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

15 days

median 5 h 43 min

90 days agoToday

Other Akamai Cloud (Linode) incidents

All incidents

Akamai 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.

Resolvedresolved 6 h ago

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.

Degradedupdated 1 d ago

Akamai Cloud (Linode)·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.

Noticeupdated 2 d ago

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.

Noticeupdated 4 d ago

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.

Degradedupdated 4 d ago

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.

Prompt

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.

RSS

https://outages.live/feed.xml?providers=linode

Slack

/feed subscribe https://outages.live/feed.xml?providers=linode

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane