All Systems Operational
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
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
EU-West (London) Linode Kubernetes Engine Operational
EU-Central (Frankfurt) Linode Kubernetes Engine Operational
AP-Northeast-2 (Tokyo 2) Linode Kubernetes Engine Operational
AP-Southeast (Sydney) Linode Kubernetes Engine Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
May 31, 2020

No incidents reported today.

May 30, 2020

No incidents reported.

May 29, 2020
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.
May 29, 02:39 UTC
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.
May 29, 01:52 UTC
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.
May 29, 00:54 UTC
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 29, 00:33 UTC
May 28, 2020
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.
May 28, 22:27 UTC
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.
May 28, 20:48 UTC
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 28, 16:27 UTC
May 27, 2020

No incidents reported.

May 26, 2020

No incidents reported.

May 25, 2020

No incidents reported.

May 24, 2020

No incidents reported.

May 23, 2020

No incidents reported.

May 22, 2020
Completed - The scheduled maintenance has been completed.
May 22, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 22:00 UTC
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, 21:52 UTC
May 21, 2020
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.
May 21, 01:41 UTC
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.
May 21, 00:14 UTC
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.
May 20, 22:22 UTC
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 20, 20:22 UTC
May 20, 2020
May 19, 2020
Completed - The scheduled maintenance has been completed.
May 19, 22:25 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 19, 21:45 UTC
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.
May 19, 21:42 UTC
May 18, 2020
Resolved - Linode Kubernetes Engine cluster creation has remained stable, and we're confident that this matter has been resolved. If you are still experiencing additional issues, please contact our Customer Support Team for assistance.
May 18, 11:26 UTC
Monitoring - The issues impacting the Linode Kubernetes Engine have corrected and cluster creation is now stable. We will continue to monitor this issue to ensure there are no further issues with cluster creation. If you continue to experience issues with deploying a Kubernetes cluster through the Linode Kubernetes Engine, please reach out to our Support team for assistance.
May 18, 10:22 UTC
Identified - We have identified the cause for the cluster creation issues impacting the Linode Kubernetes Engine. Our team is currently working to correct this issue and we will provide additional updates as the incident develops.
May 18, 09:59 UTC
Investigating - We’re currently investigating an issue with the Linode Kubernetes Engine. Customers are not able to create additional clusters at this time. We will provide more information as this develops.
May 18, 09:35 UTC
Resolved - Object Storage has 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.
May 18, 11:23 UTC
Monitoring - At this time we have been able to correct the issues affecting Object Storage in Newark. We will be monitoring this issue to ensure everything remains stable. If you are still experiencing issues, please reach out to our Customer Support Team for assistance.
May 18, 10:20 UTC
Identified - We have identified the cause of the issues affecting Object Storage in Newark. Our team is currently working to correct this matter and we will provide additional updates as this incident develops.
May 18, 09:43 UTC
Investigating - We are aware of connectivity issues affecting Object Storage in Newark and are currently investigating. We will continue to provide additional updates as this incident develops.
May 18, 08:12 UTC
Completed - The scheduled maintenance has been completed.
May 18, 07:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 18, 04:00 UTC
Scheduled - We will be performing an emergency network maintenance on a Core Switch in the Newark data center on Monday, May 18th, 04:00 UTC, until Monday, May 18th, at 07:00 UTC. This maintenance is a continuation and permanent fix of the maintenances listed below. 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.
https://status.linode.com/incidents/rkfjsp6cj1pk
https://status.linode.com/incidents/5v5hrj5g2r8k
May 15, 19:18 UTC
May 17, 2020

No incidents reported.