7 Comments

Summary:

Amazon’s S3 cloud-based storage service went down earlier this morning, according to numerous tips we’ve received. The service has impacted many companies, including folks like Twitter. According to our tipsters, the service went down around 4:30 a.m., and is showing a 500 Internal Server Error message. […]

Amazon’s S3 cloud-based storage service went down earlier this morning, according to numerous tips we’ve received. The service has impacted many companies, including folks like Twitter. According to our tipsters, the service went down around 4:30 a.m., and is showing a 500 Internal Server Error message.

Read more over at GigaOm.

  1. Not at all. I don’t use it.

    Share
  2. [...] posts (on the Amazon outage): Rough Type, mathewingram.com/work, LinkFog, Data Center Knowledge, Web Worker Daily, [...]

    Share
  3. It is not impacted because I built in redundancy. The people that are complaining probably didn’t. If you rely on a single point of storage for mission critical data, well then, you’ve got bigger problems.

    Share
  4. Well, me personally…very little, I only host a few images on there for my personal site. The project I’m working on though was hit because it uses S3 for all of it’s images(inspirationfolder.com) but being the smart developer I am had a fail-safe built in so it switched over to using local images when S3 went down. It’s still not good but most people should have something like this in place.

    Share
  5. It impacting my grammar.

    Share
  6. I backup my iPhoto library nightly to Amazon S3 using the automated feature of JungleDisk. Last nigh’s backup completed successfully. I will see about tonight.

    Share
  7. So that’s why I can’t access it. I thought it was a problem with JungleDisk, but the reality is a little scarier. Time to start using a second online storage provider, I guess — maybe something that is reliable, like OmniDrive.
    Yes, that’s a joke.

    Share

Comments have been disabled for this post