Akamai Cloud (Linode)
Akamai Cloud (Linode) is reporting degraded
Partially Degraded Service
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.
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.
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.
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.
Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities
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.
History
Incidents in 90 days
28
Days with an incident
89
Median duration
5 h 43 min
Longest incident
309 days
Components
242Regions
Sep 21, 2026
We haven't observed any additional issues with the Cloud Manager or API, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.status.linode.com
On September 21, 2026, starting at approximately 16:10 UTC, Akamai observed degraded DNS resolution performance affecting a subset of Linode instances within the London \(`LON1`\) region. Platform-wide DNS resolution remained functional, and no other regions were affected. The disruption occurred during a drive transplant of a compute host at the London \(lon1\) data center, which temporarily took a customer-facing DNS resolver offline. Due to a software logic flaw, customer workload configurations deployed in the last year across the region were disproportionately reliant on this single resolver, causing DNS failures when it became unavailable. At 21:45 UTC, engineering teams deployed an emergency configuration update to rebalance and reorder active DNS resolver assignments in the region, returning DNS query performance to baseline levels. Post-remediation monitoring confirmed stable operations across `LON1`. Long-term engineering updates are currently being deployed to ensure provisistatus.linode.com
Maintenance
Scheduled Longview Maintenance - US-Central (Dallas)
As part of addressing security vulnerabilities, we will be upgrading Longview servers in Dallas region. Existing graphs will remain available, but graph updates may be slightly delayed during individual server upgrades. The Maintenance period is expected to be from October 27 through November 3, 2026, with activities scheduled between 5:30 AM and 11:30 AM UTC.
Scheduled Longview Maintenance - US-Central (Dallas)
As part of addressing security vulnerabilities, we will be upgrading Longview servers in Dallas region. Existing graphs will remain available, but graph updates may be slightly delayed during individual server upgrades. The Maintenance period is expected to be from October 27 through November 3, 2026, with activities scheduled between 5:30 AM and 11:30 AM UTC.
Scheduled Longview Maintenance - US-Central (Dallas)
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Affected components
1- US-Southeast (Atlanta)RegionsDegraded
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=linodeGo from tracking outages to fixing production issues with Polylane.
Try Polylane