Most people complaining about uptime aren't free users or open-source developers. It's people whose companies are enterprise GitHub customers. It's a real problem and affects productivity.
replyGitHub going down during office hours in a large enterprise has knock on effects for hours as well. Especially if you are in a monorepo.
replydeleted
replyI'm happy to report that my one-person sysops has successfully hit nine-fives for the 20th year in a row!
replyIf there's only a 9 in availability, they've got a minimum downtime of 87.6 hours per year (98.99999999999999999%)
replyHonestly, you're right - 2̶7̵ 87+ (correction from sibling) hours per year is absolutely fine & normal for me & anything I want to run. I personally think it should be fine for everybody.
replyOn the other hand the baseline minimal Github Enterprise plan with no features (no Copilot, GHAS, etc.) runs a medium sized company $1m+ per annum, not including pay-per-use extras like CI minutes. As an individual I'm not the target audience for that invoice, but I can envisage whomever is wanting a couple of 9s to go with it. As a treat.
87 hours a year is 1.5 hours a week. If that 1.5 hour window is when you need to use it it matters a hell of a lot more than if it’s 4am on a Sunday.
reply