Forum Moderators: phranque
If you don't have any complex SQL database on the back of it you could copy it all down to a local webserver at your house.....use DNS forwarding to point it to the IP at your house when your host goes down. Then swap it back when your host comes back online.
If any of the 3 answers are unsatisfactory, immediately look into changing to a different host.
Since you are their client, it is completely up to you how you define "unsatisfactory." My "satisfactory" level would be along the lines of:
1) Nearby construction crews cut Internet backbone cable and it took 30 hours to restore service.
2) Have purchased redundant connections from alternative providers to ensure that connectivity remains even if access to one provider dies.
3) A bare minimum of 5% of my monthly hosting/co-location fee. Your contract with them probably absolves them of any liability for lost revenue, so you probably can't expect to get much from them.
When Hurricane Wilma hit the coast of Florida the DNS server got knocked out for about 30 hours. The generator,which was supposed to keep running, got knocked out by the hurricane. So my sites were still up, but a large group of people couldn't access them. It was very frustrating.
Stuff happens. The company in Florida is one of the most reputable, stable companies out there.
Still, you could ask for a refund, or an extra month free, or something like that. The worst they could say is "no."