Live data from Hacker News

Another GitHub outage in the same day

githubstatus.com

181–190 of 298 posts

Re: Another GitHub outage in the same day

#181
post #129

I moved everything on github to a self hosted foregjo instanse some days ago. I really did not do anything. Created some tokens so that CC could access github and forgejo and my dns API. Self hosting is so much simpler and easier with AI. Expect more people to self host small to medium stuff.

Ironic that that same AI you're mentioning is probably a large part of why this class of outages are increasing. Id highly recommend folks understand their infrastructure enough to setup/run it without AI before they put anything critical on it.

Sure. I can agree with that. At the same time, the reason people aren't doing it is not solely a skill issue. It's also a matter of time, energy, and what you want to prioritise.

I believe I have good enough control over it to fix issues that may arise. But then again, CC will probably do it faster. I will most likely not need to fix my own issues, but if needed, I think I will be able to.

"Critical" plays an important role in what you're saying. The true core of any business is something you should have good control over. You should also accept that less important parts are OK for AI to handle.

I think the non-critical part is a larger part than most people think.

We are lagging behind in understanding what AI can handle for us.

I'm an optimistic grey beard, even if the writing makes me sound like a naive youth :)

Re: Another GitHub outage in the same day

#182

Earlier quoted context omitted.

How much has the volume increased, from what you know?

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.

Goodness if that's true... And I actually felt bad when they banned me from the free tier of LFS.

Re: Another GitHub outage in the same day

#183

Earlier quoted context omitted.

> We are in a future that nobody wanted. some people wanted this future and put in untold amount of money to make it happen. Hint: one of them is a rabid Tolkien fan.

Rent seekers paradise (ft copilot)

It’s just feudal with Capital.

Re: Another GitHub outage in the same day

#184

Earlier quoted context omitted.

How much has the volume increased, from what you know?

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-...

Re: Another GitHub outage in the same day

#185

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.

One hundred ? Did I read that right?

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-...

Re: Another GitHub outage in the same day

#186

GitLab is the solution, if you aren't on it already. I worked for one of Australia largest airline company, monthly meeting with Github team resumed in one word: AI There is zero focus into the actual platform as we knew it, it is all AI, Copilot, more AI and more Copilot. If you are expecting things to get better, I have bad news for you. Copilot is not being adopted by companies as they hoped, they are using Claude…

To be honest all the GitLab dev focus is also AI.

* Originally it was Dev (issues)

* Then it was DevOps (runners)

* Then it was DevSecOps (SAST)

* Now it's AI DevSecOps (reviews, etc)

The problem is that each feature has been slightly more half-baked than the last one. The SecOps stuff is full of gotchas which don't exist. Troubleshooting a pipeline behaving correctly is extremely painful.

The other problem is that if you want a feature you have to upgrade the seat license for everyone :(

Re: Another GitHub outage in the same day

#187

[dead]

> The irony of githubstatus.com itself being hosted on a third-party (Atlassian Statuspage) is not lost on anyone who works in incident management. Your status page being up while your product is down is table stakes, not a feature

That's WHY it's hosted externally, so that if GitHub goes down the status page doesn't.

Re: Another GitHub outage in the same day

#188

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.

> We are in a future that nobody wanted. some people wanted this future and put in untold amount of money to make it happen. Hint: one of them is a rabid Tolkien fan.

Who is it?

Re: Another GitHub outage in the same day

#189
post #121

Earlier quoted context omitted.

“ I enjoy GH copilot as much as the next person” So not at all?

Really? I’d be interested to hear more. Disclaimer: I work in Microsoft (albeit in a quite disconnected part of it, nothing to do with GitHub or Copilot).

In testing for my workflows copilot significantly underperforms the SOTA agents, even when using the exact same models. It's not particularly close either.

This has lead to 2 classes of devs at my company a) AI hesitant, who for many copilot is their only interaction, having their worst fears confirmed about how bad AI is. b) AI enthusiasts who are irritated by dealing with management that don't know the difference pushing back on their asks for access to SOTA agents.

If I were the frontier labs, and wasn't billions of dollars beholden to Microsoft, I'd cut Copilot off. It poisons the well for adoption of their other systems. I don't deal with the other copilots besides the coding agent variants but I hear similar things about the business application variants.

Microsofts AI reputation is in the toilet right now, I'm not sure if its understood how bad it really is within the org.

Re: Another GitHub outage in the same day

#190

Earlier quoted context omitted.

Hey from the GitHub team. Outages like this are incredibly painful and we'll share a post-mortem once our investigation is complete. It stings to have this happen as we're putting a lot of effort specifically into the core product, growing teams like Actions and increasing performance-focused initiatives on key areas like pull requests where we're already making solid progress[1]. Would love if you would reach out to…

For what it's worth, I doubt that people think it's the engineering teams that are the problem; it feels as though leadership just doesn't give a crap about it, because, after all, if you have a captive audience you can do whatever you want. (See also: Windows, Internet Explorer, ActiveX, etc. for how that turned out) It's great that you're working on improving the product, but the (maybe cynical) view that I've hear…

> 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.

Post reply on HN