AWS introduces DNS resilience upgrade after US East failures

AWS is making a noticeable shift in how it handles one of its most heavily scrutinized pain points: the recurring failures in its US East region that often ripple across the internet. In a new update, the company has rolled out additional DNS resilience features meant to help customers keep control of their domain changes during regional disruptions, a scenario that has historically left many businesses stuck waiting for systems to recover before they could act.

The change comes after years of customers asking for something more dependable than hoping the next US East incident would be mild. According to AWS, organizations in tightly regulated fields have repeatedly stressed that they need a way to adjust DNS settings even when an outage affects one of Amazon’s busiest regions. Banks, financial platforms and SaaS providers, in particular, want the ability to redirect traffic or activate standby environments without being held hostage by regional downtime.

AWS now promises that customers will be able to perform DNS updates within a 60-minute recovery window during a disruption in US East. The commitment represents a small but meaningful improvement for teams that have often watched outages in the region unfold with little ability to intervene in real time. Even so, a full hour leaves plenty of room for widespread interruption if a failure hits at the wrong moment, a reality that AWS itself acknowledges.

The very existence of this feature is a quiet admission that US East remains a trouble spot despite years of criticism and multiple high-profile events. Past outages, including the DynamoDB incident and additional region-level failures in 2021 and 2023, amplified concerns that the scale of the region creates fragile pressure points. While AWS has pushed back on the idea that US East is less reliable than others, it has repeatedly conceded that its size magnifies any issue that occurs.

This update does not eliminate the risk of cascading outages, but it signals that AWS is trying to give customers at least some levers to pull when the region falters. For many businesses that depend on fast DNS adjustments to keep services reachable, that alone marks a shift worth noting.