Linode incident

Service Issue - Linode Automated Networking

Notice Resolved View vendor source →

Linode experienced a notice incident on July 1, 2026 affecting Cloud Manager and API, lasting 1h 6m. The incident has been resolved; the full update timeline is below.

Started
Jul 01, 2026, 05:21 PM UTC
Resolved
Jul 01, 2026, 06:28 PM UTC
Duration
1h 6m
Detected by Pingoru
Jul 01, 2026, 05:21 PM UTC

Affected components

Cloud Manager and API

Update timeline

  1. identified Jul 01, 2026, 05:21 PM UTC

    Our team is investigating a service issue that affects the auto configuration of networking on Linodes by Network Helper to fail. During that time, some users may have Linodes provision but appear to have no connectivity. This also can impact Linodes created by the Linode Kubernetes Engine and impact autoscaling or provisioning of clusters. Customers can still manually configure networking via the LISH console to mitigate this issue. Please see our guide on manual network configuration on a Compute Instance. We will share additional updates as we have more information.

  2. monitoring Jul 01, 2026, 06:09 PM UTC

    A fix has been implemented to resolve the automated network configuration issue on Linodes using Network Helper. We recommend rebooting your Linode to restore full network functionality. We are actively monitoring the results to ensure continued stability.

  3. resolved Jul 01, 2026, 06:28 PM UTC

    We haven’t observed any additional issues with the Linode Automated Networking service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.