It seems everything bug CI is back up.<p>Congrats to Codeberg for having a real status page and not a made up one like AWS and many others.
What's better, CI thats built by monkeys or CI that's offline?
I agree with tpoacher.<p>A CI that's completely broken and not building anything cannot produce incorrect results.<p>If it's producing no result at all, you know it's broken, not simply incorrect.
definitely the latter.
Shame on Atlassian that during their last full bitbucket outage took an hour to even acknowledge an issue on their status page, then another full hour until the status page reflected the reality (that it was indeed a complete outage).
> Powered by Uptime Kuma<p>Uptime Kuma is really nice: <a href="https://github.com/louislam/uptime-kuma" rel="nofollow">https://github.com/louislam/uptime-kuma</a><p>Supports all sorts of alerts and can even tell you if it ever looks like your TLS certs will soon expire (if any automation is broken, or you use commercial certs with manual rotation).
Those made up status pages like AWS and Azure need to be signed up by a director so it doesn't hurt their pretty SLA.
<a href="https://social.anoxinon.de/@Codeberg/115652289949965925" rel="nofollow">https://social.anoxinon.de/@Codeberg/115652289949965925</a> , Dec 02, 2025, 10:18 PM<p>"We are currently fighting against a DDoS attack against our service and our status page. We are analyzing network traffic with the help of our ISP at the moment and let you know once we have updates to share."
Didn't SourceHut go through the same issue?<p>(Yes, I'm aware DDoS attacks are nothing new)
<a href="https://sourcehut.org/blog/2024-01-19-outage-post-mortem/" rel="nofollow">https://sourcehut.org/blog/2024-01-19-outage-post-mortem/</a><p>> At around 06:00 UTC on January 10th [2024], a layer 3 distributed denial-of-service (DDoS) attack began to target SourceHut’s PHL infrastructure. We routinely deal with and mitigate application layer (layer 7) DDoS attacks, however, a layer 3 attack takes place at a lower level and is not within our ability to mitigate without the assistance of our network provider.
They're not paying the Cloudflare protection money?
DDoS or just too many new legitimate clients?
Codeberg has been under DDOS attacks for most of 2025, someone out there has it in for them and has been attacking relentlessly. The volunteer team has been very transparent posting about in social media and their blogs.
I think it's best to take their statement at face value. I have no special insight into the organization.
Define legitimate clients. I'd guess that a good number of their "clients" are AI scrapers.
Since we've seen some high-profile projects move to Codeberg recently, and I was trying to sign-up, may be relevant to HN's interests :)
"Zig quits Github" is like two steps down from this on the front page: <a href="https://news.ycombinator.com/item?id=46131406">https://news.ycombinator.com/item?id=46131406</a><p>:D
<a href="https://codeberg.org/ziglang/zig" rel="nofollow">https://codeberg.org/ziglang/zig</a><p>Currently Zig is the second most "stared" project on Codeberg (1443 stars). The first one is forgejo/forgejo (3154 stars) which is powering Codeberg, and the third one is dnkl/foot terminal emulator (1434). (see <a href="https://codeberg.org/explore/repos?q=&only_show_relevant=true&sort=moststars" rel="nofollow">https://codeberg.org/explore/repos?q=&only_show_relevant=tru...</a>)<p>It's always interesting to see big and significant projects moving away from major commercial platforms. Could it be a sign of something new on the horizon?
I mean, just disable the AI bloat features in GitHub. I’ve been using GitHub since 2010 (15 years - holy shit I am old) and it’s still the best. I never understood the mass complaining, though I give GitLab credit for building a massive company and taking it public. When GitLab launched I was like, this is going to fail as a business 100%. I was wrong.<p>Edit: Funny enough GitLab is down 9% in pre-market and near all-time lows.
The issue with Github is that they never denied feeding ai with private repositories. Gitlab, on the contrary, issued an official statement that they don't.<p>EDIT:
here is one statement from Gitlab
<a href="https://forum.gitlab.com/t/can-i-opt-out-from-my-code-being-used-as-training-data-in-gitlab-duo/96563/5" rel="nofollow">https://forum.gitlab.com/t/can-i-opt-out-from-my-code-being-...</a><p>I thinl I also saw another one
I was thinking the same thing, looks like a hug of death.
Good thing git is distributed!<p>I always like to move as much as possible into the repo itself, 'issues' etc in a TODO, build scripts, or however you want to achieve that, so you can at least carry on uninterrupted when the host is down.
I had a few updates failing because parts of it are hosted on Codeberg. If anything, this shows that people are moving there.
Considering moving to Codeberg too, but only 90% uptime for codeberg.org has me concerned. Not a great look unfortunately
why not sourcehut?
Because the UI looks like it crafted by a Nix system admin and the user experience is garbage. Just my opinion.
Unless you want to pay for the price increase and have no issue with the owner, then go for signing up for a sourcehut account.
Here's the pricing page, for anyone curious: <a href="https://sourcehut.org/pricing/" rel="nofollow">https://sourcehut.org/pricing/</a><p>> All users who host projects on SourceHut are expected to pay according to their means. choose the subscription plan most appropriate to your means — there is no difference between the subscriptions besides price.<p>Interesting approach and asking for some money upfront to cover the actual hosting costs and other stuff feels pretty good - rather than having to worry about shady monetization and about whether your data is the product.<p>There's plenty of screenshots on the main page of the UI: <a href="https://sourcehut.org/" rel="nofollow">https://sourcehut.org/</a><p>Some people will enjoy that kind of minimalism, definitely not everyone's cup of tea - feels really fast and reminds me a bit of Kanboard, though.<p>No idea about owner, not my place to comment.
Drew's direct engagement into tech cancel-culture (with targets such as DHH, RMS, Andreas Kling, Jack Dorsey), makes it difficult to do business with him (assuming hosted sourcehut service as an alternative to codeberg). Furthermore, at the newly proposed service rates it is much more liberating to self-host (any lightweight forge–including sourcehut).
Fair enough.<p>I haven't followed closely; but the few times I did, it seemed that he had reasonably nuanced opinions translating into upholdable values, rather than overzealous cancel-fever, whether I agreed with his opinions or not. To me this is not reason enough to not use his product, and I happen to like his product (much more than the alternatives anyway).<p>Also, it would be remiss of me not to appreciate the irony that you're effectively suggesting "cancelling" his business over his opinions which you consider of a "cancelly" nature ...
So when Codeberg gets famous what's to stop Microsoft or another behemoth from acquiring it and starting the whole cycle over again?
It’s an e.V., a German legal construct for public good organizations.<p>That doesn’t make it impossible to buy it, but all profits from a sale must flow into recognized public good efforts. The incentive to sell for huge sums is just much lower for all people involved.
It is a non-profit association based in Berlin, and its very existence is a protest towards Microsoft and the other big actors in this space. And it is built on Forgejo, an open source project with a strong community around it.<p>Both Codeberg and sourcehut are good options when escaping the walled gardens of Big Tech :)
"bad press is good press"<p>I don't care for Zig at all, and had never heard of Codeberg, they are now solidified in my mind aha
I would say hug of death is very different to an outage due to an error. Still good to own up ofcourse!
probably because of the zig migration lol /jk. first big project I see
[flagged]
[flagged]
Let's see if anyone will pay for Codeberg after the migration from GitHub.