Linode Status · History · Incident #3743
RESOLVEDService Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]
Minor · Started May 16, 2026 · 12:42 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Linode Status · History · Incident #3743
RESOLVEDMinor · Started May 16, 2026 · 12:42 AM
Duration
1h 1m
Severity
Minor
Detection lead
—
User reports
—
Summary
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.
Started
May 16, 2026 · 12:42 AM
Resolved
May 16, 2026 · 1:43 AM
Duration
1h 1m
Severity
None
Event timeline
Investigating
May 16 · 12:42 AM LinodeOur team is investigating an emerging service issue affecting Linodes booting across all regions. We will share additional updates as we have more information.
Investigating
May 16 · 1:06 AM LinodeWe are continuing to investigate this issue.
Identified
May 16 · 1:27 AM LinodeThe issue has been identified and a fix has been implemented.
Resolved
May 16 · 1:43 AM LinodeThis incident has been resolved.
Postmortem
May 20 · 7:15 PM LinodeOn 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.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026