Hi @bunjee
If snapshots or backups were generated on your account, they can be used to recover data from the point in time they were generated, though without snapshots or backups, recovery would not be possible as we do not maintain individual backups for customers.
Customers can generate live snapshots on the fly anytime by clicking the name of the Droplet, followed by Snapshots from the left menu, and then Create Live Snapshot, though backups would need to be enabled at the time the Droplet is deployed.
I know that this isn't a huge help given the size of the issue, though I mention it as backup strategy is always important and should be something that anyone should factor in when running their own web server(s).
Even the most reliable providers run in to issues and things do happen from time to time. I've seen numerous issues over the last 10-15 years, many far worse -- though I can understand how it'd be hard to imagine.
...
We are doing the best we can as quickly as possible. In cases where customers do have snapshots or backups, we'll be more than happy to guide them through the process of restoring them.
In cases where customers do not have backups or snapshots, unfortunately, we don't have an option to pull down data as it's not physically possible. Much like how if a customer accidentally deleted their own Droplet, we wouldn't be able to restore without a snapshot or backup in place, though they would have had to of generated that snapshot or enabled backups on the Droplet for us to do that.
...
That being said, we are a self-managed provider, which does mean the user is responsible for their hosted data, including backups and recovery -- we're available to help, and even recommend alternative options for data backup (I've made recommendations to numerous customers already), though we're not a fully managed provider that handles everything top to bottom -- we provide the services to allow customers to freely design and develop solutions and ultimately, it is up to them how they set things up and manage their deployments.
Please don't take that as me passing the blame, as that is certainly not what I am doing nor what I intend by the above statement (which is my own), just to be clear.
