12 ms·

Another GitHub outage in the same day

375 points by Nezteb 8mo ago

whateveracct 8mo ago
down to a single 9
vampiregrey 8mo ago
At this point, GitHub outages feel closer to cloud provider outages than a SaaS blip. Curious how many people here still run self-hosted Git (GitLab / Gitea) vs fully outsourcing version control.
- betaby 8mo ago
  Self hosted GitLab is absolutely worth it.
  - sam_lowry_ 8mo ago
    Self-hosted git is absolutely worth it.
  - monkaiju 8mo ago
    or forgejo!
    - zhouzhao 8mo ago
      Yeah man. Forgejo (albeit it being a weird name from a language that nobody wants to use), is doing very well in my homelab. When I worked at the univerity we used Gitea. Every job outside of univerity I had used Gitlab self hosted. While I don't like the UI or any aspect of Gitlab a lot, it gets the job done.
      - zer00eyz 8mo ago
        I use Gitea already... I haven't seen Forejo before today. Im now curious if it is worth the switch.
        terminalbraid 8mo ago
        Forejo was originally forked from Gitea
    - DeepYogurt 8mo ago
      Forgejo should 100% be people's default for self hosting
  - edverma2 8mo ago
    I was just looking into this today but it seems pricey. $29/user/month for basic features like codeowners and defining pr approval requirements. Going with Forgejo.
    - 1f60c 8mo ago
      Wait, what? So you're on the hook for backups, upgrades, etc. and you have to pay them for the privilege? I thought GitLab was free as in speech and beer.
      - cyberax 8mo ago
        It's an Open Core model. You can deploy the free version, but it lacks some pretty important features like SSO. But that $30 per month per user is also the cost for their cloud-hosted version. It also includes quite a bit of CI/CD runtime.
    - deleted 8mo ago
      [deleted]
    - rcakebread 8mo ago
      Forgejo isn't comparable.
  - vampiregrey 8mo ago
    I think i will slowly start moving to self hosted git intra at my homelab.
  - blibble 8mo ago
    forgejo doesn't need half a supercomputer to run it
  - deleted 8mo ago
    [deleted]
- neilv 8mo ago
  Yay for GitLab and Forgejo/Gitea. My previous two startups used GitLab successfully. The smaller startup used paid-tier hosted by gitlab.com. The bigger startup (with strategic cutting-edge IP, and multinational security sensitivity) used the expensive on-prem enterprise GitLab. (The latter startup, I spent some principal engineer political capital to move us to GitLab, after our software team was crippled by the Microsoft Azure-branded thing that non-software people had purchased by default. It helped that GitLab had a testimonial from Nvidia, since we were also in the AI hardware space.) If you prefer to use fully open source, or have $0 budget, there's also Forgejo (forked from Gitea). I'm using it for my current one-person side-startup, and it's mostly as good as GitLab for Git, issues, boards, and wiki. The "scoped" issue labels, which I use heavily, are standard in Foregejo, but paid-tier in GitLab. I haven't yet exercised the CI features.
  - vampiregrey 8mo ago
    I just checked out Forgejo. I think i start with it, looks clean and lightweight. For my homelab I don’t have very large requirements. Might be a good starting point for me.
- arthur-st 8mo ago
  Self-hosted Gitea is a good time if you're comfortable taking care of backups and other self-hosting stuff.
- yoyohello13 8mo ago
  We self-host the full fat version of GitLab and it's very worth it.
noodlesUK 8mo ago
Can someone in GitHub senior leadership please start paying attention and reprioritise towards actually delivering a product that's at least relatively reliable? I moved my company over to GH enterprise last year (from AzDO) and I'm considering moving us away to another vendor altogether as a result of the constant partial outages. Things that used to "just work" now are slow in the UI, and GH actions fail to schedule in a reasonable timeframe way more than they ever used to. I enjoy GH copilot as much as the next person, but ultimately I came to GH because I needed a git forge, and I will leave GH if the git forge doesn't work.
- kasey_junk 8mo ago
  “ I enjoy GH copilot as much as the next person” So not at all?
  - 1f60c 8mo ago
    That does seem to be the implication, yes. :D
  - nfg 8mo ago
    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).
    - macintux 8mo ago
      I’ve only started using it, so maybe I’m holding it wrong, but the other day I asked the IntelliJ plugin to explained two lines of code by referencing the line numbers. It printed & explained two entirely different lines in a different part of the file. I asked again. It picked two lines somewhere else. After using ChatGPT for the last 6 months or so, Copilot feels like a significant downgrade. On the other hand, it did easily diagnose a build failure I was having, so it’s not useless, just not as helpful.
    - 0xy 8mo ago
      Not even Microsoft employees like Copilot. Maybe start why not even your coworkers can use your own slop. https://www.theverge.com/tech/865689/microsoft-claude-code-anthropic-partnership-notepad https://www.theverge.com/tech/865689/microsoft-claude-code-a...
