Live data from Hacker News

Another GitHub outage in the same day

githubstatus.com

241–250 of 298 posts

Re: Another GitHub outage in the same day

#241
post #188

Earlier quoted context omitted.

Who is it?

Peter Thiel. Evil incarnate and the next president of the United States you've never heard of. Vance is his sock puppet, he was chosen because he is guaranteed not to have a single independent thought so when Trump croaks Thiel will be the president in all but name. It was also he who willed OpenAI to be in order to help destroying American democracy.

IDK what you're smoking, but he was born in Germany so can't be the next potus.

Re: Another GitHub outage in the same day

#242

Earlier quoted context omitted.

No its not. 121M repos added on github in 2025, and overall they have 630 million now. There is probably at best 2x increased in output (mostly trash output), but no where near 100x https://github.blog/news-insights/octoverse/octoverse-a-new-...

Published in Oct 2025... I think your estimate is off. Note the hockey stick growth in the graph they showed in Oct. Here we are in February. It's gotten way worse now with additional Claude's, Claw's, Ralph's, and such. It may not be 100x as was told to me but it's definitely putting the strain on the entire org.

> Oct 2025

Doubling down by insisting that the data is out of date, when the data is 3 months old and the latest available is unconvincing.

If you're telling me that in December it went from 2x to 100x then I don't believe you.

Re: Another GitHub outage in the same day

#243

Earlier quoted context omitted.

The trend of "non-functional software" is happening everywhere. See the recent articles about Copilot in Notepad, failing to start because you aren't signed in with your Microsoft Account. We are in a future that nobody wanted.

Laughs in my own Linux distro

Care to elaborate? How do you deal with the constant churn?

Re: Another GitHub outage in the same day

#244

I guess firing so many in the Github team was not that wise a decision. But immediate share holder value go vrooom. Long term impact? Leadership aint gonna stay to see that.

Lets be real, these outages were happening for years, nobody cares because nobody is accountable when you're too big to fail.

Re: Another GitHub outage in the same day

#245
post #71

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…

Github used to publish some pretty interesting postmortems. Maybe they still do. IIRC that they were struggling with scaling their SQL db and were starting to hit the limits. It's a tough position to be in because you have to either to a massive migration to a data layer with much different semantics, or you have to keep desperately squeezing performance and skirting on the edge of outages with a DB that wasn't reall…

I’d be surprised by this: GitHub pretty famously used Vitess, and I’d be surprised if each shard were too big for modern hardware. Based on previous reporting [0], they’re running out of space in the main data center and new management is determined to move to Azure in a hurry. I’d bet that these outages are a combination of a worsening capacity crunch in the old data center and…well, Azure.

[0]: https://thenewstack.io/github-will-prioritize-migrating-to-a...

Re: Another GitHub outage in the same day

#246

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…

I second this. GitHub used to be a fantastic product. Now it barely even works. Even basic functionality like the timeline updating when I push commits is unreliable. The other day I opened a PR diff (not even a particularly large one) and it took fully 15 seconds after the page visually finished loading -- on a $2,000 dev machine -- before any UI elements became clickable. This happened repeatedly. It is fairly stun…

I mean.. it’s a Microsoft product now. That’s basically a guarantee it will suck, and continue to get worse and worse until it’s an unusable mess of garbage like everything else they make. I haven’t seen any good user-facing windows products in at least 10 years and somehow the bar drops lower by the year.

Re: Another GitHub outage in the same day

#247

Earlier quoted context omitted.

I for one am shocked--SHOCKED, I say!--to learn that anything bad could happen as a result of a) putting everything in "the cloud" and b) handing control over the entire world's source code to the likes of Microsoft. Who could have POSSIBLY foreseen any kind of dire consequences?

Nobody. Nobody at all could have seen it. Microsoft is cool now, haven't you seen VSCode? They do Open Source, they run Linux, they've joined the fold, the tiger shed its stripes.

Ironically they are enshitifying vscode too. Even products them make themselves can’t survive long.

Re: Another GitHub outage in the same day

#248
post #73

Earlier quoted context omitted.

Not quite everywhere. There's a common denominator for all of those: Microsoft. Their business is buying good products and turning them into shit, while wringing every cent they can out of the business. Always has been. They have a grace period of about 2-4 years after acquisition where interference is minimal. Then it ramps up. How long a product can survive once the interference begins largely depends on how good s…

I for one am shocked--SHOCKED, I say!--to learn that anything bad could happen as a result of a) putting everything in "the cloud" and b) handing control over the entire world's source code to the likes of Microsoft. Who could have POSSIBLY foreseen any kind of dire consequences?

You're obviously being sarcastic, but for the longest time the dominant position of a huge chunk of HN (and the tech world in general) has been that the cloud is the answer to any problem, and that anything deviating from it is either impossible, too expensive or too stupid.

After a generation of indoctrinated people, Microsoft (or any FAANG really) can't even afford to do anything differently.

Re: Another GitHub outage in the same day

#249

Earlier quoted context omitted.

Literally everyone who has used Github to look at a pull request in say the last year has experienced the ridiculous performance issues. It's a constant laughing point on HN at this point. There is no way you don't know this. Inviting to take this to a private channel, along with the rest of your comment really, is simply standard corporate PR.

I look at pull requests daily, I haven't encountered the problems you speak of, not sure what they are.

I have been using GitHub since 2011 and it's undeniable that the performance of the website have been getting worse. The new features that are constantly being added are certainly a factor, but I think the switch to client-side rendering that obviously shifted the load from their server to our browsers and also tend to produce ridiculously large and inefficient DOMs[1] is the main cause.

If you want a practical example, here you go. I'm a Nixpkgs commiter and every time I make a pull request that backports some change to the stable branch, GitHub unprompted starts comparing my PR against master. If I'm not fast enough to switch the target branch within a couple of seconds it literally freezes the browser tab and I may have to force quit it. Yes, the diff is large, but this is not acceptable, and more importantly, it didn't happen a few years ago.

[1]: https://github.com/orgs/community/discussions/111001

Re: Another GitHub outage in the same day

#250
post #222
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/

this one does not seem to be updated? last outage is Feb 6...

It seems to be correct now
Post reply on HN