Linode Outage History

Linode experienced a major networking issue affecting their Washington, DC data center (US-IAD) that disrupted connectivity for services hosted in that location. The incident lasted approximately 2 hours while their team investigated and identified the root cause. The issue was resolved after implementing a fix, with no additional connectivity problems observed.

Linode experienced a service issue that prevented the deployment of new LKE Enterprise Clusters in the Osaka, Japan region for approximately 2 hours. The team investigated and corrected the underlying problems affecting the LKE service. The incident was resolved after a monitoring period confirmed the service remained stable.

Linode experienced connectivity issues affecting compute hosts in their IAD (Washington, DC) data center for approximately 49 hours. The service disruption impacted users' ability to connect to their compute instances in that region. The technical team identified and corrected the underlying connectivity problems, with the incident resolved after a monitoring period to ensure stability.

Linode experienced an 11.3-hour incident where customers received delayed event notifications and notification emails from Cloud Manager activities. The issue was caused by a backlog of notifications that accumulated from a previous incident on March 4, 2026, which created processing delays when the system attempted to clear the queue. The incident was resolved once the notification backlog was fully processed and cleared.

Linode's Object Storage service in Osaka, Japan experienced an issue causing users to encounter connection timeouts and errors. The incident was classified as minor and lasted 11 minutes while the team investigated the problem. The service issue was resolved after the brief investigation period.

Linode experienced a critical service issue affecting NVIDIA RTX 4000 Ada GPU nodes across multiple regions (Osaka, Seattle, and Chicago), causing unrecoverable error states that led to failures in Vulkan initialization and GPU-accelerated workloads. The incident also impacted some LKE clusters in the Osaka region with Control Plane connectivity issues, resulting in timed-out API requests and errors. The issue was resolved after 16.1 hours, with the root cause identified as a regression in the underlying host hypervisor or GPU firmware.

Linode customers experienced duplicate notification emails being sent at fixed intervals due to an issue affecting the Linode Manager and API. The incident lasted 14.5 hours while Linode's team investigated and worked to resolve the email duplication problem. The issue was resolved with no additional problems observed, and customers were advised to contact support if they continued experiencing issues.

Linode experienced a connectivity issue in their Mumbai data center that caused intermittent connection timeouts, errors, and degraded networking performance for all services deployed in that region. The issue was caused by ongoing restoration activities on a third-party service provider's cable system, which resulted in packet loss and connectivity problems. After applying mitigation steps and the completion of the cable system restoration work, normal operations resumed and the incident was resolved after 92.5 hours.

Linode experienced a connectivity issue in their Singapore data center starting at approximately 1905 UTC on February 27, 2026, lasting 46 minutes. Users experienced intermittent connection timeouts and errors for all services deployed in the affected data center. The incident was resolved after no additional connectivity issues were observed.

Linode experienced a connectivity issue affecting their Chennai (in-maa) and Mumbai Expansion (in-bom-2) data centers, causing intermittent connection timeouts and errors for all services deployed in these locations. The incident lasted 6.2 hours before connectivity issues were corrected and the service was restored. The team monitored the resolution to ensure stability before declaring the incident fully resolved.