Linode Status

Current Status

Service Issue - NodeBalancers Widespread

Incident Report for Linode

Postmortem

On October 7th, 2025 starting at approximately 16:07 UTC, a misconfiguration caused by a firewall update in one of our data centers resulted in IPv6 connections for our NodeBalancer service to be blocked. Due to the reliance of NodeBalancer infrastructure on IPv6, this caused customers to experience issues with provisioning NodeBalancers and editing NodeBalancer configurations during the period of impact. 

After identifying the update as the cause of the issue, the database team reverted the changes made, which restored service at 20:10 UTC on the same date.

Since this event, we have redeployed the firewall update successfully and have verified that IPv6 connections are working as expected. To prevent recurrences of this issue, we are examining our current practices on updating essential databases and are taking steps to improve monitoring to better detect IPv6-related errors proactively.

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 15, 2025 - 00:32 UTC

Resolved

We haven’t observed any additional issues with the NodeBalancer service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Posted Oct 07, 2025 - 23:41 UTC

Monitoring

Starting at 16:07 UTC on October 7th, 2025, our team became aware of a widespread issue affecting our NodeBalancer service. During this period of time, users may have experienced nodebalancer provisioning issues.
We can confirm that we have been able to correct the issues affecting the NodeBalancer service at approximately 20:10 UTC on October 7th, 2025. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a ticket with our Support Team.
Posted Oct 07, 2025 - 22:26 UTC
This incident affected: NodeBalancers (US-East (Newark) NodeBalancers, US-Central (Dallas) NodeBalancers, US-West (Fremont) NodeBalancers, US-Southeast (Atlanta) NodeBalancers, US-IAD (Washington) NodeBalancers, US-ORD (Chicago) NodeBalancers, CA-Central (Toronto) NodeBalancers, EU-West (London) NodeBalancers, EU-Central (Frankfurt) NodeBalancers, FR-PAR (Paris) NodeBalancers, AP-South (Singapore) NodeBalancers, AP-Northeast-2 (Tokyo 2) NodeBalancers, AP-West (Mumbai) NodeBalancers, AP-Southeast (Sydney) NodeBalancers, SE-STO (Stockholm) NodeBalancers, US-SEA (Seattle) NodeBalancers, JP-OSA (Osaka) NodeBalancers, IN-MAA (Chennai) NodeBalancers, BR-GRU (São Paulo) NodeBalancers, NL-AMS (Amsterdam) NodeBalancers, ES-MAD (Madrid) NodeBalancers, IT-MIL (Milan) NodeBalancers, US-MIA (Miami) NodeBalancers, ID-CGK (Jakarta) NodeBalancers, US-LAX (Los Angeles) NodeBalancers, GB-LON (London 2) NodeBalancers, AU-MEL (Melbourne) NodeBalancers, IN-BOM-2 (Mumbai 2) NodeBalancers, DE-FRA-2 (Frankfurt 2) NodeBalancers, SG-SIN-2 (Singapore 2) NodeBalancers, JP-TYO-3 (Tokyo 3) NodeBalancers).