Linode Status

Current Status
IPv6 Connectivity Issue - London (EU-West)
Incident Report for Linode

On February 2, 2022, incorrect IPv6 routes were inadvertently advertised due to a conflicting networking configuration on a newly-installed rack of hosts. This resulted in a data center wide IPv6 networking outage at the London data center. Customer Linodes in the London data center were provided incorrect default routes and this led to a loss of IPv6 connectivity at the Linode level.

At approximately 11:18 UTC, we began to see failures in the provisioning of a newly-deployed rack of hosts within the London data center. Around 11:30 UTC, we began receiving reports from customers reporting outages on IPv6 addresses. At 13:00 UTC, the Networking team identified the IPv6 routing issue, and at 13:15 UTC, the newly-provisioned rack of hosts was taken offline. This corrected the routing issues, and IPv6 connectivity was restored at 13:40 UTC.

We have made improvements to our host deployment processes by creating safeguards that prevent the deployment of an improper networking configuration. We've also made improvements to our deployment processes that will allow us to more quickly identify potential problems on newly-provisioned hosts.

If you have any further questions for us, please open a Support ticket for assistance.

Posted Feb 15, 2022 - 17:05 UTC

This incident has now been resolved.

If you are still experiencing issues, please open a Support ticket for assistance.
Posted Feb 02, 2022 - 14:51 UTC
A fix has been implemented and we are monitoring the results.
Posted Feb 02, 2022 - 13:40 UTC
The issue has been identified and a fix is being implemented.
Posted Feb 02, 2022 - 13:25 UTC
Our team is investigating an IPv6 connectivity issue in our London (EU-West) data center. During this time, users may experience connection timeouts and errors for all services deployed in this data center over IPv6, however IPv4 traffic is currently unaffected. We will share additional updates as we have more information.
Posted Feb 02, 2022 - 12:56 UTC
This incident affected: Regions (EU-West (London)).