Just In
- 11 hrs ago Dell Introduces AI-Powered Laptops and Mobile Workstations for Enterprises in India
- 13 hrs ago Meta AI Powered by Llama 3 Takes Aim at ChatGPT and Gemini: All You Need to Know!
- 14 hrs ago OnePlus Ace 3 Pro Leak Hints at New Design; Expected Launch, Specifications We Know So Far
- 14 hrs ago Vivo V30e Launch Date in India set for May 2: Flipkart Availability Confirmed
Don't Miss
- Finance FREE, FREE, FREE! 3:1 Bonus: Pharma Stock Hits Back-To-Back Upper Circuits; 500 Shares To Earn Rs 1,69,500
- Sports Manchester City vs Chelsea LIVE Streaming: Where to Watch FA Cup Semi-Final in India, UK, USA and Other Countries
- Movies Pukaar Dil Se Dil Tak Promo: Sayli Salunkhe Impresses In First Video Of Sony TV Show, Details About Her Role
- Lifestyle Golden Rules To Follow For Happy Marriage For A Long Lasting Relationship
- News Chinese President Xi Jinping Orders Biggest Military Reorganisation Since 2015
- Education Exam Pressure Does Not Exist; Studying Punctually is Crucial; Says Aditi, the PSEB 2024 Topper
- Automobiles Suzuki Swift Hatchback Scores 4 Star Safety Rating At JNCAP – ADAS, New Engine & More
- Travel Journey From Delhi To Ooty: Top Transport Options And Attractions
Amazon Web Services outage was caused by a typo
It was a typo that caused the issue!
The Amazon Web Services went down a few days back causing a number of websites such as Netflix, Quora, Spotify, Pinterest, Trello, Slack, Buzzfeed, etc go down. Even the website that is meant to check if the other sites are working fine was down due to the disruption in the service.
Following the outage, Amazon investigated the matter to find the root cause. Amazon didn't stop there but revealed the reason officially bringing clarity in the matter. As per Amazon, a single typo (a wrong command) executed by an employee is the prime cause of the cascading effect that took a number of websites down.
It was an employee of the Amazon S3 (Simple Storage Service) team, who caused the outage. While conducting a routine debugging operation, the employee meant to take down a few servers those handled the S3 billion process but a large number of servers were removed due to a typo one of the inputs in the given command.
Amazon Web Services outage creates chaos among internet users
While the four hours of disruption is said to have caused an estimated loss of $160 million, Amazon has announced that it is working on steps that will make sure a similar disruption does not happen again in future. The company has implemented automatic checks, where the capacity will be removed slowly. This way, any incorrect command will not disrupt the services in the future.
-
99,999
-
1,29,999
-
69,999
-
41,999
-
64,999
-
99,999
-
29,999
-
63,999
-
39,999
-
1,56,900
-
79,900
-
1,39,900
-
1,29,900
-
65,900
-
1,56,900
-
1,30,990
-
76,990
-
16,499
-
30,700
-
12,999
-
62,425
-
1,15,909
-
93,635
-
75,804
-
9,999
-
11,999
-
3,999
-
2,500
-
3,599
-
8,893