As too many of us know, Netflix Christmas Eve crashed and burned. The outage lasted from 1 pm to after midnight Pacific time. Once again, it was Amazon Web Services (AWS) where the problems occurred. Specifically, the “Elastic Load Balancer” started generating errors at 1:50 pm Pacific time according to the AWS Service Health Dashboard. To Amazon’s great credit, they are transparent about problems that occur and keep their log files reasonably up to date with progress reports. But, let’s face it, a service outage of ten hours is unacceptable. Wired.com has pretty good coverage, as does Techcrunch.com. Others have covered the basic story, so all I’ll try to do here is fill in some details and add some editorial commentary. But first, some humor.
Best comment so far is on Wired.com:
“Daren_Gray • North Virginia. Maybe the NSA needed the server space to make sure their holiday naughty/nice list does not omit a single American. Somewhere over Whoville a drone waits for a kill order. Netflix will have to wait.”