Skip to content
OutageDeck

Incident detail

Emerging Service Issue - Networking in Washington, DC (US-IAD)

Emerging Service Issue - Networking in Washington, DC (US-IAD)

Resolved incidentMajor0 affected services

Timeline window

to

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    Our team is investigating an emerging service issue affecting networking in our Washington, DC location (US-IAD). We will share additional updates as we have more information.

  2. Investigating

    We are continuing to investigate the issue. We will share additional updates as we have more information.

  3. Investigating

    Our team has identified the issue affecting connectivity in our Washington 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. Identified

    Our team has identified the issue affecting connectivity in our Washington 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. Resolved

    We haven’t observed any additional connectivity issues in our Washington data center, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

  6. Resolved

    _On March 13, 2026, between approximately 17:35 UTC and 18:54 UTC, our Washington \(US-IAD\) data center experienced connectivity issues. During this time, customers may have noticed disruptions across all services hosted in this data center._  ‌ _Our investigation revealed that three servers previously used for testing were released back to inventory without the drives being wiped. As a result, one of these servers was sent to the warehouse and later returned to the Washington data center. This led to a host broadcasting an invalid path, which caused the service disruption._ ‌ _We promptly isolated the affected host, and service began to improve around 18:54 UTC. After thorough monitoring and system checks, we confirmed that the issue was fully resolved by 19:01 UTC._ ‌ _To help prevent similar issues in the future, we will conduct a detailed investigation to determine why this host was incorrectly configured and why our network propagated the invalid path. Based on our findings, we will implement corrective measures to prevent this type of misconfiguration from recurring._  ‌ _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._