Linode incident

Connectivity Issue - Linodes in Milan, Italy

Minor Resolved View vendor source →

Linode experienced a minor incident on July 20, 2026 affecting IT-MIL (Milan), lasting 2h 18m. The incident has been resolved; the full update timeline is below.

Started
Jul 20, 2026, 01:52 AM UTC
Resolved
Jul 20, 2026, 04:10 AM UTC
Duration
2h 18m
Detected by Pingoru
Jul 20, 2026, 01:52 AM UTC

Affected components

IT-MIL (Milan)

Update timeline

  1. investigating Jul 20, 2026, 01:52 AM UTC

    Our team is currently investigating a connectivity issue affecting Linodes in the Italy (Milan) region. During this time, existing Linodes in this location may be unreachable. Please note that creating new Linodes is functioning normally and remains unaffected.

  2. investigating Jul 20, 2026, 02:56 AM UTC

    We are continuing to investigate this issue. We will provide the next update as we make progress.

  3. investigating Jul 20, 2026, 03:12 AM UTC

    Our team has identified the issue affecting connectivity in our Milan (Italy) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

  4. monitoring Jul 20, 2026, 03:20 AM UTC

    At this time, we have been able to correct the issues affecting connectivity in our Milan (Italy) data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.

  5. resolved Jul 20, 2026, 04:10 AM UTC

    We haven’t observed any additional connectivity issues in our Milan (Italy) data center and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

  6. postmortem Jul 20, 2026, 05:45 AM UTC

    Starting around 00:33 UTC on July 20, 2026, some hosts in the Milan, Italy data center became unavailable, impacting customer access to Linodes. The investigation identified that this issue occurred during scheduled router firmware updates. While we follow a phased upgrade process to prevent service disruption, an unexpected intersection of concurrent maintenance activities led to a temporary loss of network connectivity for the affected hosts. Service was fully restored by 02:16 UTC on July 20, 2026, and all systems are now operating as expected. Internally, we are reviewing our change management and maintenance scheduling procedures to ensure better coordination and prevent similar impacts in the future. 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.