Is Linode Down Today?

Common Linode issues

• →Object Storage 503s in specific regions
• →Linode boot stuck on Lassie restart
• →DNS propagation delays for new domains

• Service Issue - Cloud Manager and API

  postmortem

  Between approximately 10:15 and 12:18 UTC on September 7, 2026, customers could have experienced elevated error rates and 5xx response codes when using Cloud Manager or performing API calls.  The investigation revealed that the issue started due to increased API load that over-utilized our database resources which in turn led to the symptoms seen by users. To mitigate the issue, the team addressed the elevated API load issue which brought back utilization of our resources within normal ranges. Ongoing actions include monitoring platform stability, and planning enhancements to API rate limiting. 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.

  Sep 7, 2026Details →

• Service Issue - US-SEA (Seattle, WA)

  postmortem

  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.

  Aug 28, 2026Details →

• Service Issue - Object Storage - US-SEA

  resolved

  We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

  Aug 24, 2026Details →

• Service Issue - US-SEA (Seattle, WA)

  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.

  Aug 21, 2026Details →

• Connectivity Issue - IT-MIL (Milan) data center

  postmortem

  On August 14, 2026, starting around 17:30 UTC, during an event in our IT-MIL \(Milan\) data center, multiple alerts were triggered indicating that multiple hosts in this data center became unreachable. ‌ Akamai immediately began investigating the issue and working to restore the impacted hosts. During the impact window, customers would have experienced intermittent connection timeouts and errors across all services deployed in this data center. ‌ We restored the impacted hosts and fixed the connectivity issues at 21:20 UTC on August 14, 2026. We are still investigating the cause of the failure condition. ‌ We are committed to preventing future incidents and will conduct a thorough investigation into why the hosts became unreachable, implementing measures to enhance stability and reliability. ‌ 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.

  Aug 14, 2026Details →