6 ms·

I love multiple 9s as much as the next guy but that's only 27 hours per year of downtime. For a mostly free (for me) service, I'm thankful.

malfist 6mo ago
If there's only a 9 in availability, they've got a minimum downtime of 87.6 hours per year (98.99999999999999999%)
wavemode 6mo ago
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.
- deleted 6mo ago
  [deleted]
- sefrost 6mo ago
  GitHub going down during office hours in a large enterprise has knock on effects for hours as well. Especially if you are in a monorepo.
skeeter2020 6mo ago
I'm happy to report that my one-person sysops has successfully hit nine-fives for the 20th year in a row!
lucideer 6mo ago
Honestly, 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. On 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.
- maccard 6mo ago
  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.
siren2026 6mo ago
The issue is also that those 27 hours don't happen at once, They happen in small chunks of a couple minutes which makes it happen almost everyday and has a ton of downstream build and retry issues. The resulting downtime is probably 2 orders of magnitudes higher at least.
gymbeaux 6mo ago
Those 27 hours only seem to happen during the workday when I’m trying to push branches, run CI pipelines or otherwise use GitHub (I don’t use Copilot). Whatever the yearly figure, it’s been a pain in the ass these last few months and it’s unacceptable, free or no (my company pays for GitHub).

malfist 6mo ago

If there's only a 9 in availability, they've got a minimum downtime of 87.6 hours per year (98.99999999999999999%)

wavemode 6mo ago

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.

deleted 6mo ago
[deleted]
sefrost 6mo ago
GitHub going down during office hours in a large enterprise has knock on effects for hours as well. Especially if you are in a monorepo.

skeeter2020 6mo ago

I'm happy to report that my one-person sysops has successfully hit nine-fives for the 20th year in a row!

lucideer 6mo ago

Honestly, 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. On 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.

maccard 6mo ago
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.

siren2026 6mo ago

The issue is also that those 27 hours don't happen at once, They happen in small chunks of a couple minutes which makes it happen almost everyday and has a ton of downstream build and retry issues. The resulting downtime is probably 2 orders of magnitudes higher at least.

gymbeaux 6mo ago

Those 27 hours only seem to happen during the workday when I’m trying to push branches, run CI pipelines or otherwise use GitHub (I don’t use Copilot). Whatever the yearly figure, it’s been a pain in the ass these last few months and it’s unacceptable, free or no (my company pays for GitHub).