Linode incident

Connectivity Issue - US-ORD (Chicago)

Minor Resolved View vendor source →

Linode experienced a minor incident on November 18, 2025 affecting US-ORD (Chicago) Block Storage, lasting 22h 29m. The incident has been resolved; the full update timeline is below.

Started
Nov 18, 2025, 06:19 AM UTC
Resolved
Nov 19, 2025, 04:49 AM UTC
Duration
22h 29m
Detected by Pingoru
Nov 18, 2025, 06:19 AM UTC

Affected components

US-ORD (Chicago) Block Storage

Update timeline

  1. investigating Nov 18, 2025, 06:19 AM UTC

    Our team is investigating an issue affecting connectivity in our US-ORD (Chicago) data center. During this time, users may experience intermittent connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information.

  2. investigating Nov 18, 2025, 07:35 AM UTC

    The investigation revealed that the issue is caused due to internal network connectivity. Due to this issue, Compute services/applications hosted in this data center will experience 5xx errors and timeouts. We are actively working on mitigation steps. We will provide the next update as we make progress.

  3. investigating Nov 18, 2025, 08:47 AM UTC

    We are continuing to investigate this issue. Subsequent updates will be provided as we make progress.

  4. investigating Nov 18, 2025, 09:18 AM UTC

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

  5. monitoring Nov 18, 2025, 10:10 AM UTC

    At this time, we have been able to correct the issues affecting connectivity in our US-ORD (Chicago) 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.

  6. monitoring Nov 18, 2025, 01:09 PM UTC

    We are continuing to monitor. If you are still experiencing issues, please open a Support ticket for assistance.

  7. resolved Nov 19, 2025, 04:49 AM UTC

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

  8. postmortem Nov 21, 2025, 01:10 AM UTC

    Starting around 03:05 UTC on November 18, 2025, the US-ORD \(Chicago\) datacenter \(DC\) started having network connectivity issues that led to intermittent packet loss. The Compute Object Storage service was impacted as a result. The proactive monitoring system detected this issue, triggering the internal alerts. The investigation revealed that the issue was caused due to an ASIC failure corrupting the forwarding table in one of the network routers in this DC. The problematic network router was isolated to mitigate the impact. The issue was mitigated at around 08:46 UTC on November 18, 2025. Akamai replaced the faulty network router and brought the network router into production service. We monitored the traffic after this step and confirmed that the services are restored and working as expected after replacing the network router. 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.