Linode Status

Current Status

Service Issue - NodeBalancers (US-ORD, US-LAX, EU-WEST, FR-PAR, JP-OSA)

Incident Report for Linode

Postmortem

On September 22, 2025, beginning at 17:30 UTC, we experienced an issue that led to performance degradation for a subset of customers using our NodeBalancer product.

The root cause was sustained high CPU utilization on the shared compute infrastructure that underpins the NodeBalancer service. Because this infrastructure is shared among customers, unusually high demand from a few customers pushed CPU usage close to 100%, resulting in degraded performance for others on the same hardware.

This issue impacted multiple regions, including LAX3, LON4, ORD2, PAR3, and OSA1. Our engineering teams quickly traced the elevated CPU usage to overloaded NodeBalancers and worked to stabilize the environment. Mitigation efforts were prioritized to restore performance, with full resolution completed by 15:49 UTC on October 6, 2025.

We are taking proactive steps to reduce the likelihood of similar incidents in the future. This includes a range of improvements aimed at enhancing overall system efficiency and stability. We remain committed to transparency and reliability, and we appreciate your patience as we continue to strengthen our platform and deliver consistent service.

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.

Posted Oct 20, 2025 - 23:32 UTC

Resolved

We haven’t observed any additional issues with the NodeBalancer service in US‑ORD, US‑LAX, EU‑WEST, FR‑PAR, or JP‑OSA, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Posted Sep 25, 2025 - 18:08 UTC

Update

We are continuing to work on a fix for this issue. Most customers remain unaffected, but if you do encounter any problems with NodeBalancers, please open a ticket with our Support Team.
Posted Sep 24, 2025 - 16:10 UTC

Identified

Our team has identified the issue affecting the NodeBalancer service in our US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Posted Sep 23, 2025 - 20:10 UTC

Investigating

Our team is investigating an issue affecting the NodeBalancer service in the US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. Some users in these regions may experience NodeBalancer service degradation, including performance issues. At this time, the number of customers impacted appears to be limited, but we are closely monitoring the situation as there is some risk of broader impact. We will share additional updates as we have more information.
Posted Sep 23, 2025 - 15:36 UTC
This incident affected: NodeBalancers (US-ORD (Chicago) NodeBalancers, EU-West (London) NodeBalancers, FR-PAR (Paris) NodeBalancers, JP-OSA (Osaka) NodeBalancers, US-LAX (Los Angeles) NodeBalancers).