Identified - We have identified and developed a number of critical stability and performance improvements for our infrastructure. These include fixes for a potential crash, general performance tweaks, and enhancements to networking throughput. After implementing, testing, deploying, and gaining confidence in these changes, we are now ready to roll updates out to the remaining fleet. This is expected to significantly decrease the amount of unplanned maintenance.

To complete this, we will be performing reboots 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.

During the actual maintenance window, your Linode will be cleanly shut down and will be unavailable while we perform the updates. To minimize impact, maintenance will be limited to each respective datacenter’s local off-hours time. A 2-hour window is allocated, however the actual downtime should be around 45-60 minutes. After the maintenance has concluded, each Linode will be returned to its last state (running or powered off).

This status page will be updated once maintenance is complete.
Jul 16, 14:18 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-2 (Tokyo 2) Operational
AP-West (Mumbai) Operational
AP-Southeast (Sydney) 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-2 (Tokyo 2) Backups Operational
AP-West (Mumbai) Backups Operational
AP-Southeast (Sydney) Backups 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
AP-West (Mumbai) 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-2 (Tokyo 2) NodeBalancers Operational
AP-West (Mumbai) NodeBalancers Operational
AP-Southeast (Sydney) NodeBalancers Operational
Object Storage Operational
US-East (Newark) Object Storage Operational
EU-Central (Frankfurt) Object Storage Operational
AP-South (Singapore) Object Storage Operational
Linode Kubernetes Engine Operational
US-East (Newark) Linode Kubernetes Engine Operational
US-Central (Dallas) Linode Kubernetes Engine Operational
US-West (Fremont) Linode Kubernetes Engine Operational
CA-Central (Toronto) Linode Kubernetes Engine Operational
EU-West (London) Linode Kubernetes Engine Operational
EU-Central (Frankfurt) Linode Kubernetes Engine Operational
AP-South (Singapore) Linode Kubernetes Engine Operational
AP-Northeast-2 (Tokyo 2) Linode Kubernetes Engine Operational
AP-West (Mumbai) Linode Kubernetes Engine Operational
AP-Southeast (Sydney) Linode Kubernetes Engine Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Aug 7, 2020

No incidents reported today.

Aug 6, 2020
Resolved - Network connectivity to our Frankfurt data center continues to remain stable, so we are considering this event resolved. If you are still experiencing additional problems please open a Support ticket from the Linode Manager.
Aug 6, 20:06 UTC
Update - Connectivity has remained stable, and we are still monitoring this issue. We will provide additional updates as they are available.
Aug 6, 18:59 UTC
Monitoring - Connectivity to our Frankfurt data center has remained stable since our last update. We are continuing to monitor this situation to ensure no new issues arise.
Aug 6, 17:20 UTC
Identified - At this time we have identified the connectivity issues affecting our Frankfurt data center and network connectivity should be restored. We will provide additional updates as they develop.
Aug 6, 15:56 UTC
Investigating - We are aware of connectivity issues affecting Linodes in our Frankfurt data center and are currently investigating. We will continue to provide additional updates as this incident develops.
Aug 6, 15:38 UTC
Aug 5, 2020

No incidents reported.

Aug 4, 2020
Completed - The scheduled maintenance has been completed.
Aug 4, 21:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 4, 20:00 UTC
Scheduled - We will be performing a scheduled network maintenance on our aggregate routers in the Tokyo 2, JP data center on Tuesday, August 4th from 20:00 UTC until 21:00 UTC. We do not expect any downtime during this maintenance however, a brief period of packet loss or increased latency may be observed.
Jul 31, 16:45 UTC
Aug 3, 2020

No incidents reported.

Aug 2, 2020

No incidents reported.

Aug 1, 2020

No incidents reported.

Jul 31, 2020
Resolved - Scheduled maintenance for the Linode Kubernetes Engine has been completed.
Jul 31, 05:14 UTC
Identified - In preparation for our upcoming scheduled maintenance for general stability and performance improvements, we will need to perform maintenance on the Linode Kubernetes Engine. We anticipate this maintenance may result in a loss of connectivity to LKE control planes for up to 5 minutes, however, in many cases it will be much less. Most workloads already running in an LKE cluster will not be impacted by this maintenance.

To minimize impact, maintenance will be limited to each respective data center’s local off-hours time. Please see below for a complete list of maintenance windows by data center:

AP-South (Singapore) - 13:00 - 15:30 EST - 07/30
AP-Northeast-2 (Tokyo 2) - 13:00 - 15:30 EST - 07/30
EU-Central (Frankfurt) - 15:00 - 17:30 EST - 07/30
EU-West (London) - 15:00 - 17:30 EST - 07/30
US-East (Newark) - 22:00 - 00:30 EST - 07/30
US-West (Fremont) - 22:00 - 00:30 EST - 07/30
US-Central (Dallas) - 22:00 - 00:30 EST - 07/30
Jul 29, 21:24 UTC
Jul 30, 2020
Resolved - Maintenance on the Linode Images and Linode Backup Service in our US-Central (Dallas) data center has been completed. If you are experiencing additional problems with your Images or Backup Service, please open a Support ticket from the Linode Manager.
Jul 30, 14:16 UTC
Identified - We will be performing maintenance to the Linode Images and Linode Backup Service in our US-Central (Dallas) data center. During this maintenance, customers may intermittently be unable to create or restore images, backups, or snapshots, and may experience increased image, backup, and snapshot restoration or deployment times for Linodes in Dallas.

We understand the importance of these services and are working to complete this maintenance as quickly as possible. We expect this maintenance to be completed within approximately one week. If additional time is needed, we’ll provide updates here.
Jul 23, 20:34 UTC
Jul 29, 2020
Completed - The scheduled maintenance has been completed.
Jul 29, 18:27 UTC
Update - This maintenance is taking a bit longer than anticipated. We have extended the maintenance window by another 30 minutes to 18:30 UTC.
Jul 29, 18:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 29, 17:00 UTC
Scheduled - We will be performing maintenance to our Linode Rescue Mode environment on Wednesday July 29 from 17:00 until 18:00 UTC. During this time, you may not be able to boot your Linode into rescue mode or use our Finnix rescue image.
Jul 23, 15:34 UTC
Jul 28, 2020
Completed - The scheduled maintenance has been completed.
Jul 28, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 28, 20:00 UTC
Scheduled - We will be performing a scheduled network maintenance on our B side gateway router in the Tokyo 2, JP data center on Tuesday, July 28th from 20:00 UTC until 22:00 UTC. We do not expect any downtime during this maintenance however, a brief period of packet loss or increased latency may be observed.
Jul 22, 16:22 UTC
Resolved - Our DNS Services have remained stable, so we are considering this incident resolved. If you are still experiencing issues, please email our Customer Support Team at support@linode.com for assistance.
Jul 28, 09:51 UTC
Monitoring - At this time we have been able to correct the issues affecting DNS resolution and we will be monitoring to ensure it's stable.
If you are still experiencing issues, please reach out to our Customer Support Team for assistance.
Jul 28, 08:51 UTC
Investigating - We are aware of issues affecting our DNS. We are currently investigating and will continue to provide additional updates as this incident develops.
Jul 28, 08:01 UTC
Jul 27, 2020

No incidents reported.

Jul 26, 2020

No incidents reported.

Jul 25, 2020

No incidents reported.

Jul 24, 2020

No incidents reported.