Amazon Web Services (AWS) resumed service after a server fault in Virginia led to the failure of the company’s cloudy systems, affecting services like Tinder, Netflix and IMDb that are dependent on the cloud service.
Amazon Web Services powers web and mobile applications, and it provides data processing and warehousing, storage, and archiving to websites across the globe.
Reports started appearing on Sunday morning after an AWS status page noted DynamoDB database issues at its US-East data centre complex in Ashburn, Virgina – which is the company’s oldest public-cloud facility.
The issue prevailed until afternoon when the database service reported increased error rates responding to Application Programming Interface (API) calls, which dragged other dependent services down.
CloudWatch, a monitoring system for the application that runs on the platform and Cognito, a mobile data based service also suffered outrage along with DynamoDB.
However, Amazon had to to throttle APIs to recover the service.
Some users complained of problems relating to streaming videos on Netflix, while others were having trouble with the Wink home automation hub’s that are dependent on AWS. Even Tinder users had trouble finding a date due to the outrage.
Amazon said: "The metadata service is now stable and we are actively working on removing throttles."
Earlier this year, Amazon AWS Health Dashboard faced DNS problems for end users on British Telecom ISP in the UK.
Users had trouble accessing several websites hosted on AWS but the company managed to solve the issue immediately.
AWS have stated that very few customers were entirely "down." Specifically, Netflix, was never down. Many users in the US-East region, however, did experience higher than usual error rates.
An AWS spokesperson, said: "Between 2:13 AM and 7:10 AM PDT on September 20, 2015, Amazon Web Services (AWS) experienced significant error rates with read and write operations for the Amazon DynamoDB service in the US-East Region, which impacted some other AWS services in that region, and caused some AWS customers to experience elevated error rates."