← Live dashboard

Emerging Service Issue - LKE Enterprise - All Regions

ResolvedminorOfficial source confirmedGlobal service disruptionFirst recorded update Jun 5, 2026, 02:23 PM · Resolved Jun 5, 2026, 02:58 PM

This incident has been resolved.

Linode live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Linode now? Check the current status

Affected services

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 EngineAP-South (Singapore) Linode Kubernetes EngineAP-Northeast (Tokyo 2) Linode Kubernetes EngineAP-West (Mumbai) Linode Kubernetes EngineAP-Southeast (Sydney) Linode Kubernetes EngineSE-STO (Stockholm) Linode Kubernetes EngineUS-SEA (Seattle) Linode Kubernetes EngineJP-OSA (Osaka) Linode Kubernetes EngineIN-MAA (Chennai) Linode Kubernetes EngineID-CGK (Jakarta) Linode Kubernetes EngineBR-GRU (São Paulo) Linode Kubernetes EngineNL-AMS (Amsterdam) Linode Kubernetes EngineES-MAD (Madrid) Linode Kubernetes EngineIT-MIL (Milan) Linode Kubernetes EngineUS-MIA (Miami) Linode Kubernetes EngineUS-LAX (Los Angeles) Linode Kubernetes EngineGB-LON (London 2) Linode Kubernetes EngineAU-MEL (Melbourne) Linode Kubernetes EngineIN-BOM-2 (Mumbai 2) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineSG-SIN-2 (Singapore 2) Linode Kubernetes EngineJP-TYO-3 (Tokyo 3) Linode Kubernetes Engine

Updates (2)

  1. Jun 5, 2026, 02:58 PM
    Emerging Service Issue - LKE Enterprise - All Regions

    This incident has been resolved.

    Linode ↗
  2. Jun 5, 2026, 02:23 PM
    Emerging Service Issue - LKE Enterprise - All Regions

    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.

    Linode ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Linode's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.