Skip to content

Incident detail

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

Resolved incidentMinor

Timeline window

to

Outage alerts

Get alerted the next time Linode breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update Linode posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

    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

    We are continuing to investigate this issue.

  3. Identified

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

  4. Resolved

    This incident has been resolved.

  5. Resolved

    On May 15, 2026, at 18:18 UTC, we identified an issue impacting the deployment of Linodes that relied on StackScripts (including all newly created Linode Kubernetes Engine (LKE) and (LKE-E) nodes), resulting in deployment failures. These deployment failures resulted in Linodes created with StackScripts to be unbootable and LKE autoscaling or recycling activity to fail.

    Subject matter experts determined that the cause of the issue was the removal of a credential parser during a recent update on compute hosts. This credential parser is used in the process of decoding StackScripts and its removal caused Linode deployments relying on StackScripts to fail.

    With the issue identified, we began to test a rollback at 01:10 UTC on May 16, 2026  and a reduction in failures was noted at 01:20 UTC. We mitigated the broader customer impact by  01:30 UTC on May 16, 2026.

    This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Keep exploring

More from Linode

Neighboring incidents on Linode's timeline and the rest of their record on OutageDeck.