4 ms·
Frequent enough to interrupt the flow of an entire organization, wasting thousands of hours. Take a look: https://mrshu.github.io/github-statuses https://mrshu
by khaledh 7mo ago
Frequent enough to interrupt the flow of an entire organization, wasting thousands of hours. Take a look:
https://mrshu.github.io/github-statuses https://mrshu.github.io/github-statuses
- gobalini 7mo agoYeah that is pretty bad I guess. For decades 99% has been achievable for many orgs. 92% phew. But “waste” is arguable. If folks have literally nothing to do when GitHub is down, I question that a bit. For example, design, administrative work (everyone has that), lunch. You know? Critical CI/CD can use Jenkins, but in that case folks might end up with 89% uptime!
- khaledh 7mo ago> If folks have literally nothing to do when GitHub is down, I question that a bit. It's not about a single person. I work at a company with over 10k employees, most of them rely on GitHub one way or another. It's not just about PRs and issues; there's a huge amount of automation, workflows, and integrations that depend on GitHub, round the clock. With this kind of uptime it has material impact on productivity of the company as a whole.