GlobalOutageMap
← Live dashboard
Linode logoLinode

Service Issue - US-SEA (Seattle, WA)

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Aug 28, 2026, 10:26 AM · Resolved Aug 28, 2026, 05:44 PM

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

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)Linode.com

Updates (7)

  1. Aug 28, 2026, 08:36 PM
    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

    Linode ↗
  2. Aug 28, 2026, 05:44 PM
    Service Issue - US-SEA (Seattle, WA)

    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.

    Linode ↗
  3. Aug 28, 2026, 12:48 PM
    Service Issue - US-SEA (Seattle, WA)

    We are continuing to monitor for any further issues.

    Linode ↗
  4. Aug 28, 2026, 12:45 PM
    Service Issue - US-SEA (Seattle, WA)

    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.

    Linode ↗
  5. Aug 28, 2026, 12:15 PM
    Service Issue - US-SEA (Seattle, WA)

    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.

    Linode ↗
  6. Aug 28, 2026, 11:39 AM
    Service Issue - US-SEA (Seattle, WA)

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

    Linode ↗
  7. Aug 28, 2026, 10:26 AM
    Service Issue - US-SEA (Seattle, WA)

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