← Live dashboard

Service Issue - US-SEA (Seattle, WA)

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Aug 21, 2026, 05:23 PM · Resolved Aug 21, 2026, 09:59 PM

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...

Linode live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Linode now? Check the current status

Affected services

US-SEA (Seattle)

Updates (3)

  1. Sep 7, 2026, 06:36 PM
    Service Issue - US-SEA (Seattle, WA)

    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 syste

    Linode ↗
  2. Aug 21, 2026, 09:59 PM
    Service Issue - US-SEA (Seattle, WA)

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

    Linode ↗
  3. Aug 21, 2026, 05:23 PM
    Service Issue - US-SEA (Seattle, WA)

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

    Linode ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Linode's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.