Service Issue - US-SEA (Seattle, WA)

Summary

Service Issue - US-SEA (Seattle, WA)

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.

• Started

  Aug 28, 2026 · 10:26 AM

• Resolved

  Aug 28, 2026 · 5:44 PM

• Duration

  7h 18m

• Severity

  None

• ◐

  Investigating

  Aug 28 · 10:26 AM Linode

  We are investigating an emerging service issue affecting us-sea (Seattle, WA). We will share additional updates as we have more information.

• ◐

  Investigating

  Aug 28 · 11:39 AM Linode

  We are continuing to investigate the issue. We will share additional details as soon as we have them.

• ◐

  Investigating

  Aug 28 · 12:15 PM Linode

  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.

• ◉

  Monitoring

  Aug 28 · 12:45 PM Linode

  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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

• ◉

  Monitoring

  Aug 28 · 12:48 PM Linode

  We are continuing to monitor for any further issues.

• ✓

  Resolved

  Aug 28 · 5:44 PM Linode

  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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

• ✓

  Postmortem

  Aug 28 · 8:36 PM Linode

  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.