47 comments

[ 4.9 ms ] story [ 41.9 ms ] thread
GitHub Incident again/
Are they running paid marketing campaigns for Gitlab ?
I'm so done with GitHub.
https://isgithubcooked.com

Normally I defend GH in the comments of these incidents but it’s been an impressively bad month by their standards, even when you filter for critical components filter out sev-2’s and 3’s.

Wow, it seems that 100% of sev-3 ("critical") incidents in the last year (=365 days) have occurred between April 22, 2026 and now.

Is it possible that there has been a change in the way the data are collected/recorded that even partially accounts for this sudden onset?

Maybe we should start posting av story when GitHub has been fine for some time instead of posting every incident
They may have gotten down to only 2 nines on most of their services, but at least the LLM is still running at full power! must increase value for shareholders
git is supposed to be decentralized.

maybe it's time to revert back to the central idea of git & not centralize around a particular provider.

for issues - mailing list will do. you can always slap a beautiful ui if you want to or a tui (as is the fad) these days.

actions can also be decentralized via an API spec & webhooks.

Before clicking, I assumed this was going to be a write-up of the one from a few days ago instead of an entirely new incident.
is it me or ever since AI coding became the norm, there have been way more outages with otherwise reliable services?

I get downtime on Supabase every few weeks. Even Cloudflare. And now Github

Tried to do a git push - it succeeded after 3 mins. Then I wanted to open a PR and it failed with a 500 error.

Facepalmed and decided that this is it for today.

Yesterday my CI runs wouldn't even be created because Actions was eating shit, and today my CI runs get created but fail because the API is eating shit. Fun.
This is getting ridiculous. One particularly concerning thing I’m seeing is that pull requests on both the web UI and API aren’t reflecting all commits or branch changes consistently. It would be very easy to merge something without realizing you’re not actually reviewing the full diff.
For years we had a GitHub status thing in our Slack but I had to remove it about a year ago because the noise got too much, it would be unbearable in 2026.
GitHub is not agent scale.

Multiple companies are trying to create new versioning primitives/architectures which can handle machine-level code generation - 1 commit per second per repo.

It's like switching from horse buggies to automobiles, the whole worlds needs re-architecturing to handle the new load.

The age of boutique hand-coding is being replaced by the age of industrial software factories.

It seems before AI eats software, its going to first eat GH and Microsoft.
[flagged]
We've banned this account for repeatedly posting abusive comments. We've asked you before to observe the guidelines, and the recent trend is getting much worse. When this happens we eventually have to assume you want to be banned. If you don't want to be banned, you can email us (hn@ycombinator.com) and commit to using HN as intended.
as a github user, we are paying for the slow git operations through our github action minutes, if someone from GH is here, will you be compensating for it?
Maybe GitHub needs to freeze free repository creation until they get this under control because this is ridiculous.
I thought it was the yesterday's thread but no, here we go again
If you go to www.githubstatus.com, the downtime is not showing in the chart. I was annoyed enough yesterday when I visited this page to figure out why my Actions had failed and was greeted with big green ticks and only a tiny red rectangle halfway down the page to indicate the problem.

This time they've just scrubbed the evidence outright?

I'd appreciate if they'd not mark the incident as resolved when there's still fallout - ie: my commits didn't display on the branch, my actions didn't run

It's the same issue as the other day - display message at the top admitting that cache needs to be refreshed (or whatever the wording was)