alexellisuk 8mo ago
I’m seeing 429s cascading downloading things like setup-buildx on self hosted runners. That seems odd/off. Anyone else having issues? It is blocking any kind of release
deleted 8mo ago
[deleted]
kevmo314 8mo ago
I wonder if GitHub is feeling the crush of fully automated development workflows? Must be a crazy number of commits now to personal repos that will never convert to paid orgs.
- 1f60c 8mo ago
  IME this all started after MSFT acquired GitHub but well before vibe coding took the world by storm. ETA: Tangentially, private repos became free under Microsoft ownership in 2019. If they hadn't done that, they could've extracted $4 per month from every vibe coder forever(!)
  - dizhn 8mo ago
    Is someone who is not really using github's free service losing something important?
    - _heimdall 8mo ago
      As an individual, likely not. As a team or organization there are nice benefits though.
  - globular-toast 8mo ago
    Why would every vibe coder necessarily use private repos? IIRC they were kinda forced to make private repos free because competitors like Gitlab had it and they felt threatened.
- reactordev 8mo ago
  This is the real scenario behind the scenes. They are struggling with scale.
  - zero_shift 8mo ago
    How much has the volume increased, from what you know?
falloutx 8mo ago
We can all chill for couple weeks, Github guys take your time. Infact, don't even worry about it.
Kovah 8mo ago
I consider moving away from Github, but I need a solid CI solution, and ideally a container registry as well. Would totally pay for a solution that just works. Any good recommendations?
- swamp-agr 8mo ago
  https://nix-ci.com/ https://nix-ci.com/
  - dysoco 8mo ago
    Why this and not Garnix?
- joeskyyy 8mo ago
  Long time GitLab fan myself. The platform itself is quite solid, and GitLab CI is extremely straightforward but allows for a lot of complexity if you need it. They have registries as well, though admittedly the permission stuff around them is a bit wonky. But it definitely works and integrates nicely when you use everything all in one!
- dylan604 8mo ago
  Should our repos be responsible for CI in the first place? Seems like we keep losing the idea of simple tools to do specific jobs well (unix-like) and keep growing tools to be larger while attempting to do more things much less well (microsoft-like).
  - tibbar 8mo ago
    I think most large platforms eventually split the tools out because you indeed can get MUCH better CI/CD, ticket management, documentation, etc from dedicated platforms for each. However when you're just starting out the cognitive overhead and cost of signing up and connecting multiple services is a lot higher than using all the tools bundled (initially for free) with your repo.
- tibbar 8mo ago
  Lots of dedicated CI/CD out there that works well. CircleCI has worked for me
bstsb 8mo ago
my four-core VPS running a Git server has higher uptime than GitHub at this point (although admittedly less load and redundancy)
- chilipepperhott 8mo ago
  Does redundancy even matter if the end result is still poorer uptime?
  - monkaiju 8mo ago
    Exactly! Also operating "at scale" is only impressive if you can do it with comparable speed and uptime, it doesn't mean much if every page takes seconds to load and it falls over multiple times a day lol
nhuser2221 8mo ago
I am glad I have finally started self hosting my own git server, and stop worrying about github :-)
an0malous 8mo ago
Claude, make me an SCM provider
- jraph 8mo ago
  Sure! Do you allow me to run the following command? cd project; find -type f | while read f; do mv "$f" /dev/null; done
  - tryauuum 8mo ago
    Don't do this It will break your /dev/null
    - jraph 8mo ago
      yeah, maybe do a backup before: mv /dev/null{,.bak} So you can restore it if your kernel nuked your null device.
devy 8mo ago
They were talking about prioritizing migration into Azure for a long while now. Not sure this incident today is related. https://thenewstack.io/github-will-prioritize-migrating-to-azure-over-feature-development/ https://thenewstack.io/github-will-prioritize-migrating-to-a... And coincidentally, an early CircleCI engineer wrote an article about GitHub Action (TLDR: don't use GitHub Action for CI/CD!) https://www.iankduncan.com/engineering/2026-02-05-github-actions-killing-your-team https://www.iankduncan.com/engineering/2026-02-05-github-act... https://news.ycombinator.com/item?id=46908491 https://news.ycombinator.com/item?id=46908491
- baq 8mo ago
  > TLDR: don't use GitHub Action for CI/CD! You should reach the same conclusion by trying to use it for this purpose, but also indeed for any purpose at all. Incidents that make you unable to deploy making all your CD efforts pointless are only the cherry on top.
