Emerging Service Issue - [DNS] - [eu-west]
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 provisi
The latest update from Akamai Cloud (Linode).
State
Resolved
Started
41 d ago
2026-09-21 16:50 UTC
Lasted
7 h 15 min
until 2026-09-22 00:04 UTC
Worst impact
Notice
Timeline
7 updatesInvestigating
1 h 52 min 26%
Identified
3 h 25 min 47%
Monitoring
1 h 58 min 27%
Updates
Times in UTCAs posted by Akamai Cloud (Linode)
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 provisi
This incident has been resolved.
At this time 21:45 UTC September 21st, 2026 we have been able to correct the issue affecting our DNS service in the London 1 (EU-West) region. We will be monitoring this to ensure that connectivity remains stable. Customers can apply this fix by enabling Network Helper (https://techdocs.akamai.com/cloud-computing/docs/automatically-configure-networking) and rebooting the effected Linode or please open a ticket with our Support Team.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
Our team has identified the issue affecting our DNS service in the London 1 (EU-West) region. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Our team is investigating an emerging service issue affecting our DNS service in the London 1 (EU-West) region. We will share additional updates as we have more information.
Affected components
1Akamai Cloud (Linode) in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
89
Median duration
6 h 29 min
This incident
About the median
Other Akamai Cloud (Linode) incidents
All incidentsAkamai Cloud (Linode)·Service Issue - US-Southeast (Atlanta)
A service issue affects US-Southeast (Atlanta). Akamai Cloud (Linode) reports that the region has degraded performance. Akamai Cloud (Linode) is still investigating the issue.
Akamai Cloud (Linode)·Customer Security Advisory: CVE-2026-98432
Akamai Cloud (Linode) reports a security advisory for CVE-2026-98432. Akamai states that it is investigating and is deploying mitigations for the known attack vector. Akamai advises customers to apply OS updates from their upstream provider when those updates become available.
Akamai Cloud (Linode)·Service Issue - Block Storage (BR-GRU)
Block Storage does not work in the BR-GRU (São Paulo) region. Akamai Cloud reports that a fix is in place and the state is monitoring.
Akamai Cloud (Linode)·Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)
Akamai Cloud reports a connectivity problem between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2). The service is degraded in these two regions. Akamai Cloud moved the incident to monitoring and continues to monitor the impact.
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.cc/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.cc/feed.xml?providers=linode/feed subscribe https://outages.cc/feed.xml?providers=linodeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane