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.
show comments
kpres62
Maybe it's time we start HitGub
joshuahedlund
Given that the outages are caused by record traffic, so far they are only cooked in the Yogi Berra sense of “Nobody goes there anymore, it’s too crowded”
show comments
Fuzzwah
Near the end of the 8.5 years that I worked at GitHub as an enterprise support engineer, I asked in an all hands if a "GitHub Classic" product had been considered. Much like World of Warcraft Classic, I imagined it would be a rewrite focused on matching the simpler feature set of the past.
I was basically given the same response that blizzard gave that question; "you think you want that but you don't".
JeremyHerrman
> "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...
show comments
erlkonig
Since when does Microsoft owning a thing actually improve that thing?
_heimdall
I feel for the team having to deal with these problems at github today. Its also beyond me how those in charge for years wouldn't have seen this coming.
Github was bought by Microsoft, whether they wanted to acknowledge that internally or not. Microsoft went deep on LLMs, and specifically on LLMs for coding use cases. They must have recognized that LLM generated code and PRs would effectively DDoS GitHub.
I can only assume they simply didn't care, likely driven by greed.
bushbaba
could have been a page with a static 'Yes' and a significant portion of time it'd be accurate.
show comments
crossroadsguy
But after exploring some options for small but private and personal repos (not foss; not yet at least) I realised I am better off with a free Github private repo. There simply isn't a feasible free alternative for such a use-case without hitting, often a 50MB to say few 100s MB, the limit ASAP. There's gitlab.com, bitbucket (? haven't opened it in ages) but those are not better in any way for use cases like mine.
Are there any?
silver92bullet
I hear the comments that state we should have sympathy for github. For the individual ops/sre I can have that sympathy because it must a heck of a time internally to manage things. I can't however have sympathy for company itself. They have not set themselves or the community for success. I think it is the responsibility of the company to anticipate the issues or at least react in a way that would build trust. The fact is there is a systemic issue in the company that causes the repeated unreliableness and they have not rooted it out.
404mm
If backend GitHub services are anything like GHES then I’m surprised it even managed to scale this much.
xyzzy_plugh
Is GitHub Cooked? Decidedly yes.
Migrating to something else has been raised as a concern during every engagement with clients and prospective clients in the past year.
"Do you use GitHub?"
"Yes though we'd like to move to something else, we just don't know what yet."
As soon as the next big thing shows up, they're done. And they know it.
show comments
imnes
It's not making headlines, but Google and Apple seem to be getting hammered by AI as well. Getting app updates approved to release on prod on Play Store / App store used to take days, now it's taking weeks.
nightpool
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
show comments
djieidj283
It’s ironic that the SCM that 2026 software engineers landed on, is one with a complicated distributed usage model and is slow/down because of a centralised service
devy
Didn't GitHub CTO Vladimir Fedorov just posted this a couple days ago?
There is alternatives for github, but all of them would be offline 100% is they got even 10% of traffic Github gets after AI.
Any dev can just have their own git mirror and work there, but replacing github is not really feasable, not one of the other services come even close.
If github is down for say 2h i dont really care. I can live with that. IF i did care i would just host my own.
microcannot
What most people don't understand is that Microsoft can no longer engineer a technology product, they simply can't develop anything anymore. They can throw slop around, but they lack the corporate culture to actually build an innovative technology product. They can purchase other companies that have built products, but as soon as they do those products stop innovating and begin dying.
microcantanymor
What most people don't understand is that Microsoft can no longer engineer a technology product, they simply can't develop anything anymore. They can throw slop around, but they lack the corporate culture to actually build an innovative technology product. They can purchase other companies that have built products, but as soon as they do those products stop innovating and begin dying.
GrumpySciGuy
Yes, but I did not need to look at the tracker to know that.....
arlattimore
I literally chuckled out loud when I saw the headline :D
kevmo
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%.
show comments
johnea
Oh, I thought it said "Github Outrage Tracker".
I was ready to click...
show comments
rvz
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.
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.
Maybe it's time we start HitGub
Given that the outages are caused by record traffic, so far they are only cooked in the Yogi Berra sense of “Nobody goes there anymore, it’s too crowded”
Near the end of the 8.5 years that I worked at GitHub as an enterprise support engineer, I asked in an all hands if a "GitHub Classic" product had been considered. Much like World of Warcraft Classic, I imagined it would be a rewrite focused on matching the simpler feature set of the past.
I was basically given the same response that blizzard gave that question; "you think you want that but you don't".
> "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...
Since when does Microsoft owning a thing actually improve that thing?
I feel for the team having to deal with these problems at github today. Its also beyond me how those in charge for years wouldn't have seen this coming.
Github was bought by Microsoft, whether they wanted to acknowledge that internally or not. Microsoft went deep on LLMs, and specifically on LLMs for coding use cases. They must have recognized that LLM generated code and PRs would effectively DDoS GitHub.
I can only assume they simply didn't care, likely driven by greed.
could have been a page with a static 'Yes' and a significant portion of time it'd be accurate.
But after exploring some options for small but private and personal repos (not foss; not yet at least) I realised I am better off with a free Github private repo. There simply isn't a feasible free alternative for such a use-case without hitting, often a 50MB to say few 100s MB, the limit ASAP. There's gitlab.com, bitbucket (? haven't opened it in ages) but those are not better in any way for use cases like mine.
Are there any?
I hear the comments that state we should have sympathy for github. For the individual ops/sre I can have that sympathy because it must a heck of a time internally to manage things. I can't however have sympathy for company itself. They have not set themselves or the community for success. I think it is the responsibility of the company to anticipate the issues or at least react in a way that would build trust. The fact is there is a systemic issue in the company that causes the repeated unreliableness and they have not rooted it out.
If backend GitHub services are anything like GHES then I’m surprised it even managed to scale this much.
Is GitHub Cooked? Decidedly yes.
Migrating to something else has been raised as a concern during every engagement with clients and prospective clients in the past year.
"Do you use GitHub?"
"Yes though we'd like to move to something else, we just don't know what yet."
As soon as the next big thing shows up, they're done. And they know it.
It's not making headlines, but Google and Apple seem to be getting hammered by AI as well. Getting app updates approved to release on prod on Play Store / App store used to take days, now it's taking weeks.
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
It’s ironic that the SCM that 2026 software engineers landed on, is one with a complicated distributed usage model and is slow/down because of a centralised service
Didn't GitHub CTO Vladimir Fedorov just posted this a couple days ago?
https://github.blog/news-insights/company-news/the-august-17...
I’ve reached the point where I just feel a mourning kind of sadness for GitHub
using github in 2026 is a self own. its that simple at this point
https://mrshu.github.io/github-statuses/
There is alternatives for github, but all of them would be offline 100% is they got even 10% of traffic Github gets after AI.
Any dev can just have their own git mirror and work there, but replacing github is not really feasable, not one of the other services come even close.
If github is down for say 2h i dont really care. I can live with that. IF i did care i would just host my own.
What most people don't understand is that Microsoft can no longer engineer a technology product, they simply can't develop anything anymore. They can throw slop around, but they lack the corporate culture to actually build an innovative technology product. They can purchase other companies that have built products, but as soon as they do those products stop innovating and begin dying.
What most people don't understand is that Microsoft can no longer engineer a technology product, they simply can't develop anything anymore. They can throw slop around, but they lack the corporate culture to actually build an innovative technology product. They can purchase other companies that have built products, but as soon as they do those products stop innovating and begin dying.
Yes, but I did not need to look at the tracker to know that.....
I literally chuckled out loud when I saw the headline :D
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%.
Oh, I thought it said "Github Outrage Tracker".
I was ready to click...
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
Now add an rss/atom feed link and you have my support
Possibly inspired by:
https://red-squares.cian.lol/