Linode Status

Current Status

Linodes failing to boot and apply firewall changes in all Data Centers

Incident Report for Linode

Postmortem

At around 17:00 UTC on November 14th, 2024, we started noticing failures across several data centers (including London, Dallas and Atlanta) after a change made by Akamai. This change was supposed to enable a new feature on host systems that would be transparent to end users. However, this unexpectedly caused some Linodes to fail booting, and those that were already running on affected hosts were unable to apply changes to Cloud Firewall rules.

In order to mitigate the issue, Akamai rolled back the deployed configuration at around 21:19 UTC on November 14th, 2024. In addition, all failed firewall rules were identified and remediated. Customers with affected firewalls were directly contacted.

To prevent this issue from happening in the future, Akamai will be prioritizing the resilience of the underlying service used to invalidate configurations for this infrastructure, defining a better method of configuration testing, and adding tests specific to this type of configuration test failure.

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 Nov 27, 2024 - 20:42 UTC

Resolved

We haven't observed any additional issues causing boot failures for Linodes as well as inability to make changes to Cloud Firewall rules, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.
Posted Nov 14, 2024 - 23:42 UTC

Monitoring

As of 21:19 UTC we have been able to correct the issue causing boot failures for Linodes as well as the inability to make changes to Cloud Firewall rules. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com.
Posted Nov 14, 2024 - 21:43 UTC

Identified

As of 19:46 UTC, we have been able to fix the issue causing the inability to boot Linodes and those booted Linodes are able to apply changes to Cloud Firewall rules. We are actively working to fix the Cloud Firewall rules that were deployed during the impact window as they are not applied at the moment. We will share additional updates as we have more information.
Posted Nov 14, 2024 - 20:32 UTC

Update

To add on to our previous post, customers may have issues with creating/recycling Linode Kubernetes Engine nodes and/or deploying Managed Databases as a result of this issue. Any Cloud Firewalls used along with those services would likely be unable to apply rule changes, as well.
Posted Nov 14, 2024 - 19:45 UTC

Investigating

At around 17:00 UTC on November 14th after a change we started noticing Host job failures across several Data Centers (including London, Dallas and Atlanta) specifically, some Linodes are failing to boot, and those which fail to boot may also be unable to apply changes to Cloud Firewall rules. Our team is investigating a service issue. We will share additional updates as we have more information.
Posted Nov 14, 2024 - 19:38 UTC
This incident affected: Linode Manager and API.