There are 44640 minutes in May. If it was out for 0.5% of them, it was down for 223.2 minutes. The data point is a little bit less, but not much. It is closer to having been down for 3.5 hours.
I initially misread the graph. I thought each mark on the horizontal axis was one month. And there were three data points per month. That was wrong. Each mark is the first month of the quarter and each point is one month.
Same image with readable axis labels.
Edit: Just to put it in perspective, that big spike is about 4 hours and 2 minutes of downtime for the month of May 2023. Sauce
There are 44640 minutes in May. If it was out for 0.5% of them, it was down for 223.2 minutes. The data point is a little bit less, but not much. It is closer to having been down for 3.5 hours.
I initially misread the graph. I thought each mark on the horizontal axis was one month. And there were three data points per month. That was wrong. Each mark is the first month of the quarter and each point is one month.
Real triple 99.9% is pretty hard to achieve on a massive service.
That’s not the point of the post tho?
It was hitting 99.9% before acquisition. Unless you want to say that github only became massive after MS acquisition
I don’t know anything concrete, but MS may report downtime differently, and have more strict requirements for reporting downtime.
I’ve seen it happen at another ‘start up’ that got acquired and suddenly started reporting way more downtime events than prior to acquisition.
That actually may be true, but honestly my personal/anecdotal evidence also shows github being down more since atleast a couple of years.
Thanks!