GitHub incident 2022-03-23

Re:GitHub incident 2022-03-23 by mbesto on Wednesday March 23, 2022 @01:30PM (#30781019)

The number of incidents isn't so much of a problem as the amount of downtime is. That would be more interesting to see.

[ Parent | on HN ]

Re:GitHub incident 2022-03-23 by belter on Wednesday March 23, 2022 @02:03PM (#30781390)

GitHub Availability Report [1]

Service Downtime Core Services Only - Cumulative per Month

( Some months with more than one outage)

Jan 2021: 3 hours 53 min

Feb 2021: 1 hour 42 min

Mar 2021: 4 hours 10 min

Apr 2021: 2 hours 20 min

May 2021: 10 hours 34 min

Jun 2021: 0 min

Jul 2021: 0 min

Aug 2021: 4 hours 23 min

Sep 2021: 0 min

Oct 2021: 1 hour 36 min

Nov 2021: 2 hours 50 min

Dec 2021: 0 min

Jan 2022: 26 min

Feb 2022: 13 min

[1] https://github.blog/tag/github-availability-report/

[ Parent | on HN ]

Re:GitHub incident 2022-03-23 by mbesto on Wednesday March 23, 2022 @02:32PM (#30781696)

So, if my math is right (for 2021 only): 1888 min / 525,600 min = 99.64% uptime.

If it was more like 99.80+ I think I would be like "meh", but honestly for the price you pay that's not terrible. Still, for a company at the Microsoft level, it should be 99.80 at least.

[ Parent | on HN ]

Re:GitHub incident 2022-03-23 by JonChesterfield on Wednesday March 23, 2022 @09:58PM (#30785689)

This is the same Microsoft that reboots laptops in the middle of teams calls to do hour long update cycles. >99% is implausibly good.

[ Parent | on HN ]