[codingdave]

That bites.

At the same time, this is why the concept of "business continuity" exists. If you are running a hobby-level service, it may not be worth the trouble, but for anything where the continued existence of the service truly matters, you should have a plan in place of what to do when (not if) your host blows up and leaves you with nothing. That should include the ability to re-launch the code/database/server/whatever on a new host, and restore the latest data backup to that new host.

I get that planning ahead for such things increases the work to launch a service - but anything short of it means you are not in control of your own destiny.