We were not able to identify the actor who is causing the high load on our systems. We have made the hard decision to temporarily shut off access to a certain project to keep Codeberg available for everyone else.
As soon as we allow web access to a certain project, our system resources are used up within seconds.
https://social.anoxinon.de/@Codeberg/113570122051262332
@Codeberg good luck dealing with this. Can you say which repo was being requested so much?
@Codeberg since you don't use a competent service for freaking 2 day to have better insight on who is the culprit and go back to what you have now after 2 freaking days …
Continue to have this […]
@Codeberg Thank you for your hard work for us, your community members. I hope you will find out what exactly happened here!
@Codeberg maybe related? mapstodon.space/@beacondb/1135…
@Codeberg i will clean empty projects, that i haven't used yet, i just was too lazy todo that /tbh :ablobcatwink:
@Codeberg I do not know the exact architecture that you have setup in Codeberg and you may have set it up already, but what about reverse proxies that introduce rate limiting based on a window […]
@Codeberg No common IP prefixes or ASNs?
@Codeberg i had somewhat similar situation this week on my forgejo instance and the only idea I had was to
Make one of my public repos private (it did help, but just a little)Block whole […]
@Codeberg fascinating. I hope this is a benign accidental ddos and not a malign one that’s *aiming* to reduce access to said project. Best of luck on this
@Codeberg oh no :(
#hugops, and let's hope these assholes go away
────
────