Identified - A number of serious security vulnerabilities affecting multiple CPU architectures were recently disclosed by Google’s Project Zero team as outlined in our blog post[1]. In order to address these vulnerabilities, the host on which your Linode resides will need to undergo maintenance. This is the first of several separate maintenances that will be necessary to fully mitigate these vulnerabilities.

Each Linode's maintenance window will be communicated to you via support ticket and will also be visible within the Linode Manager. During the maintenance window, your Linode will be cleanly shut down and will be unavailable while we perform the updates. A two-hour window is allocated, however the actual downtime should be much less. After the maintenance has concluded, each Linode will be returned to its last state (running or powered off).

You can prepare your Linode for this maintenance by following our Reboot Survival Guide. By following this guide before your maintenance, you will be able to ensure that services running on your Linode are resumed properly. The Reboot Survival Guide is available here:

https://www.linode.com/docs/uptime/reboot-survival-guide

These updates affect the underlying infrastructure that your Linode resides on and will not affect the data stored within your Linode. In order to fully mitigate the Meltdown vulnerability, you must update your Linode’s kernel to version 4.14.11 or later. If your Linode’s Configuration Profile is set to utilize our latest kernel, your Linode will automatically use 4.14.11 or later upon rebooting.

We have also made a guide available with more information on these vulnerabilities and how you can protect your Linode:

https://www.linode.com/docs/platform/meltdown_statement/

We regret the short notice and the downtime required for this maintenance. However, due to the severity of these vulnerabilities, we have no choice but to take swift and immediate action to ensure the safety and security of our customers. For these reasons, we must adhere to a strict timetable, and will not be able to reschedule or defer this maintenance.

Stay tuned for more information.

[1] https://blog.linode.com/2018/01/03/cpu-vulnerabilities-meltdown-spectre
Jan 10, 22:17 UTC
Linode Manager and API   Operational
Hosted DNS Service   Operational
London   Operational
Newark   Operational
Atlanta   Operational
Dallas   Operational
Fremont   Operational
Tokyo 1   Operational
Tokyo 2   Operational
Singapore   Operational
Frankfurt   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jan 22, 2018

No incidents reported today.

Jan 21, 2018

No incidents reported.

Jan 20, 2018

No incidents reported.

Jan 19, 2018
Resolved - We haven't observed any additional issues with the Linode Manager or our API, and will now consider this incident resolved. If you are still experiencing additional issues, please email our Customer Support Team at support@linode.com for assistance.
Jan 19, 13:40 UTC
Monitoring - We have been able to correct the connectivity issues affecting the Linode Manager, and our API. We will be monitoring this issue to ensure that connectivity remains stable. If you are still experiencing connectivity issues with the Linode Manager or our API, please email our Customer Support Team at support@linode.com for assistance.
Jan 19, 13:03 UTC
Investigating - We are currently aware of and are investigating connectivity issues with the Linode Manager, and the API. Our team is investigating further. We are working to restore service as quickly as possible. We will continue to provide additional updates as this incident develops.
Jan 19, 12:48 UTC
Resolved - This maintenance has been completed successfully.
Jan 19, 10:21 UTC
Identified - As our team continues to perform Meltdown-related maintenance across our infrastructure, customers may experience brief periods of intermittent connectivity to their NodeBalancer service.

We regret the short notice for this maintenance. However, due to the severity of these vulnerabilities, we have no choice but to take quick action to ensure the safety and security of our customers. For these reasons, we will not be able to reschedule or defer this maintenance. Thank you for your understanding. We will continue to provide updates as this maintenance progresses.
Jan 19, 02:34 UTC
Jan 18, 2018

No incidents reported.

Jan 17, 2018

No incidents reported.

Jan 16, 2018

No incidents reported.

Jan 15, 2018

No incidents reported.

Jan 14, 2018

No incidents reported.

Jan 13, 2018

No incidents reported.

Jan 12, 2018

No incidents reported.

Jan 11, 2018

No incidents reported.

Jan 9, 2018

No incidents reported.

Jan 8, 2018

No incidents reported.