[neeksHN]

Pretty fantastical post, seeing as Github had a severe outage on 1.27.2017. I'd also guesstimate Github has at least 2 to 3 major outages per year (a mix of DDoS and human errors)

Setting up a DigitalOcean droplet or AWS instance would have only added a few dollars and extra minutes to your transfer today. The benefit would be to reduce dependencies on external service that are vital to your core product.

Always remember, when you don't host your code you don't have full control of your code. To me having 100% ownership of your source should be the foundation to any software-driven organization

[oompahloompah]

This really applies to more than just code. Any time you rely on an outside provider you're opening up yourself to risks. Ultimately it comes down to whether or not you trust the ability of the provider to provide you with service more than you trust your own ability.

Really though, this situation is just re-hashing the fact that everyone has to be careful about single points of failure. If you're screwed because a single service provider you rely on is down you need to think about increasing redundancy. This goes for absolutely everything whether the service is for DNS, VPSes, or version control repositories.

[WettowelReactor]

Any time you rely on an outside provider you shift your risks around. Thinking that you eliminate risks by hosting yourself is simply not true. Whether using an outside provider increases your risks requires a case by case analysis.

[rxminus]

Yeah read about that one. I would like to avoid hosting our own code, but if Github proves to be too unreliable as well then indeed that will be our only option. But gitlab just had too frequent outages/slowdowns for me to feel comfortable staying. I don't expect 100% uptime, (as nothing does) but it's the frequency and consistency of outages that started to worry me.