Hacker News Reader

Comment by perks_12 | Hacker News Reader

The LLM code influx is not the problem. Microsoft mismanagement is: https://damrnelson.github.io/github-historical-uptime/

View on HN

I was there before 2018, their reliability was never that good.

I still remember that they launched GitHub Actions in 2018 and back then I was thinking: They can't even make the website reliable, surely this will only cause them more problems.

This site's trustworthiness when it goes for pre-aquisition data was disputed here already:

https://news.ycombinator.com/item?id=48086786

Thanks for sharing this, had no idea. This information changes my perspective a lot.

GitHub's historical uptime page is fake, they backfilled it with 100% uptime going back to 1996: https://www.githubstatus.com/uptime?page=200

seems to be correct. there's no record of the outage on 8/13 :/

HN is likely a better source than GH status...

Wow.

Why would they do that?

Strange. The back button in the UI is disabled once you get back to September 2016. https://www.githubstatus.com/uptime/8l4ygp009s5s?page=40

The earliest recorded downtime for Git Ops I could find is in December 2018. https://www.githubstatus.com/uptime/8l4ygp009s5s?page=32

Fax. Those falling for the load/capacity excuse are gullible.

Maybe not the only problem, but that graph ends in February and it gets visibly worse starting in May: https://isgithubcooked.com/

Pretty sure this is caused by trying to move to Azure (and I'd bet like $1000 partially due to trying to move DBs to network backed disk instances)

Reply on news.ycombinator.com