←back to thread

Days since last GitHub incident

(github-incidents.pages.dev)
212 points AquiGorka | 2 comments | 11 Dec 25 16:52 UTC | HN request time: 0s | source
Show context
behnamoh[dead post] ◴[11 Dec 25 17:16 UTC] No.46234123[source]▶
[flagged]
llbbdd ◴[11 Dec 25 17:18 UTC] No.46234170[source]▶
I don't work at Github but I'd read here recently that they've been undergoing a herculean migration from whichever cloud provider they were on to Azure since their Microsoft acquisition, and that it coincides with an increase in outages. I'm guessing that the solution here was probably just to not do that and it's too late.
replies(2): >>46234544 #>>46235692 #
1. nightpool ◴[11 Dec 25 19:08 UTC] No.46235692[source]▶
They weren't on any cloud provider previously. They famously had their own "metal cloud" of managed servers with everything being containerized and managed by Kubernetes. It seemed like it's worked pretty well, especially for their complex git operation tasks which had specific hardware requirements, but the official word is that apparently they're running into scaling limits with finding new datacenter capacity.
replies(1): >>46236218 #
2. llbbdd ◴[11 Dec 25 19:47 UTC] No.46236218[source]▶
Yikes, that's worse, I thought the migration was at least a little politically motivated to reduce a dependency on a competitor like AWS or something. It's not exactly a great advertisement in any case to know that bare metal was more reliable for them than their own infrastructure when they now own it all the way through.