"The problems began just after midnight US Pacific Time today when Amazon Web Services (AWS) noticed increased error rates and latencies for multiple services running within its home US-EAST-1 region. Within a couple of hours, Amazon's techies had identified DNS as a potential root cause of the issue, specifically the resolution of the DynamoDB API endpoint in US-EAST-1, and were working on a fix."
"As The Register reported earlier, Amazon.com itself was down for a time, while the company's Alexa smart speakers and Ring doorbells stopped working. But the effects were being felt by messaging apps such as Signal and WhatsApp, while in the UK, Lloyds Bank and even government services such as tax agency HMRC were impacted. According to a BBC report, outage monitor Downdetector indicated there had been more than 6.5 million reports globally, with upwards of 1,000 companies affected."
Just after midnight US Pacific Time, Amazon Web Services detected increased error rates and latencies in the US-EAST-1 region. Engineers identified DNS resolution of the DynamoDB API endpoint in US-EAST-1 as a potential root cause and worked on a fix. The DNS issue affected other AWS services and global features that rely on US-EAST-1 endpoints, including IAM updates and DynamoDB global tables. The outage disrupted Amazon.com, Alexa, Ring, messaging apps like Signal and WhatsApp, UK bank Lloyds, and government services such as HMRC. Downdetector recorded over 6.5 million reports and more than 1,000 affected companies. The incident exposed single-region dependencies and challenged cloud resiliency assumptions; AWS regions have multiple availability zones and customers are advised to design across AZs for fault tolerance.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]