- Level
- confirmed
- Worst impact
- Partial outage
- Components
- DIRECTCONNECT
- Regions
- us-east-1
- Down Index
- 58of 100
What to do
Check whether you use AWS DIRECTCONNECT in us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 35m it lasted.
Anything that failed between 2026-02-21 00:38 UTC and 2026-02-21 02:13 UTC may need a replay.Subscribe to AWS's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=aws works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from AWS 6
- investigating
We are investigating connectivity issues impacting AWS Direct Connect connectivity to the US-EAST-1 Region.
provider
- investigating
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.
provider
- investigating
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.
provider
- investigating
We are seeing early signs of recovery, and continue to work toward full recovery.
provider
- investigating
We are seeing significant signs of recovery and continue to monitor to ensure full recovery.
provider
- investigating
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-e5b15a39cb
Is AWS still down?
No, this incident was resolved 2026-02-21 02:13 UTC. For AWS's live state, see https://down.guide/aws.
How long did it last?
1h 35m, from 2026-02-21 00:38 UTC to 2026-02-21 02:13 UTC, by the times AWS posted.
What was affected?
AWS named DIRECTCONNECT in us-east-1.
What caused it?
AWS hasn't published a root cause. If it does, it shows here.
Where does this come from?
AWS's official status page, https://health.aws.amazon.com/health/status, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.