AWS Direct Connect connectivity loss

We are investigating connectivity issues impacting AWS Direct Connect connectivity to the US-EAST-1 Region.

We can confirm connectivity issues for some customers using AWS Direct Connect in the US-EAST-1 Region. During this time, some customers may be missing previously advertised routes from their VPCs to their on-premise locations, resulting in connectivity issues from VPC resources in the N.Virginia (US-EAST-1) Region. We have identified the root cause and are actively working on multiple parallel paths to mitigate this issue. We will provide additional information within the next 30 minutes.

AWS Direct Connect connectivity issues

We are actively working on restoring routes that were no longer being advertised. This is resulting in connectivity issues for some customers from VPC resources in N.Virginia (US-EAST-1) Region to on-premise locations. We have identified the root cause and are actively trending towards recovery. While we work toward restoring all affected routes, some customers may see intermittent recovery while others may experience impact until we have fully mitigated the issue. We expect full recovery in approximately 90 minutes, but we are actively working on ways to increase the velocity of recovery. We will continue to provide updates as we have additional information to share, or within the next 45 minutes.

We are seeing early signs of recovery, and continue to work toward full recovery.

We are seeing significant signs of recovery and continue to monitor to ensure full recovery.

Between 11:41 AM PST and 5:45 PM PST, we experienced connectivity issues for some AWS Direct Connect Customers in the US-EAST-1 Region. While the issue was introduced at 11:41 AM PST, impact was limited until approximately 1:30 PM PST when impact grew as a result of a subsystem deployment. Our automated deployment takes approximately 12 hours so impact stayed limited to a subset of customers until we began observing broader impact at approximately 3:00 PM PST. Engineers were engaged and began identifying the root cause. By 4:45 PM PST, we had identified the root cause and began mitigating affected routes. At 5:45 PM PST, all affected routes had been re-advertised and the issue was fully mitigated. During this time, customers may have experienced issues routing between their AWS VPC resources in N.Virginia (US-EAST-1) and their on-premise environments. We do not expect this issue to reoccur. The issue has been resolved and the service is operating normally.