AWS DynamoDB Outage Caused by DNS Resolution Issues

Technology News

AWS DynamoDB Outage Caused by DNS Resolution Issues
AWSDynamodbOutage
  • 📰 WIRED
  • ⏱ Reading Time:
  • 116 sec. here
  • 8 min. at publisher
  • 📊 Quality Score:
  • News: 67%
  • Publisher: 51%

Amazon's DynamoDB database experienced an outage in the US-EAST-1 region due to DNS resolution problems, impacting various services. The issue prevented the accurate translation of web URLs to server IP addresses. AWS has applied initial mitigations, but some services may still experience delays.

The outages stemmed from Amazon's DynamoDB database application programming interfaces in US-EAST-1, and AWS said in status updates that the problem was specifically related to DNS resolution issues. The “domain name system” is a foundational internet service that essentially acts as an automatic phonebook lookup to translate web URLs like www.

wired.com into numeric server IP addresses so web browsers show users the right content. DNS resolution issues occur when DNS servers aren't accurately connecting these dots and, to keep with the phonebook analogy, are providing the wrong numbers for a given name, or vice versa. “Based on our investigation, the issue appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1,” AWS wrote in status updates on Monday. Shortly after, the company added: “If you are still experiencing an issue resolving the DynamoDB service endpoints in US-EAST-1, we recommend flushing your DNS caches.” An AWS spokesperson did not immediately respond when asked for details about the nature of the failure. DNS resolution issues can be malicious—known as DNS hijacking—but there is no indication that Monday's AWS outages were nefarious. “When the system couldn't correctly resolve which server to connect to, cascading failures took down services across the internet,” says Davi Ottenheimer, a longtime security operations and compliance manager and a vice president at the data infrastructure company Inrupt. “Today's AWS outage is a classic availability problem, and we need to start seeing it more as data integrity failure.” Problems began around 3 am ET. By 5:22 am, AWS had applied “initial mitigations” that were starting to take effect. At 6:35 am, Amazon said that it had fully addressed the underlying technical issues but that “some services will have a backlog of work to work through, which may take additional time to fully process.” AWS has suffered other large-scale outages, including a major incident in 2023. Reliance on central cloud services from giants like AWS, Microsoft Azure, and Google Cloud Services has, in may ways, improved cybersecurity and stability around the world by creating a baseline of guardrails and best practices for all customers. But this standardization comes with major trade-offs, because the platforms become a single point of failure for large swaths of critical services. “Failures increasingly trace to integrity,” Ottenheimer says. “Corrupted data, failed validation or, in this case, broken name resolution that poisoned every downstream dependency. Until we better understand and protect integrity, our total focus on uptime is an illusion.”

We have summarized this news so that you can read it quickly. If you are interested in the news, you can read the full text here. Read more:

WIRED /  🏆 555. in US

AWS Dynamodb Outage DNS Cloud Computing

 

United States Latest News, United States Headlines

Similar News:You can also read news stories similar to this one that we have collected from other news sources.

AWS Outage Causes Smart Beds to Malfunction, Disrupting SleepAWS Outage Causes Smart Beds to Malfunction, Disrupting SleepAn Amazon Web Services (AWS) outage caused Eight Sleep smart beds to malfunction, leaving users with uncomfortable temperatures and positions, highlighting the reliance on cloud connectivity and the impact of service interruptions on smart home devices. Eight Sleep is now rolling out an 'outage mode' that allows for Bluetooth connectivity.
Read more »

AWS Outage Highlights Need for Proactive Prevention, Expert WarnsAWS Outage Highlights Need for Proactive Prevention, Expert WarnsA leading tech expert warns that the recent AWS outage, which disrupted major platforms, underscores the need for a shift from reactive incident response to proactive prevention in increasingly complex digital ecosystems. The outage, attributed to DNS resolution problems, impacted services like Snapchat, Fortnite, and Coinbase, highlighting the potential for widespread disruptions and the importance of anticipating potential points of failure to avoid prolonged outages and costly impacts.
Read more »

The Protocol: AWS Outage Halts Some Crypto AppsThe Protocol: AWS Outage Halts Some Crypto AppsAlso: Monad’s Tech, Quantum Computing and Bitcoin and Securitize’s MCP Server.
Read more »

The AWS Outage Borked People’s Pricey ‘Smartbeds’The AWS Outage Borked People’s Pricey ‘Smartbeds’Eight Sleep staff undoubtedly endured a sleepless night as the impact of the AWS outage spread to its neck of the woods.
Read more »

AWS Outage Latest—New Analysis Explains What Went Wrong And WhyAWS Outage Latest—New Analysis Explains What Went Wrong And WhyAmazon Web Services has explained what went wrong to cause the major outage that crippled many businesses this week. Here's what you need to know.
Read more »

AWS DynamoDB Outage Caused by DNS Resolution Issues in US-EAST-1AWS DynamoDB Outage Caused by DNS Resolution Issues in US-EAST-1Amazon's DynamoDB database suffered an outage in the US-EAST-1 region due to DNS resolution problems, impacting its ability to translate web URLs into server IP addresses. The issue began around 3 am ET and was partially mitigated by 5:22 am, with full resolution of the underlying technical issues announced at 6:35 am, though some services faced backlogs. Experts highlight the outage as a classic availability and data integrity failure.
Read more »



Render Time: 2026-04-01 19:53:14