Any scheduled server maintenance or related issues will be posted here in real time.
View Server Status
May 29, 02:39 UTC May 29, 01:52 UTC May 29, 00:54 UTC May 29, 00:33 UTC
Resolved - After monitoring this issue, Linode Kubernetes Engine services have remained stable and we are confident that this matter has been resolved. If you are still experiencing issues please reach out to Linode Customer Support.
Monitoring - We've deployed a fix for this issue, and we're monitoring the status of the Linode Kubernetes Engine to ensure that no further issues occur. We'll continue to provide updates until we're confident this has been resolved.
Identified - We have identified the cause of the degraded services affecting the Linode Kubernetes Engine and are implementing a fix at this time. We will continue to investigate this issue and provide updates as they become available.
Investigating - We are currently investigating an issue with the Linode Kubernetes Engine that has resulted in partially degraded service for some customers. We will be providing additional updates as we gather more information.
May 28, 22:27 UTC May 28, 20:48 UTC May 28, 16:27 UTC
Resolved - We are confident the fix implemented to correct issues with the CSI Block Storage driver is working as expected, and so we are considering this issue resolved. If you are still experiencing additional problems please open a Support ticket from the Linode Manager.
Monitoring - Our team has implemented a fix to correct the upstream issue affecting the use of the CSI Block Storage driver. All LKE Clusters which were deployed over the impacted timeframe, along with existing clusters, have had their CSI driver updated. We will continue to monitor this situation for any related issues.
Identified - We are aware of an upstream issue affecting the use of the CSI Block Storage driver for LKE Clusters and Nodes which are newly created or have recently restarted the CSI driver. We will continue to post additional updates as the situation develops.
May 22, 00:00 UTC May 21, 22:00 UTC May 21, 21:52 UTC
Completed - The scheduled maintenance has been completed.
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled - We will be performing an emergency network maintenance on a Core Switch in the Newark data center on Thursday, May 21st, 22:00 UTC, until Thursday, May 21st, at 24:00 UTC.
We do not expect any downtime during this maintenance; however, a 30 to 60 second period of packet loss or increased latency may be observed.
May 21, 01:41 UTC May 21, 00:14 UTC May 20, 22:22 UTC May 20, 20:22 UTC
Resolved - Connectivity in our Newark data center has remained stable, and we are confident this matter has been resolved. If you are still experiencing additional issues, please contact our Customer Support Team for assistance.
Monitoring - We have been able to correct the intermittent connectivity issues affecting our Newark data center. We will be monitoring this issue to ensure our services remain stable.
Identified - We have identified the connectivity issues affecting our Newark data center. Our team is working quickly to implement a fix for the brief and sporadic networking issues affecting some customers.
Investigating - We are aware of intermittent networking issues affecting public and private connections in our Newark data center. Our Network Operations team is working quickly to identify and resolve the root cause of these brief and sporadic outages. We’ll provide additional information as this situation develops.
May 19, 22:25 UTC May 19, 21:45 UTC May 19, 21:42 UTC
Completed - The scheduled maintenance has been completed.
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled - We will be performing maintenance on services powering the Linode Kubernetes Engine in Newark, Fremont, and Sydney on Tuesday, May 19th from 21:45PM UTC to approximately 22:30PM UTC. We do not expect any downtime or impact to Linode Kubernetes Engine workloads but users may notice a brief period of sluggishness when performing cluster management actions.