Amazon Web Services Experiences Outages Sunday Morning, Causing Outages On

Amazon Web Services Experiences Outages Sunday Morning, Causing Outages On photo Amazon Web Services Experiences Outages Sunday Morning, Causing Outages On

Jeff Bezos, the founder of Blue Origin and Amazon.com, speaks at a press conference to announce the new BE-4 rocket engine during a press conference with Tory Bruno, CEO of United Launch Alliance, at the National Press Club September 17, 2014 in Washington, DC.



Amazon Web Services (AWS), the popular cloud hosting provider, suffered a glitch yesterday that affected numerous customers who rely on its public cloud infrastructure such as Netflix, Tinder and IMDb.

According to Amazon, services were back to normal by Sunday lunchtime, but some websites were still experiencing issues long into Sunday evening.

According to Amazon status reports, the service outage was caused by DynamoDB database issues at the company’s massive data centre complex in Ashburn, Virginia, which supports Amazon services for East Coast and beyond. This practice helps many of these corporations cut costs on building their own data centers but at the price of being dependent on their provider.

The server failure has meant that some customer access to Product Hunt, Medium, SocialFlow, Buffer, GroupMe, Pocket, Viber, and Amazon Echo amongst others has been stopped temporarily.

The 2013 crash lasted for 40 minutes and Buzzfeed reported that the company lost about $1,104 in average net sales per second during that time. While the problem is now fixed, many web enthusiasts took to Twitter to complain about the outage.

An Amazon Web Services health dashboard on Monday reported that services were running correctly. CloudWatch, a monitoring system for the application that runs on AWS and Cognito, a mobile data based service, also had problems alongside DynamoDB.

Leave a Reply