Incident with Pull Requests, Git Operations and Issues

githubstatus.com

264 points by kevcampb 3 days ago


gophigure - 3 days ago

What I find problematic, especially for teams that rely on GitOps and GitHub being (relatively) stable, is the fact that GitHub's status page can't be relied on. You arrive at the conclusion, "this must be GitHub," but the status page rejects the notion, and so you go digging. That can lead to a lot of toil and wasted time, in addition to sideways looks paired with comments like, "but status shows green."

A sick person with symptoms is clearly sick, but sometimes they're asymptomatic. That's what the GitHub status page has become. When it's red and showing problems, you know you have problems. When it's all green? You know you MIGHT have problems.

That can make outages like this harder to triage, since reality is a black box.

a-squirrel-comm - 3 days ago

It looks like today there was maintenance scheduled to deprecate support for certain categories of SSH keys: https://github.blog/changelog/2026-09-22-security-improvemen...

> November 4, 2026: We’ll have a brownout of the removal of the ssh-rsa signature type (i.e., RSA keys using SHA-1) and the diffie-hellman-group-exchange-sha256 key exchange algorithm.

I guess something went sideways.

rarisma - 3 days ago

       - - >  i wake up - -
       |                  |
       |                  V
       github has an outage
eknkc - 3 days ago

Our deploys are tied to GitHub actions and it is becoming a liability at this point. What alternatives do people use? I mean for FOSS there are some decent stuff but we need a reliable provider for private repos.

cashbreaker - 3 days ago

I was thinking I'm going crazy with me ssh keys not working on both of my machines.

swe_dima - 3 days ago

Temporary workaround is to do

git config --global url."https://github.com/".insteadOf git@github.com:

so it pushes / pulls using HTTPS

when things are back to normal run:

git config --global --unset url."https://github.com/".insteadOf

igleria - 3 days ago

Can't they just... sell github back like when the germans sold the nuclear plant back to mr burns?

renehsz - 3 days ago

https://GiveUpGithub.org - why and how to ditch GitHub.

luciandan - 2 days ago

Each time something like this happens, I take another look at Forgejo. Using an AI assistant it's not that complicated to set up, but it does feel too complex. So then I accept the fact that GitHub is still the best in class for now.

Until next time. When I look into alternatives again. Probably, one day, I'll actually migrate away. But for now I shrug and tell myself that these things happen.

fauzanhilmi - 3 days ago

For a moment I thought my ssh key got breached. Fricking hell Github!

feukon - 3 days ago

The day GitHub will no longer be free is approaching... they just can't support the abnormal amount of things being pushed rn

colek42 - 3 days ago

Why do we need centralized CI? We just need a gate to make sure the code passes the right checks before we move the tip.

gowthamgts12 - 3 days ago

they marked incident with Pull requests, Git operations and issues - but i don't see any outage in the bars for today other than pull requests? what's the point of showing uptime there then? https://mrshu.github.io/github-statuses is more reliable than the official github status page.

new incident with actions now - https://www.githubstatus.com/incidents/h02n9572mx9y.

alper - 3 days ago

Same old same old.

What were the 60'000 people exiting Microsoft doing if not improving Github?

- 3 days ago
[deleted]
znpy - 3 days ago

I miss working with a self-hosted gitlab instance.

misnome - 3 days ago

At this point, even when there isn't an incident, push/pull have been so unreliable as to fail about 30% of the time.

I can live with the occasional outage but this is a constant problem.

chinathrow - 3 days ago

git clone works sometimes, sometimes not.

taran_narat - 3 days ago

The outage was quite short

thesdev - 3 days ago

Finally a GitHub outage during European workday. Yaaay.

sognetic - 3 days ago

Can't even pull no more using my key. That's a new low, I'm used to the website being janky nowadays but this is seriously essential

marvstazar - 3 days ago

Pretty good timing now that Rails has released a security update :|

https://rubyonrails.org/2026/11/4/Rails-8.0.5.2-and-8.1.4.1-...

esafak - 3 days ago

There are two more incidents:

https://www.githubstatus.com/incidents/xr3myzj7ms51

https://www.githubstatus.com/incidents/h02n9572mx9y

Get your act together, clowns.

giwook - 3 days ago

It’s kinda funny that GitHub having issues continues to make HN front page.

Perhaps these types of posts should just be pinned at this point.

dude250711 - 3 days ago

These days, perhaps, normal undisrupted operation should start counting as an incident...

grishka - 3 days ago

I managed to push a commit over ssh but then the client threw an error before the push fully completed. I can see the commit on the web, but my client still thinks it isn't pushed. And now when I try to fetch I get "permission denied" after a long wait, which is scary. I first thought something got hacked.

Maybe they need a better AI model for their vibe coding. That'll fix everything, right? At least that's what my friends keep telling me when I say that the free LLMs I played around with a bit are incredibly dumb.

rvz - 3 days ago

Another incident. Last time we had one was 5 days ago [0]

It's up to you if you want more of this instability. Perhaps you should consider a self-hosted alternative.

[0] https://news.ycombinator.com/item?id=50307843

el_psy_congroo - 3 days ago

actions still don't work correctly

sigmonsays - 3 days ago

Github only has issues on days that end in Y!

esher - 3 days ago

Again and again?

dankobgd - 3 days ago

too much slop got them

urios - 2 days ago

[flagged]

kitehosting - 3 days ago

[flagged]

larsnystrom - 3 days ago

Why haven’t they asked an AI agent to fix all their bugs yet? /s

SlightGenius - 3 days ago

[flagged]

malikolivier - 3 days ago

GitHub outages can be a drain on productivity. If your stack is pulling artifacts from GitHub, and this consistently fails during GitHub outage, you can consider having a file-cache in between.

Some of our customers unexpectedly started using the service we're running as a file-cache around GitHub to mitigate GitHub outages.

We wrote about this use case in our blog: https://www.stablebuild.com/blog/protect-your-builds-from-gi...

fredsted - 3 days ago

Just set up a Gitea instance, pushed my code and switched my deployment script to it. Took 30 minutes. Github pulls still aren't working.