- Level
- confirmed
- Worst impact
- Degraded
- Components
- Linode.com, US-SEA (Seattle)
- Regions
- us
- Down Index
- 35of 100
What to do
Check whether you use Akamai Cloud (Linode) Linode.com, US-SEA (Seattle) in us. 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 18m it lasted.
Anything that failed between 2026-08-28 10:26 UTC and 2026-08-28 17:44 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
We are investigating an emerging service issue affecting us-sea (Seattle, WA). We will share additional updates as we have more information.
provider
- investigating
We are continuing to investigate the issue. We will share additional details as soon as we have them.
provider
- investigating
Our team is investigating the issue where users may experience host unreachability, failures with all Linode control plane operations, including, but not limited to: node creation and deletion, attaching or detaching Block Storage. The issue appears to have started around 09:45 UTC on August 28, 2026. We will share additional updates as we have more information.
provider
- monitoring
At this time we have been able to correct the issues affecting the service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
We haven't observed any additional issues with Linode control plane operations and will now consider this incident resolved. If you are still experiencing additional issues, please open a Support ticket for assistance.
provider
- postmortem
Between approximately 09:51 and 12:18 UTC on August 28, 2028, customers using the Seattle data center \(US-SEA\) were unable to provision new nodes or complete host jobs, whereas customers outside Seattle were unaffected. The investigation revealed that this was due to a Linux kernel issue that was triggered on a network router due to increased network traffic at this site while a specific BIOS setting was enabled. This caused system instability and affected job processing in the US-SEA region. To mitigate the impact, the Akamai team disabled a problematic setting and rebooted the affected system, restoring service and moving the situation to a monitoring state by 12:18 UTC on August 28, 2026. As preventive actions, Akamai will audit hardware configurations to ensure the problematic feature is explicitly disabled, and implement enhanced monitoring to detect similar issues in the future. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.
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-c3d09fa5a3
Is Akamai Cloud (Linode) still down?
No, this incident was resolved 2026-08-28 17:44 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.
How long did it last?
7h 18m, from 2026-08-28 10:26 UTC to 2026-08-28 17:44 UTC, by the times Akamai Cloud (Linode) posted.
What was affected?
Akamai Cloud (Linode) named Linode.com, US-SEA (Seattle) in us.
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.