I'm told that GitHub has asserted to us that moving to this model means we would not be exposed to github.com outages. It's not at feature parity with github.com though.

nr378 7 hours ago | parent | next [-]

Thanks, this option is good to know.

We're currently on "GitHub Enterprise Cloud" on github.com and are affected by this outage (even though we use self-hosted runners!), but we're not on "GitHub Enterprise Cloud with data residency" on *.ghe.com, which I understand is/may not be affected by this outage?

	▲	saxonww 4 hours ago \| parent [-]
		This is what they've told us. It's represented as basically a separate deployment of the entire GHEC stack, so you're not exposed to the load/scaling issues they believe are the underlying cause of all the github.com outages today.

▲

annzabelle an hour ago | parent | prev | next [-]

The last large company I worked for switched from self hosted github enterprise to github.com in January 2025 or so.

I wonder how much egg is on that exec's face.

▲

herpdyderp 7 hours ago | parent | prev [-]

Do you have any meaningful level of faith in GitHub's ability to deliver on stability? At this point, I have none.

	▲	saxonww 4 hours ago \| parent \| next [-]
		Meaningful is subjective, but yes I do. It was very stable for many years, and I do believe the recent issues are mostly or all because they were caught flat-footed by the rapid AI-driven load increases. This has been a bad time, though. I'm ready to move back to self-hosting if they can't get it together or we move to GHDR and it's still bad.
	▲	creshal 5 hours ago \| parent \| prev [-]
		A lot of the stability problems come from trying to scale a free product on a still WIP cloud solution without costing too much; the same software running on separate, paid for infra has a lot better odds.