Starting around 02:29 UTC on September 24, 2025, the autoscaling of Linode Kubernetes Engine (LKE) in US-Southeast Atlanta was impacted, and customers were unable to manage them as a result. The internal logs showed 5xx errors when customers attempted to manage LKE clusters associated with this cluster controller. The impact was limited to LKE cluster management (modification of nodepools, scaling, creating & deleting clusters) only, with all active customer workloads remaining unaffected.‌

The investigation revealed that the expiring certificates on cluster controllers were rotated on September 23, 2025. As part of the post-certification rollout work, the old certificates on associated controllers were revoked at 02:29 UTC on September 24, 2025, and the impact started following this action.‌

Further investigation indicated that the issue was caused by a certificate key mismatch between API endpoints and the cluster controller, which led to this issue. Akamai’s subject matter experts are continuing to investigate the root cause and will take appropriate preventive actions.‌

To mitigate the issue, we deployed a fix for this issue, followed by restarting the API endpoints. The impact was mitigated at 06:54 UTC on September 24, 2025. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence.‌

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.