←back to thread

Days since last GitHub incident

(github-incidents.pages.dev)
212 points AquiGorka | 5 comments | | HN request time: 0.409s | source
Show context
behnamoh[dead post] ◴[] No.46234123[source]
[flagged]
1. llbbdd ◴[] 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 #
2. blahyawnblah ◴[] No.46234544[source]
Yes I would image the issues are due to doing a migration period. Not the fact that it's moving to Azure in and of itself.
replies(1): >>46236343 #
3. nightpool ◴[] 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 #
4. llbbdd ◴[] 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.
5. llbbdd ◴[] No.46236343[source]
I won't blame Azure directly without a direct reason to, but as a developer often in the market for cloud providers it's definitely not the most reassuring that they're seemingly having so many migration pains.

A bit of an aside, I've only personally used Azure on one project at one company but their console UI had some bizarre footguns that caused us problems more than once. They have a habit of hiding any controls and options that your current logged-in user doesn't have permissions to use. In some cases that manifested as important warnings or tools that I wasn't even aware of (and were important to me!), but the owner of the company and other global admins could see. AWS, at least for a lot of the services last time I used it, was comfortable greying most things out with a tooltip telling you your user is missing X permission, which was way more actionable and the Azure version gave me whiplash by comparison.