At this time, we have completed the Xen Maintenance for all hosts in all datacenters.
Posted Jul 26, 2016 - 17:55 UTC
Linode has received a Xen Security Advisory (XSA) that requires us to perform updates to our legacy Xen 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 July 26th. We must complete this maintenance before then.
These security advisories only affect legacy Xen Linodes. KVM Linodes are not affected and do not require a reboot. Any customer that upgrades to KVM prior to the maintenance can avoid it entirely. You can use the “Upgrade to KVM” link in your Linode’s dashboard to move to KVM. More KVM upgrading information can be found here:
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 we have no control over the disclosure date of this XSA. As such, we must adhere to this strict timeline to ensure the security of both our customers and platform. We strongly recommend you read through our Reboot guide, which will help you prepare your Linode for these reboots. The Reboot guide is available here:
Each Linode's maintenance window will be communicated to you via email and will also be visible within the Linode Manager. Unfortunately, unless you’re able to upgrade to KVM, due the logistical demands of this effort your assigned maintenance windows are not changeable and the host reboots are mandatory. KVM is currently not available in Tokyo, which means Linodes in Tokyo will have to undergo maintenance on-schedule.
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 should be much less. After the maintenance, each Linode will then be booted.
Stay tuned for more information.
Posted Jul 15, 2016 - 14:01 UTC
This incident affected: Regions (US-East (Newark), US-Central (Dallas), US-West (Fremont), US-Southeast (Atlanta), EU-West (London)) and Linode Manager and API.