Alex KretzschmarBrutal.
When Microsoft acquired GitHub.
Andy McKay 🇨🇦@ironicbadger hmm, quite a few opinions on that chart 😀 tl;dr it’s complicated.
Most of GitHub services, until I left a couple of years ago were not on Azure.
aburka 🫣@andymckay @ironicbadger what's complicated about it? it used to be good and now it's bad
@aburka @ironicbadger ah I was replying to a different post about it being Azure or Azure management. I did Mastodon wrong, sorry.
I will say after the acquisition when GitHub became rapidly more complex as features were added, the definition of downtime requiring a status change became a lot more strict and focused (for some teams). A bit more loose and easy beforehand.
Harris Lapiroff@andymckay @aburka @ironicbadger The change here is so stark that I did wonder if this actually reflected a policy change on how downtime is tracked.
@harris @aburka @ironicbadger yes that’s one of the factors.
Status is an indicator controlled by the company. As GitHub sold more into businesses and became more crucial to them eg: Actions part of deployments - uptime became more critical and monitored more.
In Actions we built lots of sensitive metrics and quickly became more and more transparent about downtime, customers noticed it.
@harris @aburka @ironicbadger status was also one metric for all of GitHub, it was split into 6 or more around the time Actions was coming out. So more granularity too.
Surprised copilot isn’t on the status page yet.