You can get more uptime (99.95%), more IPs, better and faster support with their business service (35 EUR / month).
Also, depending on the nature of your application, you can often get away with that kind of downtime. Something trivial (yet extremely popular) like Twitter had lots of down-time and it made the users love the service even more.
http://www.theatlantic.com/technology/archive/2015/01/the-st...
I think the main lesson here is that your error messages are part of your UX and need to be treated as such.
In that time I've had* one network issue < 1 hr and one instance where the server rebooted unexpectedly. Any other downtime has been either on purpose by me or accidentally by my hand. I can't even recall any scheduled maintenance that's taken my server offline.
* That I've noticed in my elsewhere-hosted monitoring.
My only complaint if I can even call it that is that the price of the server doesn't keep up with the specs they're selling - i.e. if you can get a server with <x> resources for cheaper than my server with <x-1> resources my price should come down to avoid me churning it). Having said that I don't know anywhere that actually does that and for reliability reasons it's probably better to cycle machines out when they get old enough for it to be worth the savings.
The only thing that rubbed me the wrong way is that they downright refuse to delete your credit card from their system when you terminate your (fully paid) account.
But they are not the only ones (not that this makes it good)... Linode did the same to me, I asked kindly after their latest data breach and they refused to do so.