@Codeberg Maybe somebody is abusing Codeberg for hosting stuff used in an app/website (happened to Wikimedia before)?

@Codeberg oh no :(
#hugops, and let's hope these assholes go away

@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 i had somewhat similar situation this week on my forgejo instance and the only idea I had was to

1. Make one of my public repos private (it did help, but just a little)
2. Block whole Facebook and Google ASNs

But this solution is suboptimal in your case, as you care about indexing

@Codeberg No common IP prefixes or ASNs?

@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 (e.g. https://www.haproxy.com/blog/four-examples-of-haproxy-rate-limiting ). You will need to check which software makes most sense to you here. That could address the scenario you have that a specific repository is affected.

Of course, all this does not address all possibly sources of Ddos attacks.

@Codeberg i will clean empty projects, that i haven't used yet, i just was too lazy todo that /tbh :ablobcatwink:

@Codeberg maybe related? https://mapstodon.space/@beacondb/113571837446525054

@Codeberg Thank you for your hard work for us, your community members. I hope you will find out what exactly happened here!

@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 kind of issue without knowing the culprit …
Cloudflare is the only one with this much information so … good bye to your service i guess.

@Codeberg good luck dealing with this. Can you say which repo was being requested so much?