You can literally watch GitHub explode bit by bit. Take a look at the GitHub Status History; it's hilarious: https://www.githubstatus.com/history.
Status page currently says the only issue is notification delays, but I have been getting a lot of Unicorn pages while trying to access PRs.
Edit: Looks like they've got a status page up now for PRs, separate from the earlier notifications one: https://www.githubstatus.com/incidents/smf24rvl67v9
Edit: Now acknowledging issues across GitHub as a whole, not just PRs.
They added the following entry:
Investigating - We are investigating reports of impacted performance for some GitHub services. Feb 09, 2026 - 15:54 UTC
But I saw it appear just a few minutes ago, it wasn't there at 16:10 UTC.
And just now:
Investigating - We are investigating reports of degraded performance for Pull Requests Feb 09, 2026 - 16:19 UTC
Yeah I've been seeing a lot of 500 errors myself, latency seems to have spiked too: https://github.onlineornot.com/
Yep, trying to access commit details is just returning the unicorn page for me
git operations are down too.
3 outages in 3 months straight according to their own status history. https://www.githubstatus.com/history
I wonder who left the team recently. Must be someone bagged with shadow knowledge. Or maybe they send devops/devs work to another continent.
They're in the process of moving from "legacy" infra to Azure, so there's a ton of churn happening behind the scenes. That's probably why things keep exploding.
It took me a second to realize this wasn't sarcasm.
I don't know jack about shit here, but genuinely: why migrate a live production system piecewise? Wouldn't it be far more sane to start building a shadow copy on Azure and let that blow up in isolation while real users keep using the real service on """legacy""" systems that still work?
So… create your shadow system piecewise? There is no reason to have "explode production" in your workflow, unless you are truly starved for resources.
Why would you avoid a perfect opportunity to test a bunch of stuff on your customers?
That’s a safer approach but will cause teams to need to test in two infrastructures (old world and new) til the entire new environment is ready for prime time. They’re hopefully moving fast and definitely breaking things.
A few reasons:
1. Stateful systems (databases, message brokers) are hard to switch back-and-forth; you often want to migrate each one as few times as possible.
2. If something goes sideways -- especially performance-wise -- it can be hard to tell the reason if everything changed.
3. It takes a long time (months/years) to complete the migration. By doing it incrementally, you can reap the advantages of the new infra, and avoid maintaining two things.
---
All that said, GitHub is doing something wrong.
Are they just going to tough through the process and whatever...
I think it's more likely the introduction of the ability to say "fix this for me" to your LLM + "lgtm" PR reviews. That or MS doing their usual thing to acquired products.
nah, they're just showing us how to vibecode your way to success
If the $$$ they saved > the $$$ they lose then yeah it is a success. Business only cares about $$$.
I think the last major outage wasn't even two weeks ago. We've got about another 2 weeks to finish our MVP and get it launched and... this really isn't helpful. I'm getting pretty fed up of the unreliability.
Sure it is not vibe coding related
What are good alternatives to GitHub for private repos + actions? I'm considering moving my company off of it because of reliablity issues.
It probably depends on your scale, but I'd suggest self-hosting a Forgejo instance, if it's within your domain expertise to run a service like that. It's not hard to operate, it will be blazing fast, it provides most of the same capabilities, and you'll be in complete control over the costs and reliability.
A people have replied to you mentioning Codeberg, but that service is intended for Open Source projects, not private commercial work.
This. I have been using Codeberg and self-hosting Forgejo runners and I'm happy. For personal projects though, I don't know for a company.
Also very happy with SourceHut, though it is quite different (Forgejo looks like a clone of GitHub, really). The SourceHut CI is really cool, too.
We self-host Gitlab at work and it's amazing. CI/CD is great and it has never once gone down.
Codeberg is close to what i need
Gitlab.com. CI is super nice and easily self hostable.
And their status history isn't much better. It's just that they are so much smaller it's not Big News.
I heard that it's hard to maintain self-hosted Gitlab instances
Not really. About average in terms of infrastructure maintenance. Have been running our orgs instance for 5 years or so, half that time with premium and half the time with just the open source version, running on kubernetes... ran it in AWS at first, then migrated to our own infrastructure.
I type docker pull like once a month and that's it.
Uhm no? We have been self-hosting Gitlab for 6 years now with monthly updates and almost zero issues, just apt update && apt upgrade.
If you want to go really minimal you can do raw git+ssh and hooks (pre/post commit, etc).
i would imagine that's what everyone is doing instead of sitting on their hands. Setup a different remote and have your team push/pull to/from it until Github comes back up. I mean you could probably use ngrok and setup a remote on your laptop in a pinch. You shouldn't be totally blocked except for things like automated deployments or builds tied specifically to github.com
Distributed source control is distributable.
It's also fun when a Jr. on the team distributes the .env file via Git...
I left for codeberg.org and my own ci runner with woodpecker. Soooo much faster than github
At my last job I ran a GitLab instance on a tiny AWS server and ran workers on old desktop PCs in the corner of the office.
It's pretty nice if you don't mind it being some of the heaviest software you've ever seen.
I also tried gitea, but uninstalled it when I encountered nonsense restrictions with the rationale "that's how GitHub does it". It was okay, pretty lightweight, but locking out features purely because "that's what GitHub does" was just utterly unacceptable to me.
One thing that always bothered me about gitea is they wouldn't even dog food for a long time. GitLab has been developing on GitLab since forever, basically.
gitea
Gitlab.com is the obvious rec.
Gitea is great.
Don't listen to the clueless suggesting Gitlab. It's forgejo (not gitea) or tangled, that's it.
> clueless suggesting Gitlab
ad hominem isn't a very convincing argument, and as someone who also enjoys forgejo it doesn't make me feel good to see as the justification for another recommender.
Can you offer some explanation as to why Forgejo and Tangled over Gitlab or Gitea?
I personally use Gitea, so I'd appreciate some additional information.
Seems Microsoft goes downhill after all in AI.
I'm fine with that!
i was right ... https://medium.com/@patrick.szymkowiak/github-is-falling-apa...
GitHub is slowly turning into the Deutsche Bahn of git providers.
I wonder if GH charges for the runners during their downtime. Last week lot of them would retry multiple times and then fail.
Take it away from Microsoft. Not sure how this isn't an antitrust issue anyway.
At its core antitrust cases are about monopolies and how companies use anti-competitive conduct to maintain their monopoly.
Github isn't the only source control software in the market. Unless they're doing something obvious and nefarious, its doubtful the justice department will step in when you can simply choose one of many others like Bitbucket, Sourcetree, Gitlab, SVN, CVS, Fossil, DARCS, or Bazaar.
There's just too much competition in the market right now for the govt to do anything.
Minimal changes have occurred to the concept of “antitrust” since its inception as a form of societal justice against corporations, at least per my understanding.
I doubt policymakers in the early 1900s could have predicted the impact of technology and globalization on the corporate landscape, especially vis a vis “vertical integration”.
Personally, I think vertical integration is a pretty big blind spot in laws and policies that are meant to ensure that consumers are not negatively impacted by anticompetitive corporate practices. Sure, “competition” may exist, but the market activity often shifts meaningfully in a direction that is harmful consumers once the biggest players swallow another piece of the supply chain (or product concept), and not just their competitors.
Can they use Github to their advantage to maintain a monopoly if they are nefarious? Think about it.
Unfortunately the question is "have they", not "can they".
> you can simply choose one of many others
Not really. It's a network effect, like Facebook. Value scales quadratically with the number of users, because nobody wants to "have to check two apps".
We should buy out monopolies like the Chinese government does. If you corner the market, then you get a little payout and a "You beat capitalism! Play again?" prize. Other companies can still compete but the customers will get a nice state-funded high-quality option forever.
Do you also post "Take it away from $OWNER" every time your open source software breaks?
If he posted every time GitHub broke, he would have certainly have posted a bunch of times.
What antitrust issue does my open source software have?
What does antitrust have to do with the GitHub services downtime?
The more stable/secure a monopoly is in its position the less incentive it has to deliver high quality services.
If a company can build a monopoly (or oligopoly) in multiple markets, it can then use these monopolies to build stability for them all. For example, Google uses ads on the Google Search homepage to build a browser near-monopoly and uses Chrome to push people to use Google Search homepage. Both markets have to be attacked simultaneously by competitors to have a fighting chance.
It regularly breaks the workflow for thousands of FLOSS projects.
It's not an antitrust issue because antitrust laws aren't enforced in the U.S.
That's on every individual that decided to "give it" to Microsoft. Git was made precisely to make this problem go away.
Git is like 10% of building software.
Not sure how having downtime is an anti-competition issue. I'm also not sure how you think you can take things away from people? Do you think someone just gave them GitHub and then take it away? Who are you expecting to take it away? Also, does your system have 100% uptime?
Companies used to be forced to sell parts of their business when antitrust was involved. The issue isn't the downtime, they should never have been allowed to own this in the first place.
There was just a recent case with Google to decide if they would have to sell Chrome. Of course the Judge ruled no. Nowadays you can have a monopoly in 20 adjacent industries and the courts will say it's fine.
I was wondering why my AUR packages won’t update, just my luck.
So what's the moneyline on all these outages being the result of vibe-coded LLM-as-software-engineer/LLM-as-platform-engineer executive cost cutting mandates?
Yeap, getting this for the last 20 minutes. Everything green on their status pages.
Azure infra rock solid as always.
vibe coding too much?
Related incidents:
Incident with Pull Requests https://www.githubstatus.com/incidents/smf24rvl67v9
Copilot Policy Propagation Delays https://www.githubstatus.com/incidents/t5qmhtg29933
Incident with Actions https://www.githubstatus.com/incidents/tkz0ptx49rl0
Degraded performance for Copilot Coding Agent https://www.githubstatus.com/incidents/qrlc0jjgw517
Degraded Performance in Webhooks API and UI, Pull Requests https://www.githubstatus.com/incidents/ffz2k716tlhx
Can we please demand that Github provide mirror APIs to competitors? We're just asking for an extinction-level event. "Oops, our AI deleted the world's open source."
Any public source code hosting service should be able to subscribe to public repo changes. It belongs to the authors, not to Microsoft.
Every repo usually has at least one local copy somewhere, worst would be few old repos disappear.
The history of tickets and PRs would be a major loss - but a beauty of git is that if at least one dev has the repo checked out then you can easily rehost the code history.
It would be nice to have some sort of widespread standard for doing issue tracking, reviews, and CI in the repo, synced with the repo to all its clones (and fully from version-managed text-files and scripts) rather than in external, centralized, web tools.
Making it even easier to snipe accidentally committed credentials?
No, we can't. Hence Git. Use it the right way, or prepare for the fallout. Anyone looking for a good way to prepare for that, I suggest Git.
I think this is an indicator of a broader trend where tech companies put less value on quality and stability and more value on shipping new features. It’s basically the enshittification of tech
[dead]
14 incidents in February! It's February 9th! Glad to see the latest great savior phase of the AI industrial complex [1] is going just as well as all the others!
[1] https://www.theverge.com/tech/865689/microsoft-claude-code-a...
You know what I think would reverse the trend? More vibe coding!
I know you are joking but I'm sure that there is at least one director or VP inside GitHub pushing a new salvation project that must use AI to solve all the problems, when actually the most likely reason is engineers are drawing in tech debt.
Upper management in Microsoft has been bragging about their high percentage of AI generated code lately - and in the meantime we've had several disastrous Windows 11 updates with the potential to brick your machine and a slew of outages at github. I'm sure it might be something else but it's clear part of their current technical approach is utterly broken.
Utterly broken - perhaps, but apparently that's not exclusive with being highly profitable, so why should they care?
Says everything... https://www.youtube.com/shorts/Dj_f2ANBfas
Better to replace management by AI.
Computers can produce spreadsheets even better and they can warm the air around you even faster.
Honestly AI management would probably be better. "You're a competent manager, you're not allowed to break or circumvent workers right laws, you must comply with our CSR and HR policies, provide realistic estimates and deliver stable and reliable products to our customers." Then just watch half the tech sector break down, due to a lack of resources, or watch as profit is just cut in half.
Plus they don't take stock options!
It’s not a joke. This is funny because it is true.
All the cool kids move fast and break things. Why not the same for core infrastructure providers? Let's replace our engineers with markdown files named after them.
This kind of thing never happened before LLMs!
No, the reason it's happening is because they must be vibe coding! :P
[flagged]
No because you missed the joke.
That's not good enough. You need SKILLS!
I think this will continue to happen until they finish migrating to Azure
Haven't they been shown the front door?
wut
https://learn.microsoft.com/en-us/azure/frontdoor/front-door...
Someone should make a timeline chart from that, lol.
https://updog.ai/status/github
Haha, that would be awesome!
Light work for an LLM
But not Copilot.
Copilot is shown as having policy issues in the latest reports. Oh my, the irony. Satya is like "look ma, our stock is dropping...", Gee I wonder why Mr!!