Brutal.

[orionkidder@mas.to]

@ironicbadger Acquire and ruin. This is the corporate way.

[kaito02@mastodon.social]

@DaveMWilburn @ironicbadger get the sweet 55.5555555% availability

[drwho@masto.hackers.town]

@cap_ybarra @ironicbadger Yup.

[drwho@masto.hackers.town]

@ironicbadger Just like when they bought Hotmail back in the day.

[a_different_jlh@mastodon.social]

@ironicbadger Where was this chart published?

[aburka@hachyderm.io]

@andymckay @ironicbadger what's complicated about it? it used to be good and now it's bad

[ironicbadger@techhub.social]

@a_different_jlh https://damrnelson.github.io/github-historical-uptime/

Sorry I should have linked to the source

[andymckay@mastodon.social]

@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.

[aburka@hachyderm.io]

@andymckay @ironicbadger yeah I can believe there are many causes, mismanagement and forced development speed as much as technology changes

[llewelly@sauropods.win]

@ironicbadger behold the jagged teeth of the dog that eat all the dogfood!

[jourei@mas.to]

@ironicbadger Could anyone explain to me, how is this possible?
I would imagine they would keep things running on the original hardware etc. which I wouldn't expect to fluctuate like this.

[cinebox@masto.hackers.town]

@Tubsta @ironicbadger iirc they were like halfway through rolling it out when Microsoft bought them lmao

[mgedmin@floss.social]

@Jourei @ironicbadger Move fast and break things!

[thunfisch@chaos.social]

@ironicbadger @isotopp what’s the data source behind it? Official status page? Because that has been notoriously inaccurate long before microslop took over.

[a_different_jlh@mastodon.social]

@ironicbadger Cheers

[martinvermeer@fediscience.org]

@ironicbadger The inverse Midas touch

[odr_k4tana@infosec.exchange]

@kaito02 @DaveMWilburn @ironicbadger works 50% of the time, all the time.

[ingoschi@digitalcourage.social]

@ironicbadger searching for "github downtime 2016" I don't trust the old values

[simonwaight@mastodon.online]

@ironicbadger interested if you can map that to growth/shrinkage in users and/or volume or data being used.

[luceos@fosstodon.org]

@ironicbadger wait, they went from 100% uptime on their own servers,which were constantly on, to 99,5% as lowest uptime on a scalable infrastructure? That's 3,5 hours max spread over a month. And you're taking the piss on them for that? That's wild. Maybe focus on their link to Israel in the Gaza war or something.