Amazon S3 went down Friday morning, causing numerous problems in Web applications that rely on the online storage service.
Graphics on Twitter and Tumblr were down as a result, one blogger states.
S3 users and an Amazon employee discussed the problem on a developer connection message board hosted by Amazon Web Services. The first poster on the thread reported an outage and "massive (500) internal server error".
"We are seeing the same thing with our Web site, which hosts all videos on Amazon S3," one poster wrote. "What is the ETA for getting this back up? Please keep us posted on the forums, since this is mission critical for some."
An Amazon Web Services employee named "Kathrin" said "we're investigating" just after the outage. Two hours later, she said the issue was resolved and performance was "returning to normal levels." But a further post by Kathrin acknowledged some lingering problems.
"This morning's issue has been resolved and the system is continuing to recover," she wrote. "However, we are currently seeing slightly elevated error rates for some customers and are actively working to resolve this. More information on that to follow as we have it. Also, we wanted to reiterate per our previous post that [we] will absolutely be posting technical information about what happened earlier this morning; our current priority of course is to ensure that the service recovers as quickly as possible and remains stable. We appreciate your patience while we do so."
Online "on-demand" storage services are becoming increasingly popular, and Amazon is one of the leading providers. The outage this morning served as a reality check to some customers who say it's good to have a backup plan in case the service fails as it did today.
"This is why you have to set up a fail-safe," one poster on the Amazon Web Services thread wrote. "My new sites host over 25,000 images on Amazon and I wake up to notice major issues this morning. I switched over to using my local server and everything is back up. . . . I really need to set something up so it does this automatically. The S3 service is great but this just proves you can't rely on it. This is a major issue especially since it's been down for so long. Way to go Amazon."
These types of "glitches" are inevitable, though, writes technology observer (and author of The Big Switch: Rewiring the World from Edison to Google) Nicholas Carr on his blog, noting his belief in "the utility mode of computing."
"How the supplier responds -- in keeping customers apprised of the situation and explaining precisely what went wrong and how the source of the problem is being addressed -- is crucial to building the trust of current and would-be users," Carr wrote.