WhyNotHugo 8mo ago
How is this "news" when it comes up multiple times a week? It's just "yet another day of business as usual" as this point.
thomasfromcdnjs 8mo ago
Someone needs to make an mcp server for my claude so it can check if services are down, it goes stir crazy when github is down and adds heaps of work around code =D
varispeed 8mo ago
Did they replace developers and devops with openclaw?
rvz 8mo ago
A great time to consider self hosting instead. Since there is no CEO of GitHub to contact anymore. A prophecy that was predicted half a decade ago [0] which is now more important then as it is now today. [0] https://news.ycombinator.com/item?id=22867803 https://news.ycombinator.com/item?id=22867803
skywhopper 8mo ago
This is the predictable outcome of subordinating the GitHub product to the overarching "AI must be part of everything whether it makes sense or not" mandate coming down from the top. It was only a year ago that GitHub was moved under the "CoreAI" group at Microsoft, and there's been plenty of stories of massive cost-cutting and forcing teams to focus on AI workflows instead of their actual product priorities. To the extent they are drinking their own Kool-Aid, this sort of ops failure is also an entirely predictable outcome of too much reliance on LLM-generated code and workflows rather than human expertise, something we see happening at an alarming scale in a number of public MS repos. Hopefully it will get bad enough fast enough that they'll recognize they need to drastically change how they are operating. But I fear we're just witnessing a slow slide into complacency and settling for being a substandard product with monopoly-power name recognition.
musha68k 8mo ago
Radicle moment.
ariedro 8mo ago
It would be interesting to have a graph showing AI adoption in coding against the number of weekly outages across different companies. I am sure they are quite correlated.
- the_real_cher 8mo ago
  I bet there's other factors that are correlated as well!
- lelanthran 8mo ago
  > It would be interesting to have a graph showing AI adoption in coding against the number of weekly outages across different companies. I am sure they are quite correlated. Probably a stronger correlation to the fact that vibe-coding has resulted in millions of new repos being created, with automatic CIs being triggered by agents continuously sending PRs for those projects.
ChrisArchitect 8mo ago
[dupe] Discussion: https://news.ycombinator.com/item?id=46946827 https://news.ycombinator.com/item?id=46946827
- esafak 8mo ago
  No, it's a new outage -- that's the point! Check the URLs.
  - ChrisArchitect 8mo ago
    That's not the point. The point is it's a duplicate discussion of one of a number of incident links being discussed, all over there.
    - bigstrat2003 8mo ago
      The point is that when a second, independent event occurs, a new thread is not a duplicate.
- rpns 8mo ago
  Not quite, that one is an earlier outage while this one started at (or a bit before) 19:01 UTC. The history for today is a bit of a mess really: https://www.githubstatus.com/history https://www.githubstatus.com/history
  - ChrisArchitect 8mo ago
    They are all being discussed in that thread, the submitted url is just one of the various incident links on the day. Duplicate discussion.
- rcakebread 8mo ago
  I'll bet you're fun at... nowhere.
heliumtera 8mo ago
Remember the other day when a bunch of yous were making fun of zig moving away from GitHub? Now suddenly you all say this is not the future you wanted. Everyday you opt in to get wrecked by Microsoft. You all do realize you all could, for a change, learn something and never again touch anything Microsoft related? Fool me once...
- TacticalCoder 8mo ago
  > You all do realize you all could, for a change, learn something and never again touch anything Microsoft related? I learned that lesson in the 90s and became an "ABM" (Anything But Microsoft). People sadly shall never learn: Windows 12 is going to come out and shall suck more than any previous version of Windows except Windows 11, so they'll see it as progress. Then Windows 13 is going to be an abysmal piece of crap and people shall hang to their Windows 12, wondering how it's possible that Microsoft came out with a bad OS. There are still people explaining, today, that Microsoft ain't all bad because Windows XP was good (for some definition of good). Windows XP came out in late 2001. Stockholm syndrome and all that.
  - alextingle 8mo ago
    Windows XP was a disaster. Resistance to adopting it was industry wide, and lasted years. It was only with Service Pack 2 (which was an enormous rewrite of basically the whole system) that they started to turn the ship around.
elzbardico 8mo ago
Yeah, Vibe code more github!
- neuropacabra 8mo ago
  So far it feels they are vibe coding it day and night lol…probably with GitHub Copilot
dec0dedab0de 8mo ago
I still say that mixing CI/CD with code/version control hosting is a mistake. At it's absolute best, everything just works silently, and you now have vendor lock-in with whichever proprietary system you chose. Switching git hosting providers should be as easy as changing your remotes and pushing. Though now a days that requires finding solutions for the MR/PR process, and the wiki, and all the extra things your team might have grown to rely on. As always, the bundle is a trap.
- bamboozled 8mo ago
  I don't think any of this was a mistake ;) Lock-in was by design.
- monkaiju 8mo ago
  I mean, not necessarily proprietary right? There are OSS solutions like forgejo that make it pretty simple, at least as simple as running a git system and a standalone CI system
  - dec0dedab0de 8mo ago
    i mean that is certainly better, but I still don’t like having them coupled. Webhooks were a great idea, and everyone seems to have forgotten about them.
atonse 8mo ago
I'm starting to wonder if people doing what were previously unconventional workflows (which may not be performance optimized) are affecting things. For example, today, I had claude basically prune all merged branches from a repo that's had 8 years of commits in it. It found and deleted 420 branches that were merged but not deleted. Deleting 420 branches at once is probably the kind of long tail workflow that was not worth optimizing in the past, right? But I'm sure devs are doing this sort of housekeeping often now, whereas in the past, we just never would've made the time to do so.
deleted 8mo ago
[deleted]
sisve 8mo ago
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.
- monkaiju 8mo ago
  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.
  - sisve 8mo ago
    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 :)
