Linode incident

Emerging Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]

Notice Resolved View vendor source →

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

Started
May 16, 2026, 12:42 AM UTC
Resolved
May 16, 2026, 01:43 AM UTC
Duration
1h 1m
Detected by Pingoru
May 16, 2026, 12:42 AM UTC

Affected components

US-East (Newark)US-East (Newark) Linode Kubernetes EngineUS-Central (Dallas)US-Central (Dallas) Linode Kubernetes EngineUS-West (Fremont)US-West (Fremont) Linode Kubernetes EngineUS-Southeast (Atlanta)US-Southeast (Atlanta) Linode Kubernetes EngineUS-IAD (Washington)US-IAD (Washington) Linode Kubernetes Engine

Update timeline

  1. investigating May 16, 2026, 12:42 AM UTC

    Our team is investigating an emerging service issue affecting Linodes booting across all regions. We will share additional updates as we have more information.

  2. investigating May 16, 2026, 01:06 AM UTC

    We are continuing to investigate this issue.

  3. identified May 16, 2026, 01:27 AM UTC

    The issue has been identified and a fix has been implemented.

  4. resolved May 16, 2026, 01:43 AM UTC

    This incident has been resolved.