[sho]

I use and love Hetzner as well. But you have to go into it eyes open. Concrete example - a month ago I was notified that network infra my systems ran over was going down for maintenance. Public link: https://status.hetzner.com/incident/ff8335b8-6fda-4370-8431-...

So, for me that was a production DB, fairly low usage but still. In the end I judged that it was going to take so much time to work around the outage that I just planned "maintenance downtime" myself and took it offline for a couple of hours until they finished.

Now, could I have architected better? No doubt. But it's a good reminder of what you're paying for and where the differences emerge in practise. AWS may be an overcomplicated, expensive mess - but I've literally never had any service of theirs go down for maintenance for any reason. Outages, sure, but taking things down for routine maintenace? Unheard of at AWS.

For me the formula is - I do whatever I want for my stuff, but if it's someone else's business, I use AWS.

[andreynering]

I have something on Digital Ocean and I receive emails about maintenance windows all the time.

So, not an exclusivity of Hetzner for sure.

[Ardren]

I don't remember ever having downtime on DO when I was using them.

I used to get those emails all the time, but the type of downtime they were talking about was extremely minimal (the entire point of VPS systems).

The last email I got about possible downtime was increased latency for the UI and API for ~10s last year. The email before that was ~5s of potential lost traffic to a droplet.

[sulandor]

tbf there are reasonably priced bare metal hosting providers that don't have maintenance or other regular outages.