- Level
- confirmed
- Worst impact
- Degraded
- Components
- Hosted DNS Service
- Regions
- eu
- Down Index
- 35of 100
What to do
Check whether you use Akamai Cloud (Linode) Hosted DNS Service in eu. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 7h 15m it lasted.
Anything that failed between 2026-09-21 16:50 UTC and 2026-09-22 00:04 UTC may need a replay.Subscribe to Akamai Cloud (Linode)'s feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=linode works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Akamai Cloud (Linode) 7
- investigating
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.
provider
- identified
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.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
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.
provider
- resolved
This incident has been resolved.
provider
- postmortem
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 provisioning utilities dynamically assign distinct, active DNS resolvers across all regions to prevent recurrence. This summary reflects our current understanding of the incident based on available details. Our investigation remains ongoing, and findings may be updated as further information is reviewed.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-15dcd046fa
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-09-22 00:04 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
7h 15m, from 2026-09-21 16:50 UTC to 2026-09-22 00:04 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named Hosted DNS Service in eu.
What caused it?
Akamai Cloud (Linode) hasn't published a root cause. If it does, it shows here.
Where does this come from?
Akamai Cloud (Linode)'s official status page, https://status.linode.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.