Linode incident

Service Issue - US-SEA (Seattle, WA)

Notice Resolved View vendor source →

Linode experienced a notice incident on August 21, 2026 affecting US-SEA (Seattle), lasting 4h 35m. The incident has been resolved; the full update timeline is below.

Started
Aug 21, 2026, 05:23 PM UTC
Resolved
Aug 21, 2026, 09:59 PM UTC
Duration
4h 35m
Detected by Pingoru
Aug 21, 2026, 05:23 PM UTC

Affected components

US-SEA (Seattle)

Update timeline

  1. investigating Aug 21, 2026, 05:23 PM UTC

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

  2. resolved Aug 21, 2026, 09:59 PM UTC

    At this time we have been able to correct the issue and the service has resumed normal operation.

  3. postmortem Sep 07, 2026, 06:36 PM UTC

    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.