- XCSme 8mo ago
  Yeah, once you start self-hosting your code, it’s kind of nice having control over everything. Makes you think about moving other stuff, like analytics, to something self-hosted too.
danhon 8mo ago
Isn't github in the middle of their (latest) attempt to migrate to Azure?[0] [0]: https://www.theverge.com/tech/796119/microsoft-github-azure-migration-move-notepad https://www.theverge.com/tech/796119/microsoft-github-azure-...
h4kunamata 8mo ago
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 themselves. If Microsoft ever rollback, boy oh boy, things will get ugly.
- deleted 8mo ago
  [deleted]
- bsimpson 8mo ago
  Do they have their own model? I thought Copilot was a frontend for Clause et. al..
  - h4kunamata 8mo ago
    To the best of my knowledge, Copilot is a Microsof in-house thing and it sucks on everything. Claude is far superior and Microsoft is allegedly using Claude internally over its own AI solution.
    - rohanmallya 8mo ago
      Github Copilot is just a front-end. You pay for the frontend and some premium requests every month. The base models like GPT 4o, 4.1 don’t have a usage cap. Models like Claude Sonet, Opus, etc have a monthly limit and you can pay more to use these through Github Copilot.
      - h4kunamata 8mo ago
        >Github Copilot is just a front-end Yes, Copilot is often used to refer to both frontend and backend. Also, the chatbot aka Copilot must have features on its own. Like I say to Roo Code/Cline on VSCode: Write a python script to output hello world. And they will do exactly that, Roo Code is pretty impressive. Copilot on its own is dogshit and when using it the same way I would use Perplexity AI or ChatGPT, it is twice as much dogshit.
mrshu 8mo ago
This (multiple major outages a day) has unfortunately been happening for quite a while now -- on the 2nd of February, 2026 for instance. The GitHub Status Page does not visualize these very well but you can see them parsed out and aggregated here: https://mrshu.github.io/github-statuses/ https://mrshu.github.io/github-statuses/
- flowardnut 8mo ago
  https://updog.ai/status/github https://updog.ai/status/github this is also scraped from datadog usage of github.
  - deleted 8mo ago
    [deleted]
- theamk 8mo ago
  this one does not seem to be updated? last outage is Feb 6...
  - Arbortheus 8mo ago
    It seems to be correct now
jamiemallers 8mo ago
[dead]
- philipwhiuk 8mo ago
  > 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.
deleted 8mo ago
[deleted]
jamiemallers 8mo ago
[dead]
oldestofsports 8mo ago
My company just migrated to GitHub, and it's been a shockingly bad experience. BitBucket never felt like anything more than a tool that did the job, but now I really miss it.
panny 8mo ago
GitHub started moving to Azure 3-4 months ago, https://archive.is/VD38Q https://archive.is/VD38Q I wonder how much of these outages are related.
natas 8mo ago
This is exactly why my employer is unlikely to adopt Azure. When CoreAI assets like GitHub appear poorly managed, it undermines confidence in the rest of the ecosystem. It’s unfortunate, because Microsoft seems to overlook how strongly consumer experience shapes business perception. Once trust is damaged, no amount of advertising spend can fully restore it.
- athorax 8mo ago
  They dont care. Their sales reps absolutely know that if you are using Microsoft products it is because you are locked in so deeply that escape is nearly impossible.
shwetanshu21 8mo ago
I guess firing so many in the Github team was not that wise a decision. But immediate share holder value go vrooom. Long term impact? Leadership aint gonna stay to see that.
- dijit 8mo ago
  Lets be real, these outages were happening for years, nobody cares because nobody is accountable when you're too big to fail.
frobisher 8mo ago
The "acquired by Microsoft" curse. OpenAI is already ongoing!
frobisher 8mo ago
I wonder if IPFS or some form of distributed storage will ever be good enough as an alternative?
jesperordrup 8mo ago
Its either https://www.reddit.com/r/selfhosted/comments/1n0h8vy/selfhosted_git_forgejo_vs_gitea_vs_gogs/ https://www.reddit.com/r/selfhosted/comments/1n0h8vy/selfhos...
pyb 8mo ago
Reminded of Dan Luu's post on the Normalization of Deviance (2015, https://danluu.com/wat/ https://danluu.com/wat/) "There's the company with a reputation for having great engineering practices that had 2 9s of reliability last time I checked..." Now it's 2026, and customers are grudgingly accepting zero 9's of reliability.
rambojohnson 8mo ago
If a few minutes of outage sends your org into existential crisis mode, the problem might not be GitHub. It might be architecture.
XCSme 8mo ago
This is exactly why so many people are thinking about self-hosting everything. Analytics is another big point of failure and a potential privacy risk that often gets overlooked. Relying on third-party tools means any outage, policy change, or data mishap can affect you directly. Using a self-hosted solution [0] gives you full control over your data and lets you decide how it’s collected, stored, and shared. For teams that care about reliability and privacy, it removes a layer of external risk most people don’t even think about. [0] https://www.uxwizz.com https://www.uxwizz.com

