Live data from Hacker News

Another GitHub outage in the same day

githubstatus.com

211–220 of 298 posts

Re: Another GitHub outage in the same day

#211
post #4

Earlier quoted context omitted.

Self hosted GitLab is absolutely worth it.

I was just looking into this today but it seems pricey. $29/user/month for basic features like codeowners and defining pr approval requirements. Going with Forgejo.

Forgejo isn't comparable.

Re: Another GitHub outage in the same day

#212

Earlier quoted context omitted.

Do they have their own model? I thought Copilot was a frontend for Clause et. al..

To the best of my knowledge, Copilot is a Microsof in-house thing and it sucks on everything. Claude is far superior and Microsoft is allegedly using Claude internally over its own AI solution.

Github Copilot is just a front-end. You pay for the frontend and some premium requests every month.

The base models like GPT 4o, 4.1 don’t have a usage cap. Models like Claude Sonet, Opus, etc have a monthly limit and you can pay more to use these through Github Copilot.

Re: Another GitHub outage in the same day

#213

Earlier quoted context omitted.

As an aside, God, Azure DevOps, what a total pile of crap that product is My "favourite" restriction that an Azure DevOps PR description is limited to a pathetic 4000 characters.

Amazon's deprecated CodeCommit is limited to 150 chars like it's an old SMS or Tweet.

Surprisingly they un-deprecated CodeCommit recently.

https://aws.amazon.com/blogs/devops/aws-codecommit-returns-t...

Re: Another GitHub outage in the same day

#214
post #66

Can someone in GitHub senior leadership please start paying attention and reprioritise towards actually delivering a product that's at least relatively reliable? I moved my company over to GH enterprise last year (from AzDO) and I'm considering moving us away to another vendor altogether as a result of the constant partial outages. Things that used to "just work" now are slow in the UI, and GH actions fail to schedul…

You might as well self-host at this point as that is far more reliable than depending on GitHub. Additionally, there is no CEO of GitHub this time that is going to save us here. So as I said many years ago [0] in the long term, a better way is to self host or use alternatives such as Codeberg or GitLab which at least you can self host your own. [0] https://news.ycombinator.com/item?id=22867803

You can self host GitHub as well

Re: Another GitHub outage in the same day

#216
post #207

Earlier quoted context omitted.

Heh, I was working at 2 of those gaming companies when they were acquired by m$. I almost fear taking another job in the gaming industry, there seems to be some kind of bastardised version of Murphy's law that any gaming company that hires me will be acquired by ms 6 months later. I mean, that's obviously not the case, but it's weird that it happened twice!

Very weird it happened twice! But that's a kind of a cool factoid to tell people haha. Even with devs and publishers that don't die or are killed, they still lay hundreds off when a game is done. Then the studio limps along in pre-production mode on their next game for 4-5 years it seems like... Maybe the only job stability in the industry is with indies, and... Nintendo?

I'd add the hugely successful studios to that list. Even after ms acquisition, to the best of my knowledge neither of the 2 studios I worked at had any layoffs.

But they boast the most sold video game in the history of videogames (Tetris a close-ish second), and most downloaded free mobile game, respectively. Each have player bases larger than the population of the country they're from!

Here's to hoping ms is hesitant to gut either!

Re: Another GitHub outage in the same day

#217
post #163

This (multiple major outages a day) has unfortunately been happening for quite a while now -- on the 2nd of February, 2026 for instance. The GitHub Status Page does not visualize these very well but you can see them parsed out and aggregated here: https://mrshu.github.io/github-statuses/

https://updog.ai/status/github this is also scraped from datadog usage of github.

[deleted]

Re: Another GitHub outage in the same day

#218
post #190

Earlier quoted context omitted.

> people think it's the engineering teams that are the problem; It could be, some people are just terrible at their job. Lots of teams have low quality standards for their work. Maybe that still comes down to leaders but for different reasons. You can ship useless features without downtime.

Permitting terrible engineers to continue to work for you is a management problem.

Sort of I think. There's a culture aspect to it too. Everything is blameless, there's no reason to not mess up.

Re: Another GitHub outage in the same day

#219

Earlier quoted context omitted.

Even just a year or two ago its web interface was way snappier. Now an issue with a non-trivial number of comments, or a PR with a diff of even just a few hundred or thousand lines of changes causes my browser to lock up.

Which website lets you load PRs with 1000 lines and it’s fast? Honest question, it’s not gitlab.

It's ~80 KiB. Do you think 80 KiB should be slow?

GH just a few days ago told me that it couldn't fetch the files changed because there were too many files changed. There were 4.

Re: Another GitHub outage in the same day

#220

Earlier quoted context omitted.

Over 100x is what I’m hearing. Though that could just be panic and they don’t know the real number because they can’t handle the traffic.

Lmao not even close. Github themselves have released the numbers and it was 121M new repos with 2025 ending up with 630M https://github.blog/news-insights/octoverse/octoverse-a-new-...

So X might have been %
Post reply on HN