Two weeks after Amazon's servers crashed causing dozens of websites to go down the company has finally issued an apology for what happened. Its explanation says an employee was trying to upgrade the server's capacity and messed up by shifting all of Amazon's server traffic to the wrong network (one that couldn't bear the load). "We want to apologize," said the company. "We know how critical our services are to our customers’ businesses and we will do everything we can to learn from this event and use it to drive improvement across our services." But not everyone's satisfied with the letter, which attempts to put the lid on a catastrophic week for many of its clients which ended up, in some cases, permanently destroying customer data. Here's what Amazon could've done better in the days since its servers crashed.
Timing This one goes without saying. It took two weeks for Amazon to apologize, a delay that made for a considerable headache for its customers. "One of the biggest criticisms of the whole affair was Amazon’s deafly silence," writes Zee at Read Write Web. "Startups and businesses were left to apologise to their customers because of Amazon’s failure."