Linode Status

Current Status

Service Issue - Linode Kubernetes Engine and NodeBalancers

Incident Report for Linode

Postmortem

On November 21, 2025, at approximately 09:52 UTC, customers started reporting that their LKE API endpoints were dropping connections, preventing them from connecting to the LKE API server. Additionally, customers experienced connection timeouts and errors in NodeBalancers. This issue was observed in the following regions:

  • Newark (US-East)
  • Atlanta (US-Southeast)
  • Toronto (CA-Central)
  • Singapore (AP-South)
  • Mumbai (AP-West)
  • Frankfurt (EU -Central)

To effectively address the impact, Akamai restarted the service on route servers in the affected regions between 15:20 UTC and 15:39 UTC on November 21, 2025. The investigation revealed that the new certificates were not loaded on the route servers, leading to unsuccessful queries to the endpoints. Consequently, the route servers were unable to retrieve updates and persisted in operating with outdated data. Multiple products depend on the proper functioning and up-to-date data of the route servers, including:

  • Shared IP (customer peering / failover)
  • /56 and /64 ranges
  • NodeBalancers

The confirmation that all services were operating in accordance with established operational standards was received at 15:48 UTC on November 21, 2025. Following a monitoring period, we validated that the issue had been fully mitigated.

Customers were affected only if they updated the products listed above after the route servers stopped retrieving updates from the Akamai Compute’s internal backend API component. If no changes were made during the impact window, the stale data cached by the route servers remained valid for them. However, any new updates could not be processed due to the failing queries.

Akamai followed the same procedure in unaffected regions to prevent the recurrence of similar issues. Additionally, we will review automated processes and procedures and will implement enhancements in certificate rotations as needed.

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.

Posted Nov 24, 2025 - 20:28 UTC

Resolved

We haven’t observed any additional issues with the LKE and NodeBalancer services, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Posted Nov 21, 2025 - 17:51 UTC

Monitoring

At this time, we have been able to correct the issues affecting the LKE and NodeBalancers services. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
Posted Nov 21, 2025 - 15:49 UTC

Identified

Our team has identified the issue affecting the LKE and NodeBalancers services. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Posted Nov 21, 2025 - 15:27 UTC

Update

We have also confirmed this issue is impacting the NodeBalancer service in Atlanta, Frankfurt, Mumbai, Singapore, Newark, and Toronto data centers. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.
Posted Nov 21, 2025 - 14:59 UTC

Update

We are continuing to investigate this issue.
Posted Nov 21, 2025 - 14:30 UTC

Investigating

Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE) impacting networking to some cluster control planes. We will share additional updates as we have more information.
Posted Nov 21, 2025 - 13:26 UTC
This incident affected: Regions (US-East (Newark), US-Southeast (Atlanta), CA-Central (Toronto), AP-South (Singapore), AP-West (Mumbai)) and NodeBalancers (US-East (Newark) NodeBalancers, US-Southeast (Atlanta) NodeBalancers, CA-Central (Toronto) NodeBalancers, EU-Central (Frankfurt) NodeBalancers, AP-South (Singapore) NodeBalancers, AP-West (Mumbai) NodeBalancers).