Still better uptime than Github
Not completely down; as a signed in user I didn't notice a thing.
Well, it was completely down in the sense that no operation was possible on the webpage. The page was just a single error code, so nothing to sign in possible. At least for me in Europe, the page and servers was out of service for about 7 hours or so (I tried over and over again, matching the experience with the graph). Maybe there were servers that was not affected at the time you logged in.
I when I read reports of the downtime on mastodon I checked status.codeberg.org and saw that almost everything was a red line, except for the authenticated traffic. I guess I was lucky that I still had my cookies.
Any official message from them? I thought they had a mastodon.
Edit: Lol the mastodon instance they're on is also down. And it's a German instance on a German cloud server. German engineering?
On their status page, it says they were being hit by lots of unauthenticated traffic, so I would assume either AI scrapers or a DDoS: https://status.codeberg.org/status/codeberg
I put a screenshot here, in case they've cleared the warning: https://lemmy.blahaj.zone/comment/21576828
AI companies, the gift that keeps on giving...
If I want to move away from GitHub, and I don't like GitLab's bloatiness, or Codeberg's general vibe, what options do I have that are not run by someone in his basement?
I'm aware of radicale. And there is also a russian forge I saw some people flock to because of the DMCA mafia. But my repos are not that edgy 😉.
I write this as a paying member of the Codeberg e.V., just so you know where my affiliation lays.
-
https://sr.ht/ is also reasonably popular, although the web interface is certainly a lot more minimal. SourceHut development and hosting of that instance and lots of other stuff is spearheaded by Drew DeVault. I have my disagreements with the guy technologically, but he holds solid views ethically, so passes the vibe check for me.
-
https://notabug.org/ has also been around for quite a few yeaes, and hosted by the https://peers.community/ non-profit. Alas:

-
Disroot also has a Forgejo instance: https://git.disroot.org/
Disroot is a community kind of pursuing decentralization and privacy online. Also been around for quite a few years by now.
Thank you. I think I knew of disroot, but now I will bookmark them.
I also just remembered tangled, which would have been an interesting federated option, if a lot of people haven't decided to hate anything that touched the AT protocol.
SourceHut
but he holds solid views ethically
😊
They seem to be a bit flakey at the moment. There has also been an outage a week or two ago.
Yeah looks like its been a problem since last month, according to this graph. Today was the worst being completely shutdown for hours.

https://status.codeberg.org/status/codeberg
Performance degradation for unauthenticated traffic
We're facing severe traffic spikes for unauthenticated traffic, impacting performance and availability. Our primary goal is to avoid interruptions for authenticated users of Codeberg.org.
Unrelated, the Mastodon instance used by the Codeberg.org status account is currently unavailable.
Date Created: 2026-07-31 18:27:32 (16 hours ago)
All Systems Operational
Well, it wasn’t AI.
I mean, their status page says they are/were seeing lots of unauthenticated traffic, which sounds like AI scrapers hitting them...

popularity is going to love them very very hard.
they need someone with a highlevel of resiliency experience. code hosting isnt normal web traffic.
i am curious what its hosted on
well, that answers that question. they need to figure out a better solution.
Codeberg runs on Forgejo which is a fork of Gitea.
I'm running Forgejo myself and am running into difficulties with High Availability. Many data files can be stored in S3 compatible interfaces, but the Git repos are stored as Git files on disk. That's hard to distribute across multiple hosts. Something like NFS seems to be prone corruption and Forgejo has to be able to lock.
An open issue on clustering : https://codeberg.org/forgejo/discussions/issues/259
Reading your comment, I immediately thought there must be an S3 FUSE wrapper out there, and quickly found this:
The problem is still concurrency. If the application, in this case the git CLI, is not thread-safe, then you could run into unsafe data mutations causing data corruption.
Imagine two pushes that come in around the same time. S3 doesn't have the locking mechanics you need to ensure that only one of those writes win and the other fails. You need to upload the individual commits (which can be isolated except in the case of multiple writes with a partial write), but then the branch and HEAD pointers have to be serialized. I've done a lot of work with distributed systems in AWS and my experience has always been to layer something like DynamoDB on-top of S3 to provide this.
My knowledge of at least one distributed Git system was that they had a fleet of Git data servers and a router on front. The router would fan it out to 3 or more data servers where each data server would store copies. But ultimately there's some application logic that is aware of the underlying filesystem and manages locking.
GitHub shares some of their architecture here: https://github.blog/engineering/infrastructure/stretching-spokes/
Servers eepy
Looks like StatusGator mentions "Codeberg reported an issue on their status page" multiple times, but links neither to the status page nor the reported incident? That seems… lacking.
Programming
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
