Linode Outage History

Linode experienced a service issue affecting LKE Enterprise clusters across all regions, causing failures when users attempted to deploy new clusters or upgrade existing ones. The incident impacted Kubernetes Engine services in 10 regions including Frankfurt, Singapore, Sydney, London, Toronto, Fremont, Mumbai, Tokyo, Newark, and Dallas. The issue was resolved after 38 minutes of investigation and remediation work.

Linode's support phone line experienced a 25.6-hour outage due to an upstream provider issue, preventing customers from reaching support by phone. The incident affected customer access to phone-based technical support, requiring users to submit support tickets through the Cloud Manager instead. The upstream issue was resolved and phone support functionality was fully restored.

Linode's Block Storage service in the Newark, US data center experienced issues causing connection timeouts, latency, and errors for users over a 24.3-hour period. The service was affected intermittently, with the team implementing fixes and monitoring for stability multiple times throughout the incident. The issue was ultimately resolved with no further problems observed.

A service issue affected network traffic in Linode's Paris data center (FR-PAR3) on May 22, 2026, with the primary impact occurring between 09:10 UTC and 11:30 UTC. The connectivity problems were resolved by 11:30 UTC the same day, and after monitoring for stability over several days, the incident was officially closed on May 26, 2026.

Linode experienced a service issue affecting GPU provisioning across all regions, specifically preventing deployment of RTX PRO 6000 Blackwell plans for approximately 4.7 hours starting around 15:00 UTC on May 19, 2026. The team deployed an API hotfix that resolved the provisioning issues by 21:27 UTC the same day. After monitoring for stability, the incident was declared fully resolved at 00:27 UTC on May 20, 2026.

Linode experienced a service issue affecting Linodes booting across all regions, impacting both regular Linode instances and Linode Kubernetes Engine (LKE) services globally. The issue prevented virtual machines from starting up properly in all of Linode's data centers worldwide. The problem was identified and resolved with a fix implementation, with the incident lasting approximately 1.1 hours.

Linode experienced global delays affecting VM cold and live migrations as well as resize operations across all regions for 1.5 hours. The issue was caused by an unexpected reboot of internal infrastructure components that failed to reinitialize properly, causing the migration queue to stall. The affected components were reinitialized, clearing the pending queue and restoring normal migration and resize functionality.

Linode experienced a connectivity issue in their NL-AMS data center that caused intermittent connection timeouts and errors for all services deployed in that location. The incident lasted 4.9 hours, during which users faced disrupted access to their deployed services. The issue was resolved after the team confirmed no customers were being impacted and connectivity had stabilized.