> if you don't need any of the features that GitHub offers
In particular, all of the new features whose addition causes instability.
I think it's the development process (as in moving things around and potentially introducing bugs) than the new features per-se.
With all due respect to the developers, it would not speak well for GitHub if they can't maintain stability while refactoring. There's a lot of testing processes and CI processes explicitly around making those actions safe.
New features breaking is a lot more understandable - even expected - than regressions and refactoring failures.
The problem is that ultimately the downtime itself matters and not the reason, and if you don't need any of the features that GitHub offers, then the self-hosted route is a better option.