Home | Notifications | New Note | Local | Federated | Search | Logout
Codeberg Status@codebergstatus@social.anoxinon.de
Service status announcements from the https://codeberg.org system administrators.
Replies to this account are not monitored. For more exciting news, make sure to follow @Codeberg. :)
Status Page: https://status.codeberg.eu/status/codeberg
Infrastructure Repos: https://codeberg.org/Codeberg-Infrastructure
Main Account (That You Likely Already Know Of): @Codeberg
Joined: 2026-05-04 01:54:07
6 notes, 0 following, 0 followers
Reply to @codebergstatus@social.anoxinon.de
Codeberg Status@codebergstatus@social.anoxinon.de (2026-05-27 23:45:10)
Bad news: Performance on Codeberg is still slow. We're seeing a lot of abusive cloning and crawling and have limited the ability to clone for several minutes to investigate the situation.
We're still investigating the situation and taking respective countermeasures. We try to keep the impact on legitimate usage as small as possible.
Codeberg Status@codebergstatus@social.anoxinon.de (2026-05-27 23:38:35)
Good news: We have addressed recent SSH performance degradation by replacing linear parsing of the authorized_keys file with a custom AuthorizedKeys command.
This is what GitHub and GitLab have been doing for years, and we have grown to a size where this has become necessary for us as well.
The cause for the degradation was still abusive patterns, as connections without valid key take more resources (scanning the file to the end) than legitimate users (scanning is stopped after match).
Codeberg Status@codebergstatus@social.anoxinon.de (2026-05-27 04:52:59)
You might have noticed that SSH connections are no longer being served at the moment.
As part of our investigation into the most recent slowness of Codeberg (which usually results in 504s being given), we have temporarily stopped those. This confirms a suspicion of ours that SSH connections have become, for whatever reason, heavy on the CPU.
We will resume serving SSH connections with a smaller queue to preserve the availability of Codeberg.
Codeberg Status@codebergstatus@social.anoxinon.de (2026-05-09 02:07:58)
It has been in the works for months, but the recent increase of downtime has accelerated work. We've moved from Caddy to HAProxy for codeberg.org traffic.
Starting over with a new reverse proxy has enabled us to make choices that enable us to set up HAProxy to scale with our increasing traffic. For example, traffic is split (when possible, decided via heuristics) over several instances to load balance expensive traffic.
We hope to share more details at a later time about this change.
Reply to @codebergstatus@social.anoxinon.de
Codeberg Status@codebergstatus@social.anoxinon.de (2026-05-04 01:50:22)
Hi all, sorry for the lack of updates. We did try to fix the problem shortly afterwards (and seemingly, we did), but we were alerted a few hours later that this hiccup seemingly occurred again. Thank you to the affected users that helped us notice by reporting this to us.
We fixed the problem for now through the classic "turning it off and on again method", but establishing the root cause is still a pending task.
Codeberg Status@codebergstatus@social.anoxinon.de (2026-05-03 18:30:27)
Hi, we are aware of reports that some users are not able to submit issues/pull requests. We apologize for the hiccup and are working on fixing this problem.