Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Incident with Issues and Webhooks – Resolved

githubstatus.com

Post reply on HN
Print view View original

181–190 of 275 posts

Re: Incident with Issues and Webhooks – Resolved

#181

Post by tardedmeme »

01HNNWZ0MV43FF wrote: post #165
tardedmeme wrote: post #129

Earlier quoted context omitted.

I don't know. Everyone seems to be using GitHub only because everyone else is using GitHub. Apparently that's important somehow. Me, I use "git init"

https://en.wikipedia.org/wiki/Network_effect It's a lot easier to get bug reports and fixes when everyone is on the same auth system. That's why there is also a call for federated forges

Why is it easier to submit a bug report if my bug reporting system is run by the same company as your code repository? Why are those things even slightly related?

Re: Incident with Issues and Webhooks – Resolved

#182

Post by fastball »

graypegg wrote: post #36
AlexB138 wrote: post #15

Github has published some incredible usage rate increase numbers, which they ascribe to the rise of agentic coding. At some point, they are going to have to change rate limits, cut free-tier usage, or find some other path to reducing load. It's clear that their infrastructure can't keep up with this significant increase, and it's unlikely that they're going to just absorb the increased costs themselves. Very curious…

IMO, they're reaching the point of no return. I don't think they can horizontally-scale their way out of the hole they dug themselves unless they separate their free and paid infra maybe... which doesn't seem likely considering how their other infra changes are going. In the same way you need to be 10x better for someone to consider switching to your product, if you get 10x worse your competitors get a free 10x by ju…

How can they not? Surely at GitHub scale there isn't a single component where they were relying on vertical scaling?

Re: Incident with Issues and Webhooks – Resolved

#183

Post by brian-armstrong »

mohsen1 wrote: post #82
AlexB138 wrote: post #15

Github has published some incredible usage rate increase numbers, which they ascribe to the rise of agentic coding. At some point, they are going to have to change rate limits, cut free-tier usage, or find some other path to reducing load. It's clear that their infrastructure can't keep up with this significant increase, and it's unlikely that they're going to just absorb the increased costs themselves. Very curious…

The same company operates the Xbox network. More daily active users and more events per second

Not comparable at all. Xbox would be mostly transient traffic. It's probably not much more than packet forwarding for a lot of traffic.

Github is a giant complicated stateful mess with a lot of reads and writes. It also has a lot of features at this point. Hard to scale and hard to optimize.

Re: Incident with Issues and Webhooks – Resolved

#184

Post by Kwpolska »

jfrbfbreudh wrote: post #151

Reduce the free tier. I’ve made 4000 commits in the last 2.5 months. That’s just to main. And I push up tons of artifacts daily for regression testing. For $0.

GitHub should add a slop tax. Co-authored by Claude? Pay up. Em-dashes in comments? Pay up. A lot of code written in a short window of time? Pay up.

Re: Incident with Issues and Webhooks – Resolved

#185

Post by bspammer »

veber-alex wrote: post #167
gejose wrote: post #30

Github has 84.92% uptime in the last 90 days according to https://mrshu.github.io/github-statuses I don't know how this is even remotely close to acceptable.

ffs can we stop talking about that number and site already. It treats any service being down as the entire platform being down which is nonsense. It's just lying with statistics.

The individual numbers for git operations, pull requests, and actions are all still single-nine.

Re: Incident with Issues and Webhooks – Resolved

#186

Post by foolswisdom »

munk-a wrote: post #166
eddyg wrote: post #77

Earlier quoted context omitted.

From the GitHub COO on April 3rd: Platform activity is surging. There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.) GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week in 2025, and now 2.1B minutes so far this week. So we're pushing incredibly hard on more CPUs, scaling services, and strengthening G…

After the Microsoft acquisition GH marketing and pricing put an immense amount of effort[1] into trying to kill secondary platforms that integrated into github and move more corporate accounts fully on-platform. We recently dropped travis for github actions and dropped reviewable for github PRs (which are terrible ). There's a portion of this that is agentic driven and there's a portion of this that's just github mak…

In other words, the set of github core services has expanded because you don't use third party tooling for some of those services anymore.

Re: Incident with Issues and Webhooks – Resolved

#188

Post by munk-a »

foolswisdom wrote: post #186
munk-a wrote: post #166

Earlier quoted context omitted.

After the Microsoft acquisition GH marketing and pricing put an immense amount of effort[1] into trying to kill secondary platforms that integrated into github and move more corporate accounts fully on-platform. We recently dropped travis for github actions and dropped reviewable for github PRs (which are terrible ). There's a portion of this that is agentic driven and there's a portion of this that's just github mak…

In other words, the set of github core services has expanded because you don't use third party tooling for some of those services anymore.

For us, yes - and likely for a lot of other users. I'm not certain who else has dealt with the headache of being migrated off their legacy pricing plan but it ends up pushing those internal offerings a lot harder than the old approach did so if they're seeing successful conversions it's likely they're seeing significantly more load from mature codebases with expensive CI/CD pipelines.

Re: Incident with Issues and Webhooks – Resolved

#189

Post by munk-a »

AlexB138 wrote: post #15

Github has published some incredible usage rate increase numbers, which they ascribe to the rise of agentic coding. At some point, they are going to have to change rate limits, cut free-tier usage, or find some other path to reducing load. It's clear that their infrastructure can't keep up with this significant increase, and it's unlikely that they're going to just absorb the increased costs themselves. Very curious…

Have they published incredible usage rate numbers somewhere? I saw their recent blog post about the outages[1] and it has a graph without axis labels and without any context around usage before 2019 to indicate just how much this agentic acceleration has actually increased usage growth.

1. https://github.blog/news-insights/company-news/an-update-on-...

Re: Incident with Issues and Webhooks – Resolved

#190

Post by simoncion »

baderb wrote: post #14

I keep wondering what causing such a bad service from GH lately, is it the overuse of AI generated code? Are they trying to cut costs with the infrastructure?

Part of it is additional load. Part of it is their move of more and more of Github infrastructure to Azure.

I've done a lot of "plain compute" work [0] with the Big Three Cloud Compute vendors. Azure is by far the worst. Mysterious resource creation failures, mysterious resource deletion failures, mysterious "incompatible schema" failures when talking to Azure provisioning and status infrastructure, mysterious and inexplicable performance problems, etc, etc, etc. Unless I was being paid a lot of money to use Azure, I'd take Google's legendarily nonexistent support over Azure's unreliability any day.

[0] That is, "create a VM with persistent disks, Internet access, and maybe a load balancer in front and ignore all of the other features provided by the vendor"

Post reply on HN