Identified - To complete our mitigations against the recent MDS (ZombieLoad) CPU vulnerability[1], we will be performing maintenance on a subset of Linode’s host machines. This maintenance will update the underlying infrastructure that Linodes reside on and will not affect the data stored within them.

If you are on an affected host, your maintenance window will be communicated to you via a Support ticket within the next few days. You can prepare your Linode for this maintenance by following our Reboot Survival Guide[2].

During the actual 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).

To fully mitigate the MDS vulnerability, set your Configuration Profile to utilize our latest kernel. If you use a distribution-supplied kernel, you can update your kernel[3] via your package manager. Linodes that use our latest kernel will automatically update upon reboot.

For more information on this vulnerability and how you can protect your Linode, please see our blog post [4].

Our status page will be updated once maintenance is complete.

[1] https://www.intel.com/content/www/us/en/architecture-and-technology/mds.html
[2] https://www.linode.com/docs/uptime/reboot-survival-guide
[3] https://www.linode.com/docs/platform/update-kernel
[4] https://blog.linode.com/2019/05/15/intels-mds-zombieload-cpu-vulnerabilities-linode
Jun 3, 14:30 UTC
Linode.com Operational
Linode Manager and API Operational
Hosted DNS Service Operational
Longview Operational
Regions Operational
US-East (Newark) Operational
US-Central (Dallas) Operational
US-West (Fremont) Operational
US-Southeast (Atlanta) Operational
CA-Central (Toronto) Operational
EU-West (London) Operational
EU-Central (Frankfurt) Operational
AP-South (Singapore) Operational
AP-Northeast-1 (Tokyo 1) Operational
AP-Northeast-2 (Tokyo 2) Operational
Block Storage Operational
US-East (Newark) Block Storage Operational
US-Central (Dallas) Block Storage Operational
US-West (Fremont) Block Storage Operational
CA-Central (Toronto) Block Storage Operational
EU-West (London) Block Storage Operational
EU-Central (Frankfurt) Block Storage Operational
AP-South (Singapore) Block Storage Operational
AP-Northeast-2 (Tokyo 2) Block Storage Operational
NodeBalancers Operational
US-East (Newark) NodeBalancers Operational
US-Central (Dallas) NodeBalancers Operational
US-West (Fremont) NodeBalancers Operational
US-Southeast (Atlanta) NodeBalancers Operational
CA-Central (Toronto) NodeBalancers Operational
EU-West (London) NodeBalancers Operational
EU-Central (Frankfurt) NodeBalancers Operational
AP-South (Singapore) NodeBalancers Operational
AP-Northeast-1 (Tokyo 1) NodeBalancers Operational
AP-Northeast-2 (Tokyo 2) NodeBalancers Operational
Backups Operational
US-East (Newark) Backups Operational
US-Central (Dallas) Backups Operational
US-West (Fremont) Backups Operational
US-Southeast (Atlanta) Backups Operational
CA-Central (Toronto) Backups Operational
EU-West (London) Backups Operational
EU-Central (Frankfurt) Backups Operational
AP-South (Singapore) Backups Operational
AP-Northeast-1 (Tokyo 1) Backups Operational
AP-Northeast-2 (Tokyo 2) Backups Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
On Saturday the 22nd of June at approximately 4:00 AM UTC we will be performing a standard upgrade to one of our switch pairs in the Newark data center.

Due to the redundant nature of these systems, we do not expect an impact on customer traffic or downtime during this process. As with any network maintenance, the possibility exists of some latency and packet loss during the window. The duration of this maintenance will be 120 minutes.
Posted on Jun 18, 23:25 UTC
Past Incidents
Jun 20, 2019

No incidents reported today.

Jun 19, 2019

No incidents reported.

Jun 18, 2019
Resolved - Connectivity with the Cloud Manager and APIv4 has remained stable, and we're confident this matter has been resolved. If you are still experiencing additional issues, please contact our Customer Support Team for assistance.
Jun 18, 01:13 UTC
Monitoring - We have been able to correct the issues affecting the Cloud Manager and APIv4. We will be monitoring this issue to ensure our services remain stable.
Jun 18, 00:27 UTC
Identified - We have identified the connectivity issues affecting the Cloud Manager and APIv4. Our team is working as quickly as possible to have connectivity restored. We will provide additional updates as the situation develops.
Jun 18, 00:16 UTC
Investigating - We are currently experiencing issues affecting the Cloud Manager and APIv4. Our team is investigating these issues and we will provide additional updates as we continue to gather information.

The Classic Linode Manager (manager.linode.com) is unaffected by these issues.
Jun 17, 23:37 UTC
Jun 16, 2019

No incidents reported.

Jun 15, 2019

No incidents reported.

Jun 14, 2019
Completed - The scheduled maintenance has been completed.
Jun 14, 12:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 14, 11:00 UTC
Scheduled - On Friday the 14th of June at approximately 11:00 AM UTC we will be performing a standard upgrade to one of our switch pairs in the Fremont data center.

Due to the redundant nature of these systems, we do not expect an impact to customer traffic or downtime during this process. As with any network maintenance, the possibility exists of some latency and packet loss during the window. The duration of this maintenance will be 90 minutes.
Jun 5, 15:46 UTC
Jun 13, 2019

No incidents reported.

Jun 12, 2019

No incidents reported.

Jun 11, 2019

No incidents reported.

Jun 10, 2019

No incidents reported.

Jun 9, 2019

No incidents reported.

Jun 8, 2019

No incidents reported.

Jun 7, 2019

No incidents reported.

Jun 6, 2019

No incidents reported.