After blocking double-digit number of IP ranges, the amount of traffic is still ramping up.
Unfortunately, the amount of traffic is just too much for us to deal with. There is a much bigger player on the other end.
Top-level
After blocking double-digit number of IP ranges, the amount of traffic is still ramping up. Unfortunately, the amount of traffic is just too much for us to deal with. There is a much bigger player on the other end. 11 comments
@Codeberg are they flooding the pipe simply with gigabits / packets per second, or are requests coming through from too many IP addresses which causes too high a cpu load in request processing? It sounds like the latter, in which case I don't understand why not block the entire autonomous system temporarily (while this is figured out) @luc They are distributing requests over multiple /18 to /20 networks, each single IP having only few requests so they are not detected by our automated rate-limiting. @luc And yes, we are blocking complete IP ranges according to whois data, but Huaweicloud has a lot of them. And we are not yet sure if all of them are malicious (could be a single customer who ordered much cloud computing) We believe the situation is now contained. We'll continue to monitor for suspicious traffic spikes. We apologize for the inconvenience the degraded performance might have caused. Thank you for supporting our mission. If you want to learn how you can help, check out https://docs.codeberg.org/improving-codeberg/ @Codeberg Did you come up with any ideas on how to prevent similar issues in the future? |
@Codeberg@social.anoxinon.de who the hell keeps taking such issue with you guys?? this is really rude