So frustrating. You can only experience so many of these outages before you seriously have to start questioning whether it makes sense to continue to use GitHub (and many have already long since reached this point)
Isn't this an example of how everyone wants to believe that vibe-coding software is enough, but no one actually wants to depend on vibe-coded software (like GitHub)?
I switched to Forgejo and it's such a breath of fresh air. You can feel the solidity, snappiness and dependability of a good old carefully coded app.
Same here. Gitea has been pleasant to use for my business, and I've had 0 downtime issues compared to near-daily problems with GitHub during the first half of the year.
Edit: Sorry, thought you wrote Gitea rather than GitLab. I've also had a nice experience with self-hosted GitLab years ago, and I'd wager that pretty much any self-hosted option would be better than GitHub at this point.
Yup am running too for 2 years now and love it. It’s my favorite service. Uptime is basically 100% since it’s only down when I’m doing server maintenance (apt get update and reboot) and then I’m not pushing anyway.
We self-host actions and this still impacted us. Incident resolved 30 minutes ago, but all our builds are still queued/pending. Maybe GitHub needs to replay some webhooks?
There has been degradation in their copilot cloud agent in the last few weeks (sessions erroring/disappearing, connections not working, etc) that is not on a status dashboard.
The more these incidents happen, the more I think about I talking to investors about investing in my GitHub alternative; an old computer in the corner running Gitea.
I don't know them, and am not an investor, but I'm trying Blacksmith as a GHA alternative because I'm losing my mind over the regular downtime. Apparently all the cool kids already use it, so... Obviously this doesn't help at all with Webhooks.
update: first jobs are green already. migration took 5 minutes. so far so good.
I'm not saying bots/LLMs aren't making GitHub's job harder but I saw an uptime graphic with a pretty stark and obvious change pre/post acquisition by Microsoft.
I have been moving everything away to a self hosted Forgejo, and I am so happy.
But now I wonder about Netlify. Their dashboard is jammed full of prompt boxes for agents. Could more AI psychosis there turn that into a house of cards as well?
So frustrating. You can only experience so many of these outages before you seriously have to start questioning whether it makes sense to continue to use GitHub (and many have already long since reached this point)
Still mid switch to self hosted Gitea here!
Isn't this an example of how everyone wants to believe that vibe-coding software is enough, but no one actually wants to depend on vibe-coded software (like GitHub)?
I switched to Forgejo and it's such a breath of fresh air. You can feel the solidity, snappiness and dependability of a good old carefully coded app.
I'm now running the actions elsewhere, but yeah, I'm almost ready to self-host a full alternative.
Forgejo with a self-hosted runner is amazing.
I implemented my own, it was time well spent.
The features I care about work as I want them to, the features I don't care about are kinda janky.
We switched to self-hosted GitLab several outages ago
Yeah, switched over to self-hosted Gitlab back in mid-June and feels like the right choice
Same here. Gitea has been pleasant to use for my business, and I've had 0 downtime issues compared to near-daily problems with GitHub during the first half of the year.
Edit: Sorry, thought you wrote Gitea rather than GitLab. I've also had a nice experience with self-hosted GitLab years ago, and I'd wager that pretty much any self-hosted option would be better than GitHub at this point.
Just don't expose them to the internet. They have a lot of CVEs latey, some even allowing full control
How would that work out for remote workers and agents?
VPN or tailscale or client certificates on https endpoint.
self hosted forgejo and forgejo action runners for my homelab
Yup am running too for 2 years now and love it. It’s my favorite service. Uptime is basically 100% since it’s only down when I’m doing server maintenance (apt get update and reboot) and then I’m not pushing anyway.
I visit https://status.github.com it is the second suggestion, after https://github.com/ itself.
We self-host actions and this still impacted us. Incident resolved 30 minutes ago, but all our builds are still queued/pending. Maybe GitHub needs to replay some webhooks?
There has been degradation in their copilot cloud agent in the last few weeks (sessions erroring/disappearing, connections not working, etc) that is not on a status dashboard.
Codeberg has been pretty stable for me
Dead in the water for actions that are merge requirements here.
The more these incidents happen, the more I think about I talking to investors about investing in my GitHub alternative; an old computer in the corner running Gitea.
I don't know them, and am not an investor, but I'm trying Blacksmith as a GHA alternative because I'm losing my mind over the regular downtime. Apparently all the cool kids already use it, so... Obviously this doesn't help at all with Webhooks.
update: first jobs are green already. migration took 5 minutes. so far so good.
Wonder how soon GitHub will tighten rate limits on OSS GitHub further and start charging per API call like x.com did to weed out bots...
Not being able to isolate OSS and Enterprise workloads properly is also quite the downer.
I'm not saying bots/LLMs aren't making GitHub's job harder but I saw an uptime graphic with a pretty stark and obvious change pre/post acquisition by Microsoft.
If you believe Twitter "weed[ed] out the bots" I have a bridge to sell you.
I have been moving everything away to a self hosted Forgejo, and I am so happy.
But now I wonder about Netlify. Their dashboard is jammed full of prompt boxes for agents. Could more AI psychosis there turn that into a house of cards as well?
Great day to be on Codeberg
i have githubstatus.com on my bookmarks. Maybe i should make it my homepage?
Another, another incident
Yet everyone still uses GitHub lolz