StatusGator last checked the status of Codeberg on July 31, 2026 at 7:57 PM CEST and the service was operational. There have been 83 user-submitted reports of outages in the past 24 hours, but the outage is now resolved.

  • Kissaki@programming.dev
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 day ago

    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

  • badmin@lemmy.today
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    1 day ago

    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 😉.

    • trem@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      7
      ·
      1 day ago

      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:
        It's currently also down due to AI scrapers...

      • 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.

      • badmin@lemmy.today
        link
        fedilink
        arrow-up
        5
        ·
        1 day ago

        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

        😊

    • thingsiplay@lemmy.mlOP
      link
      fedilink
      arrow-up
      3
      ·
      2 days ago

      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.

      • Noughtmare@programming.dev
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 day ago

        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.

  • Kissaki@programming.dev
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 day ago

    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.

  • onlinepersona@programming.dev
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    2 days ago

    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?

  • Sibbo@sopuli.xyz
    link
    fedilink
    arrow-up
    11
    ·
    2 days ago

    They seem to be a bit flakey at the moment. There has also been an outage a week or two ago.

    • thingsiplay@lemmy.mlOP
      link
      fedilink
      arrow-up
      9
      ·
      2 days ago

      Yeah looks like its been a problem since last month, according to this graph. Today was the worst being completely shutdown for hours.

    • trem@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      10
      ·
      1 day ago

      I mean, their status page says they are/were seeing lots of unauthenticated traffic, which sounds like AI scrapers hitting them…

      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. Date Created: 2026-07-31 18:27:32 (13 hours ago)

  • terabyterex@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    2 days ago

    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

    • chaospatterns@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      edit-2
      1 day ago

      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

        • chaospatterns@lemmy.world
          link
          fedilink
          English
          arrow-up
          6
          ·
          edit-2
          1 day ago

          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/