Linode Outage History

Linode experienced connectivity issues in their Frankfurt (DE-FRA-2) data center that lasted 13.4 hours. The incident affected network connectivity for services hosted in that region. The team implemented a fix and monitored the results before confirming full resolution.

Linode Kubernetes Engine Standard and Enterprise services experienced provisioning failures across all regions for 24.2 hours, preventing customers from deploying new clusters or adding new nodes to existing clusters. The issue was caused by an expired certificate which was identified and updated by the engineering team. The service was gradually restored with nodes successfully provisioning again, and the incident was fully resolved after monitoring confirmed stability.

Linode experienced a 3.4-hour service issue affecting the Cloud Manager and API that prevented customers from creating new Linodes, modifying Cloud Firewalls, performing migrations or resize operations, and caused delays in LKE autoscaling. The team identified the root cause and implemented a fix to restore normal functionality. The incident was resolved after a monitoring period to ensure service stability.

Linode experienced a service issue affecting their Dedicated CPU offering in the US-Southeast (Atlanta) region, causing failed Linode boots, resource allocation errors, unsuccessful migrations and scaling operations, and deployment difficulties for workloads requiring dedicated CPU resources. The issue impacted approximately 0.2% of hosts and lasted 49 hours before being resolved. Linode identified and implemented a fix, with a workaround available through support during the incident period.

A networking issue in Linode's US-IAD (Washington) data center caused intermittent connection timeouts and errors for services deployed in that region, lasting approximately 3 hours. The problem was caused by a specific compute host that generated abnormal network traffic when powered on, impacting the local management network and customer connectivity. The issue was resolved by isolating the problematic hardware, which immediately restored network stability and cleared the backlog of pending host jobs.

Linode experienced a major network connectivity issue in their London 2 region caused by an upstream provider problem that lasted 21.5 hours. The incident affected customer access to Linode infrastructure and services hosted in that region. The upstream provider issue was mitigated and connectivity was restored, with Linode monitoring the situation before declaring the incident fully resolved.

Linode experienced a service issue affecting Object Storage in the us-east-1 (Newark) region for 51 minutes. The issue was identified and a fix was implemented by the engineering team. The incident was fully resolved without any specified ongoing impact to users.

Linode experienced a service issue that prevented the deployment of new compute instances when the swap disk size was set to 0, which also impacted their Managed Databases service. The issue affected the Linode Manager and API for 3.5 hours. A fix was implemented and the incident was resolved after monitoring confirmed the solution was effective.

Linode experienced a major connectivity issue at their Jakarta data center that lasted 98.4 hours, affecting compute services and some Linodes and Kubernetes Engine clusters in the region. The incident also caused disruptions to dependent services in Singapore and Melbourne data centers due to backend dependencies. The team implemented fixes and restored most services, with full resolution confirmed after monitoring for stability.

Linode experienced a service issue affecting the Kubernetes Engine Enterprise (LKE-E) service in the Chicago, IL (us-ord) region for 1.3 hours. The team identified and corrected the underlying problem affecting the LKE-E service. The incident was resolved after a monitoring period to ensure service stability.