The current status update says that its now resolved:<p>>Update June 14th, 2014, 10:20 AM PDT: Stability on the DreamObjects cluster has been restored. Requests appear to be resolving properly now that the system has had time to re-balance itself. Our test are reporting properly now. If you do have any questions or concerns, please contact support contact support.<p>I'm quite interested to know what went on in particular, as I'm far more interested in Ceph than in commercial object stores that I can't extend. Librados is pretty damn awesome too, and I can foresee implementing some highly distributed storage through that directly.<p>With DreamObjects, it sounds like some API servers went down, and failure happened such that it couldn't serve some requests until the appropriate nodes came back.<p>It appears that with Ceph it will be easy to keep enough replicas such that data is not lost, but high availability is still being hashed out. Hopefully the lessons from this failure guarantee that this particular failure mode doesn't happen again.
Status update says they're running Ceph, an S3 work-alike. I don't want to say "clone" because nobody outside Amazon really knows how S3 works, and Ceph merely has an external HTTP API that supposedly works the same way. Is anybody running Ceph at scale and might be able to comment on what broke down?
How is the performance of DreamObjects?<p>For people who are actually on a budget for their projects, which is more than you might think, if the reliability is OK, this might make a lot of sense over paying much more to use the real S3 for backups.
The name of the service is DreamObjects. No affiliation to Dreamhost but doing something as basic as storing files as a service hardly deserves to be called a clone.
It seems they copied AWS S3 <i>too well</i>, including its "feature" of going down every now and then and it's overall lack of reliability. Nice!