Resolved incident
Service Issue - US-SEA (Seattle, WA)
Linode · None · Started
- Duration
- 4h 36m
- Severity
- None
- Status
- Postmortem
Summary
None · Postmortem
On August 21, 2026 starting approximately at 17:23 UTC, 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 21:59 UTC on August 21, 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.
Event timeline
How this incident unfolded, from the official status page.
Investigating
Linode
Our team is investigating an emerging service issue affecting us-sea (Seattle, WA). We will share additional updates as we have more information.
Resolved
Linode
At this time we have been able to correct the issue and the service has resumed normal operation.
Postmortem
Linode
On August 21, 2026 starting approximately at 17:23 UTC, 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 21:59 UTC on August 21, 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.