We did have a disaster recovery plan in place, and we implemented it.
It is my opinion that killing public access to a paying customer's server without talking to them first, and not providing any remedy for 60+ hours, is definitely something that DO support deserves blame for.
from the other reply it sounds like you made up your disaster recovery scenario on the fly.
DigitalOcean (and a lot of IaaS providers like them) expect you to create new servers on demand because the underlying hosts aren't 100% reliable. It could have been a RAID failure or a bad PDU feeding a rack or a number of other scenarios that would have taken your droplet offline, not just an abuse ticket.
Comments
We did have a disaster recovery plan in place, and we implemented it.
It is my opinion that killing public access to a paying customer's server without talking to them first, and not providing any remedy for 60+ hours, is definitely something that DO support deserves blame for.
from the other reply it sounds like you made up your disaster recovery scenario on the fly.
DigitalOcean (and a lot of IaaS providers like them) expect you to create new servers on demand because the underlying hosts aren't 100% reliable. It could have been a RAID failure or a bad PDU feeding a rack or a number of other scenarios that would have taken your droplet offline, not just an abuse ticket.