The Effects Of The Amazon Web Services Outages
There has been no major cloud computing outage in 2012. However, non-believers had a field day when Amazon Web Services customers experienced some service disruptions on June 14. Although AWS went offline for a few hours only, the downtime experience did have an impact on customers’ businesses. According to reports, a power outage struck Amazon’s Northern Virginia datacenter. Internet sites and startups such as Heroku, Quora, Pinterest, and Parse were affected. Heroku filed an incident report. As per Amazon’s Service Health Dashboard, the problem was reported before 9 p.m. Pacific Time. The power outage affected AWS Elastic Beanstalk, Amazon Relational Database Service, and Amazon Elastic Compute Cloud, which are all housed at its datacenter in North Virginia. The services were fully restored in a few hours.
The outage was clearly not IT-related, but Amazon did receive a lot of flak for the service disruption. A large number of comments have been posted online from people from all walks life, even from the company’s competitors and non-clients. In a nutshell, the lesson cloud computing services users must learn is that they must spread their workloads across various parts of Amazon Web Services in order to prevent being hugely affected if an individual AWS region experiences service disruption. In most cases, such service disruption is often blown out of proportion. Customers who are having doubts regarding the credibility of cloud computing service providers will likely stay out of the cloud and still prefer to buy more expensive IT products hosted on-premise.
In April 2011, the North Virginia datacenter suffered a similar service outage which affected GroupMe, Quora, Reddit, HootSuite, Twitter, and Foursquare. Amazon reported that the outage was a “re-mirroring storm”. At that time, only the relational database service and the Amazon EC2 at the North Virginia center were affected, but it did affect many customers’ services and websites. What is surprising is that even though AWS experienced some outages, the company is continuously growing. Amazon reported that its S3 storage has more than a trillion objects, which is 143 times the population of the world.
According to a recent report by the International Working Group on Cloud Computing Resiliency, a minimum of 10 hours are lost because of service disruptions yearly. The group found out that since 2007 a minimum of five hundred hours has been lost as reported by the thirteen biggest cloud computing service providers, which can be translated in economic terms to be worth a minimum of $70 million. In that same report, the group claims that a cloud computing service is usually down for an average of 7.5 hours each year, although an electric power service outage is pegged at a low 15 minutes yearly.
The group gathered the data from various sources such as Twitter, Amazon, Google, Paypal, Yahoo, Microsoft, Facebook, and others. It is estimated that the travel service provider Amadeus loses $89,000 per hour during any cloud computing outage, while Paypal loses around $225,000 per hour. There is no known data for the number of people affected by a cloud computing service outage.
By Florence de Borja
- Negotiating Tips On Software-As-A-Service Contracts - August 9, 2012
- How You Can Take Advantage Of The Cloud - August 7, 2012
- How Can Cloud Computing Help Small And Medium Enterprises - July 30, 2012
- How Microsoft Can Recover Its #1 Spot - July 19, 2012
- Common Threats To Cloud Computing - July 16, 2012