375 points by Nezteb 8mo ago

down to a single 9

At this point, GitHub outages feel closer to cloud provider outages than a SaaS blip. Curious how many people here still run self-hosted Git (GitLab / Gitea) vs fully outsourcing version control.

betaby 8mo ago
Self hosted GitLab is absolutely worth it.
- sam_lowry_ 8mo ago
  Self-hosted git is absolutely worth it.
- monkaiju 8mo ago
  or forgejo!
  - zhouzhao 8mo ago
    Yeah man. Forgejo (albeit it being a weird name from a language that nobody wants to use), is doing very well in my homelab. When I worked at the univerity we used Gitea. Every job outside of univerity I had used Gitlab self hosted. While I don't like the UI or any aspect of Gitlab a lot, it gets the job done.
    - zer00eyz 8mo ago
      I use Gitea already... I haven't seen Forejo before today. Im now curious if it is worth the switch.
      - terminalbraid 8mo ago
        Forejo was originally forked from Gitea
  - DeepYogurt 8mo ago
    Forgejo should 100% be people's default for self hosting
- edverma2 8mo ago
  I was just looking into this today but it seems pricey. $29/user/month for basic features like codeowners and defining pr approval requirements. Going with Forgejo.
  - 1f60c 8mo ago
    Wait, what? So you're on the hook for backups, upgrades, etc. and you have to pay them for the privilege? I thought GitLab was free as in speech and beer.
    - cyberax 8mo ago
      It's an Open Core model. You can deploy the free version, but it lacks some pretty important features like SSO. But that $30 per month per user is also the cost for their cloud-hosted version. It also includes quite a bit of CI/CD runtime.
  - deleted 8mo ago
    [deleted]
  - rcakebread 8mo ago
    Forgejo isn't comparable.
- vampiregrey 8mo ago
  I think i will slowly start moving to self hosted git intra at my homelab.
- blibble 8mo ago
  forgejo doesn't need half a supercomputer to run it
- deleted 8mo ago
  [deleted]
neilv 8mo ago
Yay for GitLab and Forgejo/Gitea. My previous two startups used GitLab successfully. The smaller startup used paid-tier hosted by gitlab.com. The bigger startup (with strategic cutting-edge IP, and multinational security sensitivity) used the expensive on-prem enterprise GitLab. (The latter startup, I spent some principal engineer political capital to move us to GitLab, after our software team was crippled by the Microsoft Azure-branded thing that non-software people had purchased by default. It helped that GitLab had a testimonial from Nvidia, since we were also in the AI hardware space.) If you prefer to use fully open source, or have $0 budget, there's also Forgejo (forked from Gitea). I'm using it for my current one-person side-startup, and it's mostly as good as GitLab for Git, issues, boards, and wiki. The "scoped" issue labels, which I use heavily, are standard in Foregejo, but paid-tier in GitLab. I haven't yet exercised the CI features.
- vampiregrey 8mo ago
  I just checked out Forgejo. I think i start with it, looks clean and lightweight. For my homelab I don’t have very large requirements. Might be a good starting point for me.
arthur-st 8mo ago
Self-hosted Gitea is a good time if you're comfortable taking care of backups and other self-hosting stuff.
yoyohello13 8mo ago
We self-host the full fat version of GitLab and it's very worth it.

noodlesUK 8mo ago

Can someone in GitHub senior leadership please start paying attention and reprioritise towards actually delivering a product that's at least relatively reliable? I moved my company over to GH enterprise last year (from AzDO) and I'm considering moving us away to another vendor altogether as a result of the constant partial outages. Things that used to "just work" now are slow in the UI, and GH actions fail to schedule in a reasonable timeframe way more than they ever used to. I enjoy GH copilot as much as the next person, but ultimately I came to GH because I needed a git forge, and I will leave GH if the git forge doesn't work.

kasey_junk 8mo ago
“ I enjoy GH copilot as much as the next person” So not at all?
- 1f60c 8mo ago
  That does seem to be the implication, yes. :D
- nfg 8mo ago
  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).
  - macintux 8mo ago
    I’ve only started using it, so maybe I’m holding it wrong, but the other day I asked the IntelliJ plugin to explained two lines of code by referencing the line numbers. It printed & explained two entirely different lines in a different part of the file. I asked again. It picked two lines somewhere else. After using ChatGPT for the last 6 months or so, Copilot feels like a significant downgrade. On the other hand, it did easily diagnose a build failure I was having, so it’s not useless, just not as helpful.
  - 0xy 8mo ago
    Not even Microsoft employees like Copilot. Maybe start why not even your coworkers can use your own slop. https://www.theverge.com/tech/865689/microsoft-claude-code-anthropic-partnership-notepad https://www.theverge.com/tech/865689/microsoft-claude-code-a...

alexellisuk 8mo ago

