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.
ckorhonentoday at 12:35 PM
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.
xnorswaptoday at 12:30 PM
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.
gredtoday at 4:34 PM
New PR: revert GitHub software and infrastructure to version of June 1st, 2018.
New PR: disable new user signups for 6 months
HR initiative: all future KPIs automatically require three-nines availability; all bonuses are forfeited, regardless of accomplishments, if annual availability falls below target
HR initiative: fire CEO and CTO
Robdel12today at 6:05 PM
I know it’s super fun to shit on GitHub and everyone’s favorite thing to say is “build a competitor!”
They’re trying to scale from 1 billion commits last year to over 14 billion this year. I have zero desire to try and manage that scaling. Basically being DDOS’d by agents all day now.
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
robin_realatoday at 1:35 PM
Good that the Billing functionality is still at 3 nines at least.
eithedtoday at 1:29 PM
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)
Systemic33today at 1:31 PM
Someone linked this third-party "honest" status page:
Are they running paid marketing campaigns for Gitlab ?
rozabtoday at 1:26 PM
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?
voidUpdatetoday at 12:26 PM
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
throwatdem12311today at 12:57 PM
Maybe GitHub needs to freeze free repository creation until they get this under control because this is ridiculous.
hydrogenbon007today at 2:45 PM
The software reliability and uptime is going bad across the industry, railway, github etc
wild that there is a large pattern forming up of unreliable software being pushed
dzongatoday at 12:29 PM
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.
hansmayertoday at 12:52 PM
Can't they just use one of Satiya's "powerful daily prompts" and ask the - was it "Mico"? - to excrement their way out of these troubles? Ah - you're telling me those powerful prompts were just bullshit for the lazy office cretin who is mainly reading and writing emails throughout the week? They don't really create any new fucking value? No way - I thought CEOs paid tens of millions of dollars each year had real competence justifying such high salaries.
cdrnsftoday at 4:58 PM
More AI should fix it.
trenchguntoday at 3:49 PM
But everything else still works fine, right?
fen4otoday at 12:32 PM
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.
looperhackstoday at 12:26 PM
Maybe we should start posting av story when GitHub has been fine for some time instead of posting every incident
cedwstoday at 12:20 PM
I'm so done with GitHub.
maxnoetoday at 12:15 PM
GitHub Incident again/
abhashanand1501today at 12:56 PM
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?
hehe1today at 5:39 PM
dthtrj
drcongotoday at 12:37 PM
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.
Hamukotoday at 12:32 PM
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.
dist-epochtoday at 12:42 PM
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.
Arbortheustoday at 12:23 PM
Fed up and bored of this
shevy-javatoday at 2:51 PM
I think it is time to decouple GitHub from Microsoft. Microsoft has shown irresponsible behaviour - and this continues. They keep on going at it until nothing works anymore. Typical microslop work.
emartinez-devtoday at 1:11 PM
I thought it was the yesterday's thread but no, here we go again
rvztoday at 12:25 PM
Again?
It was just yesterday [0] that GA was down and another incident today? I am convinced that Copilot and Tay.ai are destroying GitHub and there is no CEO of GitHub to contact.
Now will you please self-host as I said 6 years ago? [1]