By Prarthito Maity email: email@example.com | Dec 25, 2012 10:38 AM EST
Amazon has been in all kinds of problems all year long and as the year comes to an end, it doesn’t seem like the Amazon-related issues will come to a close anytime soon. Per reports, the Amazon cloud-based Netflix streaming service was down on Christmas Eve due to server issues.
The issue, which first surfaced after 1PM PT on Dec. 24, seems to be centered around the AWS center in Northern Virginia. While some may still state they can access the service, most of the users had complained that Netflix was down for them on Christmas Eve, mainly due to an outage of some of Amazon’s cloud infrastructure.
“Bunch of ELBs down, lots of happy Netflix instances getting no traffic, still waiting for AWS to fix it. Some devices working, others not,” stated a Twitter post from Adrian Cockcroft, Netflix cloud architect.
According to Amazon's official status page, the company started investigating these problems with its own services at 1:50PT. Later, as pointed out by GigaOm, Cockcroft confirmed on Twitter that AWS was the reason for the streaming problem. While there's no timeframe yet as to when Netflix's streaming will resume to normal, Cockcroft did state that the problem doesn't exist across all devices.
“We are investigating a number of environments in the US-EAST-1 region that are handling traffic successfully but are reporting an inaccurate RED health status,” the official report stated. “We have identified the issue and are working to fix the inaccurate RED environment health status reporting. Existing environments, while marked RED, continue to serve traffic successfully.”
The later posts mentioned that one of the heavily affected areas is North Virginia, with the area facing “Erroneous red health status.” The team assured that it was already on work to fix the service and was resolving issues with the Elastic Load Balancing Service in the US-EAST-1 region.
It was also confirmed that the issues were affecting both existing and newly created ELBs.
“While we are in the process of recovering the service, API calls for creating, modifying, or deleting ELBs will be disabled. We expect to restore full API service once the issues are resolved. We apologize for the impact of these issues on our customers,” the report added.