I’m seeing 429s cascading downloading things like setup-buildx on self hosted runners. That seems odd/off. Anyone else having issues? It is blocking any kind of release

deleted 8mo ago

[deleted]

kevmo314 8mo ago

I wonder if GitHub is feeling the crush of fully automated development workflows? Must be a crazy number of commits now to personal repos that will never convert to paid orgs.

1f60c 8mo ago
IME this all started after MSFT acquired GitHub but well before vibe coding took the world by storm. ETA: Tangentially, private repos became free under Microsoft ownership in 2019. If they hadn't done that, they could've extracted $4 per month from every vibe coder forever(!)
- dizhn 8mo ago
  Is someone who is not really using github's free service losing something important?
  - _heimdall 8mo ago
    As an individual, likely not. As a team or organization there are nice benefits though.
- globular-toast 8mo ago
  Why would every vibe coder necessarily use private repos? IIRC they were kinda forced to make private repos free because competitors like Gitlab had it and they felt threatened.
reactordev 8mo ago
This is the real scenario behind the scenes. They are struggling with scale.
- zero_shift 8mo ago
  How much has the volume increased, from what you know?

falloutx 8mo ago

We can all chill for couple weeks, Github guys take your time. Infact, don't even worry about it.

Kovah 8mo ago

I consider moving away from Github, but I need a solid CI solution, and ideally a container registry as well. Would totally pay for a solution that just works. Any good recommendations?

swamp-agr 8mo ago
https://nix-ci.com/ https://nix-ci.com/
- dysoco 8mo ago
  Why this and not Garnix?
joeskyyy 8mo ago
Long time GitLab fan myself. The platform itself is quite solid, and GitLab CI is extremely straightforward but allows for a lot of complexity if you need it. They have registries as well, though admittedly the permission stuff around them is a bit wonky. But it definitely works and integrates nicely when you use everything all in one!
dylan604 8mo ago
Should our repos be responsible for CI in the first place? Seems like we keep losing the idea of simple tools to do specific jobs well (unix-like) and keep growing tools to be larger while attempting to do more things much less well (microsoft-like).
- tibbar 8mo ago
  I think most large platforms eventually split the tools out because you indeed can get MUCH better CI/CD, ticket management, documentation, etc from dedicated platforms for each. However when you're just starting out the cognitive overhead and cost of signing up and connecting multiple services is a lot higher than using all the tools bundled (initially for free) with your repo.
tibbar 8mo ago
Lots of dedicated CI/CD out there that works well. CircleCI has worked for me

bstsb 8mo ago

my four-core VPS running a Git server has higher uptime than GitHub at this point (although admittedly less load and redundancy)

chilipepperhott 8mo ago
Does redundancy even matter if the end result is still poorer uptime?
- monkaiju 8mo ago
  Exactly! Also operating "at scale" is only impressive if you can do it with comparable speed and uptime, it doesn't mean much if every page takes seconds to load and it falls over multiple times a day lol

nhuser2221 8mo ago

I am glad I have finally started self hosting my own git server, and stop worrying about github :-)

an0malous 8mo ago

Claude, make me an SCM provider

jraph 8mo ago
Sure! Do you allow me to run the following command? cd project; find -type f | while read f; do mv "$f" /dev/null; done
- tryauuum 8mo ago
  Don't do this It will break your /dev/null
  - jraph 8mo ago
    yeah, maybe do a backup before: mv /dev/null{,.bak} So you can restore it if your kernel nuked your null device.

devy 8mo ago

They were talking about prioritizing migration into Azure for a long while now. Not sure this incident today is related. https://thenewstack.io/github-will-prioritize-migrating-to-azure-over-feature-development/ https://thenewstack.io/github-will-prioritize-migrating-to-a... And coincidentally, an early CircleCI engineer wrote an article about GitHub Action (TLDR: don't use GitHub Action for CI/CD!) https://www.iankduncan.com/engineering/2026-02-05-github-actions-killing-your-team https://www.iankduncan.com/engineering/2026-02-05-github-act... https://news.ycombinator.com/item?id=46908491 https://news.ycombinator.com/item?id=46908491

baq 8mo ago
> TLDR: don't use GitHub Action for CI/CD! You should reach the same conclusion by trying to use it for this purpose, but also indeed for any purpose at all. Incidents that make you unable to deploy making all your CD efforts pointless are only the cherry on top.

WhyNotHugo 8mo ago

How is this "news" when it comes up multiple times a week? It's just "yet another day of business as usual" as this point.

thomasfromcdnjs 8mo ago

Someone needs to make an mcp server for my claude so it can check if services are down, it goes stir crazy when github is down and adds heaps of work around code =D

varispeed 8mo ago

Did they replace developers and devops with openclaw?

rvz 8mo ago

A great time to consider self hosting instead. Since there is no CEO of GitHub to contact anymore. A prophecy that was predicted half a decade ago [0] which is now more important then as it is now today. [0] https://news.ycombinator.com/item?id=22867803 https://news.ycombinator.com/item?id=22867803

skywhopper 8mo ago

