I also no longer self-host a number of services myself, but thanks to "the Cloud", it's fairly trivial to "write five replicas of each repository across our three data centers to protect against failures at the server, rack, network, and data center levels". Uploading data to AWS S3/other cloud storage (with some additional, but fairly trivial scripting on top) gets you that same level of redundancy - or better! I don't want to be the person on-call when my self-hosted server's hard drive dies in the middle of my vacation, among other reasons, are why I use eg, GitHub.

There's an informed decision to be made when graduating from a computer in your basement, to a colo'd server, to using a VPS (or dedicated server) in the Cloud, to using a consumer facing online service. But if you're willing to have your data in the cloud, replication that used to take setting up multiple colo'd machines across the world (which I couldn't compete with, either) is fairly trivial these days. (A HA failover setup is left as an exercise to the reader.)