Scheduled Maintenance

Any scheduled server maintenance or related issues will be posted here in real time.

View Server Status

Connectivity Issues - Fremont
Scheduled for Friday February 23, 2018

Feb 23, 21:50 UTC
Resolved - Because we have not experienced additional connectivity issues affecting our Fremont data center, this matter is now resolved.
If you are still experiencing connectivity issues, please reach out to our Customer Support Team for assistance.

Feb 23, 20:04 UTC
Monitoring - Connectivity issues affecting our Fremont data center have been resolved. The connectivity issues have been identified as being the result of a power failure. Additional details regarding the power failure will be provided in a post-mortem. We will be monitoring this issue to ensure connectivity remains stable.

Feb 23, 18:51 UTC
Identified - We have identified the connectivity issues affecting our Fremont data center, and our team is working as quickly as possible to have full connectivity restored. We will provide additional updates as they develop.

Feb 23, 18:12 UTC
Investigating - We are aware of connectivity issues affecting Linodes and NodeBalancers in our Fremont data center and are currently investigating. We will continue to provide additional updates as this incident develops.

Service Issue - Lish, Weblish, Glish
Scheduled for Friday February 23, 2018

Feb 23, 17:13 UTC
Resolved - Being that we have not experienced further issues with Lish, Weblish, and Glish, this matter is now resolved.
If you experience any additional issues with these services, please reach out to our Customer Support Team for assistance.

Feb 23, 16:52 UTC
Monitoring - The issues affecting Lish, Weblish, and Glish have now been resolved. We will be monitoring this issue to ensure these services remain stable.

If you are still experiencing issues, please reach out to our Customer Support Team for assistance.

Feb 23, 16:44 UTC
Investigating - We are currently experiencing a service issue with Lish, Weblish, and Glish. Our team is investigating this issue and we will provide updates as we obtain additional information.

Network Maintenance - Fremont
Scheduled for Wednesday February 21, 2018

Feb 21, 00:00 UTC
Completed - The scheduled maintenance has been completed.

Feb 20, 23:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Feb 13, 19:45 UTC
Scheduled - We will be performing a scheduled network maintenance in Fremont to a switch on Tuesday, February 20th from 23:00 UTC until February 21st at 00:00 UTC. During this maintenance, we will be power cycling a line card. We do not expect any downtime during this maintenance, however, a brief period of packet loss or increased latency may be observed.

Lish Maintenance in Tokyo 1
Scheduled for Wednesday February 07, 2018

Feb 7, 15:30 UTC
Completed - The scheduled maintenance has been completed.

Feb 7, 15:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Feb 5, 23:08 UTC
Scheduled - We will be performing maintenance on Lish in the Tokyo 1 data center on Feb 7, 2018 at 15:00 UTC for approximately 30 minutes. Tokyo 1 Lish will be inaccessible during this time. We will update this post once the work is complete.

Linodes within the Tokyo 1 data center can still be accessed by using Lish in a different data center. https://www.linode.com/docs/networking/using-the-linode-shell-lish

Critical Maintenance for CPU Vulnerabilities
Scheduled for Thursday January 25, 2018

Jan 25, 13:39 UTC
Resolved - We've successfully deployed mitigations for the Meltdown vulnerability. For additional information, see https://blog.linode.com. If you have any questions or concerns, please feel free to reach out to our Support team.

Jan 10, 22:17 UTC
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