This is the predictable outcome of subordinating the GitHub product to the overarching "AI must be part of everything whether it makes sense or not" mandate coming down from the top. It was only a year ago that GitHub was moved under the "CoreAI" group at Microsoft, and there's been plenty of stories of massive cost-cutting and forcing teams to focus on AI workflows instead of their actual product priorities. To the extent they are drinking their own Kool-Aid, this sort of ops failure is also an entirely predictable outcome of too much reliance on LLM-generated code and workflows rather than human expertise, something we see happening at an alarming scale in a number of public MS repos. Hopefully it will get bad enough fast enough that they'll recognize they need to drastically change how they are operating. But I fear we're just witnessing a slow slide into complacency and settling for being a substandard product with monopoly-power name recognition.

musha68k 8mo ago

Radicle moment.

ariedro 8mo ago

It would be interesting to have a graph showing AI adoption in coding against the number of weekly outages across different companies. I am sure they are quite correlated.

the_real_cher 8mo ago
I bet there's other factors that are correlated as well!
lelanthran 8mo ago
> It would be interesting to have a graph showing AI adoption in coding against the number of weekly outages across different companies. I am sure they are quite correlated. Probably a stronger correlation to the fact that vibe-coding has resulted in millions of new repos being created, with automatic CIs being triggered by agents continuously sending PRs for those projects.

ChrisArchitect 8mo ago

[dupe] Discussion: https://news.ycombinator.com/item?id=46946827 https://news.ycombinator.com/item?id=46946827

esafak 8mo ago
No, it's a new outage -- that's the point! Check the URLs.
- ChrisArchitect 8mo ago
  That's not the point. The point is it's a duplicate discussion of one of a number of incident links being discussed, all over there.
  - bigstrat2003 8mo ago
    The point is that when a second, independent event occurs, a new thread is not a duplicate.
rpns 8mo ago
Not quite, that one is an earlier outage while this one started at (or a bit before) 19:01 UTC. The history for today is a bit of a mess really: https://www.githubstatus.com/history https://www.githubstatus.com/history
- ChrisArchitect 8mo ago
  They are all being discussed in that thread, the submitted url is just one of the various incident links on the day. Duplicate discussion.
rcakebread 8mo ago
I'll bet you're fun at... nowhere.

heliumtera 8mo ago

Remember the other day when a bunch of yous were making fun of zig moving away from GitHub? Now suddenly you all say this is not the future you wanted. Everyday you opt in to get wrecked by Microsoft. You all do realize you all could, for a change, learn something and never again touch anything Microsoft related? Fool me once...

TacticalCoder 8mo ago
> You all do realize you all could, for a change, learn something and never again touch anything Microsoft related? I learned that lesson in the 90s and became an "ABM" (Anything But Microsoft). People sadly shall never learn: Windows 12 is going to come out and shall suck more than any previous version of Windows except Windows 11, so they'll see it as progress. Then Windows 13 is going to be an abysmal piece of crap and people shall hang to their Windows 12, wondering how it's possible that Microsoft came out with a bad OS. There are still people explaining, today, that Microsoft ain't all bad because Windows XP was good (for some definition of good). Windows XP came out in late 2001. Stockholm syndrome and all that.
- alextingle 8mo ago
  Windows XP was a disaster. Resistance to adopting it was industry wide, and lasted years. It was only with Service Pack 2 (which was an enormous rewrite of basically the whole system) that they started to turn the ship around.

elzbardico 8mo ago

Yeah, Vibe code more github!

neuropacabra 8mo ago
So far it feels they are vibe coding it day and night lol…probably with GitHub Copilot

dec0dedab0de 8mo ago

I still say that mixing CI/CD with code/version control hosting is a mistake. At it's absolute best, everything just works silently, and you now have vendor lock-in with whichever proprietary system you chose. Switching git hosting providers should be as easy as changing your remotes and pushing. Though now a days that requires finding solutions for the MR/PR process, and the wiki, and all the extra things your team might have grown to rely on. As always, the bundle is a trap.

bamboozled 8mo ago
I don't think any of this was a mistake ;) Lock-in was by design.
monkaiju 8mo ago
I mean, not necessarily proprietary right? There are OSS solutions like forgejo that make it pretty simple, at least as simple as running a git system and a standalone CI system
- dec0dedab0de 8mo ago
  i mean that is certainly better, but I still don’t like having them coupled. Webhooks were a great idea, and everyone seems to have forgotten about them.

atonse 8mo ago

I'm starting to wonder if people doing what were previously unconventional workflows (which may not be performance optimized) are affecting things. For example, today, I had claude basically prune all merged branches from a repo that's had 8 years of commits in it. It found and deleted 420 branches that were merged but not deleted. Deleting 420 branches at once is probably the kind of long tail workflow that was not worth optimizing in the past, right? But I'm sure devs are doing this sort of housekeeping often now, whereas in the past, we just never would've made the time to do so.

deleted 8mo ago

[deleted]

sisve 8mo ago

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.

monkaiju 8mo ago
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.
- sisve 8mo ago
  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 :)
