Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

30% Positive

Analyzed from 691 words in the discussion.

Trending Topics

#github#sympathy#https#com#why#site#microsoft#service#incident#incidents

Discussion (22 Comments)Read Original on HackerNews

nightpool16 minutes ago
Getting rid of Actions and Copilot and other secondary services almost halves Github's incident rate: https://i.imgur.com/XPcMIFr.png

I'm a big fan of Github Actions and I think people are often a little too harsh on it, but it's clear that it's sad that it's come at such a high cost to the platform's stability

JeremyHerrman26 minutes ago
> "GitHub has had 1125 incidents since February 2016, implying a monthly incident rate of 24"

1125 incidents / 126 months ≈ 8.9 incidents per month, not 24

still terrible, but why such an obvious error in the first sentence...

kashnote39 minutes ago
I think we need to have a little more sympathy for GitHub. You could justify the jabs when we could all blame any outage on the migration to Azure, but then they shared numbers around the scale they're dealing with now that everyone is constantly building and pushing with AI.

I think it's commendable that they're not limiting access to the site or (intentionally) throttling newcomers. Yes, they need to get this figured out, but a little sympathy goes a long way. I personally wish them the best and hope their on-call people can go back to getting normal amounts of sleep soon.

gogobio23 minutes ago
Sympathy? It's a Microsoft company that is being ran with a consistency of a startup in early seed rounds. Their downtime is abhorrent and unacceptable as far as enterprise goes. Their engineers look like absolute amateurs allowing for such low class work it results in their customers experiencing industry leading downtime.
__MatrixMan__5 minutes ago
Sympathy negated by their 2026 Pwnie award: "Lamest Vendor"

https://this.weekinsecurity.com/microsoft-wins-lamest-vendor...

mronetwo13 minutes ago
We have a business relationship so no we shouldn’t have any sympathy. They sell a service and they’re failing to provide it.
amelius1 minute ago
Why? If we have sympathy for Apple then we can have sympathy for Microsoft ...
herpdyderp36 minutes ago
> I think it's commendable that they're not limiting access to the site or (intentionally) throttling newcomers.

I don't think this is commendable at all. I give GitHub a lot of money and I'm tired of it being wasted with downtime.

jjice31 minutes ago
It's a shame that the GitHub org that we use at my job that we pay a lot of money for gets affected the same way my personal nonsense does.

I don't know the architecture or any of that, but I feel like there could be (and it's not like they would've really known this until the last year or two with the massive spike) separate infrastructure for paid users/orgs vs free the same way they make the distinction with enterprise.

I get the massive load changes that they are under over the last two years, but why does a bunch of vibe coded slop take down the same resources that my company pays for every single month and has for years? I imagine properly splitting that out would be an absolute headache and not worthwhile for them vs stabilizing the rest of the service, but damn it sucks when I get blocked at work because GH is down.

dpz6 minutes ago
Maybe for a free account.

But we pay enterprise license and GitHub is a big dependency in our software flow.

If this continues to be a problem as an enterprise product they need to do something. Otherwise theyre are going to to start losing business

padjo29 minutes ago
I don't typically have sympathy for businesses that fail to deliver a service as advertised.

I can have sympathy for the humans caught in the crossfire but only managing one nine of availability on a commercial service is not acceptable.

JDups11 minutes ago
Constant building with AI is something that they (Microsoft) promote and are heavily invested in.
bushbabaabout 1 hour ago
could have been a page with a static 'Yes' and a significant portion of time it'd be accurate.
Gander5739about 1 hour ago
Relevant xkcd: https://xkcd.com/2236/
404mm39 minutes ago
If backend GitHub services are anything like GHES then I’m surprised it even managed to scale this much.
rvz28 minutes ago
They were cooked the moment they got acquired by Microsoft.

This is why I foresaw that centralizing everything to GitHub was just generally a bad idea 6 years ago. [0]

Now that there is no CEO of GitHub, there is no point to GitHub improving.

[0] https://news.ycombinator.com/item?id=22867803

kevmoabout 1 hour ago
An important thing to consider is how much of their uptime without incidents is not the normal working hours. Their incident-free uptime on 9-5 EST, Mon-Fri, is probably like 60%.
thombles12 minutes ago
As a daily GitHub user in Australia I still haven’t figured out why everyone’s complaining about uptime. :)
CoastalCoder30 minutes ago
> Their incident-free uptime on 9-5 EST, Mon-Fri, is probably like 60%.

And it may be even worse in EDT, which is currently in effect!

perfectstorm37 minutes ago
what's normal working hours? very US centric comment IMO. Europe, India, China, Latam etc. don't fall into your 9-5 EST normal working hour bucket.
padjo24 minutes ago
A service like GH will still show a daily usage pattern, often with a peak somewhere around 16:00 UTC when most of the US and Europe are at work.
arlattimoreabout 1 hour ago
I literally chuckled out loud when I saw the headline :D
johneaabout 2 hours ago
Oh, I thought it said "Github Outrage Tracker".

I was ready to click...

HPsquaredabout 1 hour ago
That one would be like iscaliforniaonfire.com
jakub_gabout 1 hour ago
Possibly inspired by:

https://red-squares.cian.lol/

gen22040 minutes ago
Hey! isgithubcooked.com is my site; I made this site in February '26, I think

The contribution graph as an outage calendar idea is a commonly recurring one :). I definitely saw it somewhere else as a static asset first before I made this site.

ChrisArchitectabout 1 hour ago
Advertisement