Hacker News Reader

Comment by Tainnor | Hacker News Reader

Maybe these are just a bunch of coincidences, but I have a feeling that GitHub is being poorly run recently. Apart from quite frequent uptime issues, it seems that Github Actions is pretty half-baked and they completely botched the migration of Dependabot (for example, take a look at this issue and especially, how it was handled: https://github.com/dependabot/dependabot-core/issues/3253)

View on HN

A shame they removed all their uptime graphs on the status page, since it's much harder to get a read on things now.

However, scrolling back through the status page's history for the last year shows that there between 6 and 12 incidents every month, and it often hovers at the high end of that range.

That has to be an utter misery for anyone who's on call.

> A shame they removed all their uptime graphs on the status page, since it's much harder to get a read on things now.

I've started using that (uptime/performance/latency graphs being removed from status pages) as a signal to for when companies feel embarrassed over their quality of service but don't have enough interest/resources/profits to fix it.

> interest/resources/profits

It doesn't seem like Microsoft should have any of these issues. At most "interest", but even that should be a pretty easy sell for a service as massive as github.

As Microsoft has SLAs, it probably isn't in their interest to make it easy to tell, to begin with. Management would probably just see liability.

Makes it much harder for enterprise customers to claim on their SLA as well.

...so that customers start tracking it themselves, so that everyone can waste time on discussing their differences in numbers and measurements, and who is right and who is wrong.

So who's ACTUALLY got the best reliability?

They have also largely abandoned their Terraform and Jira integrations.

Has been left up to the open source community to implement basic functionality.

Reply on news.ycombinator.com