XCSme 8mo ago
Yeah, once you start self-hosting your code, it’s kind of nice having control over everything. Makes you think about moving other stuff, like analytics, to something self-hosted too.

danhon 8mo ago

Isn't github in the middle of their (latest) attempt to migrate to Azure?[0] [0]: https://www.theverge.com/tech/796119/microsoft-github-azure-migration-move-notepad https://www.theverge.com/tech/796119/microsoft-github-azure-...

h4kunamata 8mo ago

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 themselves. If Microsoft ever rollback, boy oh boy, things will get ugly.

deleted 8mo ago
[deleted]
bsimpson 8mo ago
Do they have their own model? I thought Copilot was a frontend for Clause et. al..
- h4kunamata 8mo ago
  To the best of my knowledge, Copilot is a Microsof in-house thing and it sucks on everything. Claude is far superior and Microsoft is allegedly using Claude internally over its own AI solution.
  - rohanmallya 8mo ago
    Github Copilot is just a front-end. You pay for the frontend and some premium requests every month. The base models like GPT 4o, 4.1 don’t have a usage cap. Models like Claude Sonet, Opus, etc have a monthly limit and you can pay more to use these through Github Copilot.
    - h4kunamata 8mo ago
      >Github Copilot is just a front-end Yes, Copilot is often used to refer to both frontend and backend. Also, the chatbot aka Copilot must have features on its own. Like I say to Roo Code/Cline on VSCode: Write a python script to output hello world. And they will do exactly that, Roo Code is pretty impressive. Copilot on its own is dogshit and when using it the same way I would use Perplexity AI or ChatGPT, it is twice as much dogshit.

mrshu 8mo ago

This (multiple major outages a day) has unfortunately been happening for quite a while now -- on the 2nd of February, 2026 for instance. The GitHub Status Page does not visualize these very well but you can see them parsed out and aggregated here: https://mrshu.github.io/github-statuses/ https://mrshu.github.io/github-statuses/

flowardnut 8mo ago
https://updog.ai/status/github https://updog.ai/status/github this is also scraped from datadog usage of github.
- deleted 8mo ago
  [deleted]
theamk 8mo ago
this one does not seem to be updated? last outage is Feb 6...
- Arbortheus 8mo ago
  It seems to be correct now

jamiemallers 8mo ago

[dead]

philipwhiuk 8mo ago
> 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.

deleted 8mo ago

[deleted]

jamiemallers 8mo ago

[dead]

oldestofsports 8mo ago

My company just migrated to GitHub, and it's been a shockingly bad experience. BitBucket never felt like anything more than a tool that did the job, but now I really miss it.

panny 8mo ago

GitHub started moving to Azure 3-4 months ago, https://archive.is/VD38Q https://archive.is/VD38Q I wonder how much of these outages are related.

natas 8mo ago

This is exactly why my employer is unlikely to adopt Azure. When CoreAI assets like GitHub appear poorly managed, it undermines confidence in the rest of the ecosystem. It’s unfortunate, because Microsoft seems to overlook how strongly consumer experience shapes business perception. Once trust is damaged, no amount of advertising spend can fully restore it.

athorax 8mo ago
They dont care. Their sales reps absolutely know that if you are using Microsoft products it is because you are locked in so deeply that escape is nearly impossible.

shwetanshu21 8mo ago

I guess firing so many in the Github team was not that wise a decision. But immediate share holder value go vrooom. Long term impact? Leadership aint gonna stay to see that.

dijit 8mo ago
Lets be real, these outages were happening for years, nobody cares because nobody is accountable when you're too big to fail.

frobisher 8mo ago

The "acquired by Microsoft" curse. OpenAI is already ongoing!

frobisher 8mo ago

I wonder if IPFS or some form of distributed storage will ever be good enough as an alternative?

jesperordrup 8mo ago

Its either https://www.reddit.com/r/selfhosted/comments/1n0h8vy/selfhosted_git_forgejo_vs_gitea_vs_gogs/ https://www.reddit.com/r/selfhosted/comments/1n0h8vy/selfhos...

pyb 8mo ago

Reminded of Dan Luu's post on the Normalization of Deviance (2015, https://danluu.com/wat/ https://danluu.com/wat/) "There's the company with a reputation for having great engineering practices that had 2 9s of reliability last time I checked..." Now it's 2026, and customers are grudgingly accepting zero 9's of reliability.

rambojohnson 8mo ago

If a few minutes of outage sends your org into existential crisis mode, the problem might not be GitHub. It might be architecture.

XCSme 8mo ago

This is exactly why so many people are thinking about self-hosting everything. Analytics is another big point of failure and a potential privacy risk that often gets overlooked. Relying on third-party tools means any outage, policy change, or data mishap can affect you directly. Using a self-hosted solution [0] gives you full control over your data and lets you decide how it’s collected, stored, and shared. For teams that care about reliability and privacy, it removes a layer of external risk most people don’t even think about. [0] https://www.uxwizz.com https://www.uxwizz.com