3 ms·

> S3 is designed to provide “11 9’s” (99.999999999%) of durability Has anyone lost data on S3 or know anyone who has?

• gnrlst 6y ago
  There's different storage tiers, with different redundancy. So if anyone has an anecdote, would be curious to know which storage tier was used (e.g. single availability zone)
• ZiiS 6y ago
  If it works as designed I guess 1000 have; but how would you know. Did your perfect code running on an perfect CPU and RAM connected though a perfect network upload the file with 11 9's certainty?
  • donavanm 6y ago
    This is a real problem, but it is partially accounted for: > To ensure that data is not corrupted traversing the network, use the Content-MD5 header. When you use this header, Amazon S3 checks the object against the provided MD5 value and, if they do not match, returns an error. Additionally, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned ETag to the calculated MD5 value. It’s not as obvious with multipart uploads where each chunk is (iirc) individually checksumd and stored, but only a single md5 is returned in the “etag”
• pauldino 6y ago
  Not to me, but it’s happened. https://www.quora.com/Has-Amazon-S3-ever-lost-data-permanently/answer/Scott-Bonds https://www.quora.com/Has-Amazon-S3-ever-lost-data-permanent...
• rhacker 6y ago
  I imagine that in most cases it's a giant archive - data that no one really cares about (I mean they do in principal). Then there's probably like 0.1% that's probably operationally important data - which is actually huge. This is just a guess based on my own usage of it over the last 15 years at different companies.
• qrush 6y ago
  Yes. Once provided extensive documentation and debugging info they did refund portions of bills too.