New zero-day exploit for Log4j Java library is an enterprise nightmare
ALPHV BlackCat – This year’s most sophisticated ransomware
Volvo Cars discloses security breach leading to R&D data theft
Massive attack against 1.6 million WordPress sites underway
Microsoft: These are the building blocks of QBot malware attacks
Amazon explains the cause behind Tuesday’s massive AWS outage
Want to become a networking expert? Try this $69 Cisco course bundle
Researchers release ‘vaccine’ for critical Log4Shell vulnerability
Qualys BrowserCheck
Junkware Removal Tool
How to remove the PBlock+ adware browser extension
Remove the Search Redirect
Remove the Search Redirect
Remove the Search Redirect
Remove Security Tool and SecurityTool (Uninstall Guide)
How to remove Antivirus 2009 (Uninstall Instructions)
How to Remove WinFixer / Virtumonde / Msevents / Trojan.vundo
How to remove Google Redirects or the TDSS, TDL3, or Alureon rootkit using TDSSKiller
Locky Ransomware Information, Help Guide, and FAQ
CryptoLocker Ransomware Information Guide and FAQ
CryptorBit and HowDecrypt Information Guide and FAQ
CryptoDefense and How_Decrypt Ransomware Information Guide and FAQ
How to make the Start menu full screen in Windows 10
How to install the Microsoft Visual C++ 2015 Runtime
How to open an elevated PowerShell Admin prompt in Windows 10
How to Translate a Web Page in Google Chrome
How to start Windows in Safe Mode
How to remove a Trojan, Virus, Worm, or other Malware
How to show hidden files in Windows 7
How to see hidden files in Windows
IT Certification Courses
Gear + Gadgets
Amazon explains the cause behind Tuesday’s massive AWS outage
Amazon has published a post-event summary to shed some light on the root cause behind this week’s massive AWS outage that took down a long list of high-profile sites and online services, including Ring, Netflix, Amazon Prime Video, and Roku.
The outage started at roughly 10:30 AM EST on Tuesday. It affected the US-EAST-1 AWS region, which ensures connectivity for people and companies in the northeastern part of the United States.
As a result, streaming through Netflix, Amazon Prime, and Roku was immediately impacted together with Ring devices, brought down and unreachable, according to users reporting that they couldn’t connect to their cameras.
Around the same time, Amazon delivery employees began sharing on Reddit that they could no longer access internal apps required to scan packages, access delivery routes, or see upcoming schedules.
“At 7:30 AM PST, an automated activity to scale capacity of one of the AWS services hosted in the main AWS network triggered an unexpected behavior from a large number of clients inside the internal network,” Amazon explained in a summary of this incident.
“This resulted in a large surge of connection activity that overwhelmed the networking devices between the internal network and the main AWS network, resulting in delays for communication between these networks.
“These delays increased latency and errors for services communicating between these networks, resulting in even more connection attempts and retries. This led to persistent congestion and performance issues on the devices connecting the two networks.”
Our Support Contact Center also relies on the internal AWS network, so the ability to create support cases was impacted from 7:33 AM until 2:25 PM PST. We expect to release a new version of our Service Health Dashboard early next year that will make it easier to understand service impact and a new support system architecture that actively runs across multiple AWS regions to ensure we do not have delays in communicating with customers. – Amazon
The Tuesday AWS outage is definitely not unique as it follows multiple other similar events since 2011, including a large-scale incident that affected the same region in November 2020.
When it happened, it also brought down a large number of sites and online platforms after Amazon’s Kinesis service for real-time processing of streaming data began experiencing issues.
One year prior, during September 2019, a power outage that hit the AWS US-EAST-1 data center in North Virginia caused data loss for all Amazon customers lacking working backups to restore their files.
In February 2017, an Amazon’s S3 (Simple Storage Service) outage took down millions of small and high-profile sites and online platforms, including Adobe’s apps and services, Docker, Mailchimp, Medium, Signal, Slack, Trello, Twilio, IFTTT, and Twitch.
AWS outage impacts Ring, Netflix, and Amazon deliveries
This AWS exam prep bundle is just $5.70 for Cyber Week
Master the cloud with this pre-Black Friday deal on AWS training
Amazon is shutting down web ranking site
Some Tesla owners unable to unlock cars due to server errors
Not a member yet? Register Now
New zero-day exploit for Log4j Java library is an enterprise nightmare
Massive attack against 1.6 million WordPress sites underway
To receive periodic updates and news from BleepingComputer, please use the form below.
Terms of Use Privacy PolicyEthics Statement
Copyright @ 2003 – 2021 Bleeping Computer® LLC – All Rights Reserved
Not a member yet? Register Now
Read our posting guidelinese to learn what content is prohibited.


You May Also Like

MediaMarkt hit by Hive ransomware, initial $240 million ransom

State hackers breach defense, energy, healthcare orgs worldwideMediaMarkt hit by Hive ransomware,…

New 'Karakurt' hacking group focuses on data theft and extortion

New zero-day exploit for Log4j Java library is an enterprise nightmareALPHV BlackCat…

DHS announces 'Hack DHS' bug bounty program for vetted researchers

Microsoft December 2021 Patch Tuesday fixes 6 zero-days, 67 flawsBugs in billions…

Mozilla fixes critical bug in cross-platform cryptography library

FBI seized $2.3M from affiliate of REvil, Gandcrab ransomware gangsEwDoor botnet targets…