The maintenance on Xen Linodes due to the embargoed XSAs was completed as scheduled.
Posted Dec 19, 2015 - 15:14 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Dec 13, 2015 - 02:00 UTC
Scheduled
Linode has received several Xen Security Advisories (XSAs) that require us to perform updates to our host servers. In order to apply the updates, hosts and the Linodes running on them must be rebooted. The XSAs will be publicly released by the Xen project team on December 17th, therefore we must complete the updates before that date.
These security advisories only affect Xen Linodes. KVM Linodes are not vulnerable and do not require a reboot. Any customer that upgrades to KVM prior to the maintenance can avoid it entirely.
These updates are required to protect the security and safe operations of not only our infrastructure, but yours as well. We understand that a disruption with such limited notice is inconvenient, and we hope you understand that these measures are warranted due to the severity of the XSAs.
Each host server will be assigned a maintenance window in which the reboot will occur. The maintenance schedule is still being worked out on our end, however we can tell you that all maintenance windows will start Sunday December 13th at 9 p.m. EST and will be completed before December 17th.
We will have the maintenance schedule defined within the next few days. Each Linode's maintenance window will be communicated to you via email and will also be visible within the Linode Manager. Unfortunately, due the logistical demands of this effort, your assigned windows are not changeable and the host reboots are mandatory.
During the maintenance window Linode instances will be cleanly shut down while we perform the updates. Your Linode will be inaccessible during this time. A two-hour window is allocated, however the actual downtime can be much less. After the maintenance, each Linode will then be booted. See our Reboot Survival Guide for tips and hints on configuring and testing that your Linode services boot properly.