[slillibri]

When I worked in web hosting (more than 10 years ago), we would constantly be blackholeing Hetzner IPs due to bad behavior. Same with every other budget/cheap vm provider. For us, it had nothing to do with geo databases, just behavior.

You get what you pay for, and all that.

[SoftTalker]

Yep I had the same problem years ago when I tried to use Mailgun's free tier. Not picking on them, I loved the features of their product but the free tier IPs had a horrble reputation and mail just would not get accepted especially by hotmail or yahoo.

Any free hosting service will be overwhelmed by spammers and fraudsters. Cheap services the same but less so, and the more expensive they are the less they will be used for scams and spams.

[thwarted]

Tragedy of the Commons Ruins Everything Around Me.

[haroldp]

It's always evolving, but these days the most common platforms attacking sites that I host are the big cloud providers, especially Azure. But AWS, Google, Digital Ocean, Linode, Contabo, etc all host a lot of attacks trying to brute-force logins and search for common exploits.

[UltraSane]

AWS tries hard to keep its public IPs from getting on banlists.

[oblio]

They could put the backend on Hetzner, if it makes sense (for example queues or batch processors).

[mzhaase]

I had to try multiple floating IPs on hcloud before I got one that wasn't blacklisted on the k8s repos.

[Keyframe]

depending on the prices, maybe a valid strategy would be to have servers at hetzner and then tunnel ingress/egress somewhere more prominent. Maybe adding the network traffic to the calculation still makes financial sense?

[srockets]

At 0.02$/GB, it rarely does.