Linode incident

Emerging Service Issue - LKE Enterprise - All Regions

Notice Resolved View vendor source →

Linode experienced a notice incident on June 5, 2026 affecting US-East (Newark) Linode Kubernetes Engine and US-Central (Dallas) Linode Kubernetes Engine and 1 more component, lasting 35m. The incident has been resolved; the full update timeline is below.

Started
Jun 05, 2026, 02:23 PM UTC
Resolved
Jun 05, 2026, 02:58 PM UTC
Duration
35m
Detected by Pingoru
Jun 05, 2026, 02:23 PM UTC

Affected components

US-East (Newark) Linode Kubernetes EngineUS-Central (Dallas) Linode Kubernetes EngineUS-West (Fremont) Linode Kubernetes EngineUS-Southeast (Atlanta) Linode Kubernetes EngineUS-IAD (Washington) Linode Kubernetes EngineUS-ORD (Chicago) Linode Kubernetes EngineCA-Central (Toronto) Linode Kubernetes EngineEU-West (London) Linode Kubernetes EngineEU-Central (Frankfurt) Linode Kubernetes EngineFR-PAR (Paris) Linode Kubernetes Engine

Update timeline

  1. investigating Jun 05, 2026, 02:23 PM UTC

    We are currently investigating an emerging service issue affecting LKE Enterprise clusters across all regions. During this time, users may experience failures when deploying new clusters or upgrading existing ones. Our team is working to resolve this, and we will provide updates here as they become available.

  2. resolved Jun 05, 2026, 02:58 PM UTC

    This incident has been resolved.