Zum Inhalt der Seite gehen


Although we are not fully sure yet, there is a suspicious activity pattern from Russian IP addresses that currently brings Codeberg to a halt.

If confirmed, it is the first #IPv6 #DDoS attack in our history. Previously, we were only dealing with IPv4 so far.

Als Antwort auf Codeberg.org

If you want to be sure not to get blocked by our systems, please double-check you are not asleep on the F5 key now. Okay? Great.
Als Antwort auf Codeberg.org

But I reeeeaaaallllyyyy need to check the status of my PR. How else am I supposed to know exactly when it gets rejected?
Als Antwort auf Codeberg.org

I'm screwed. I guess I'll have to run out and get a new keyboard. 😄
Als Antwort auf Codeberg.org

hi! i wasn't even accessing codeberg while this incident happened yet looks like i got caught in the crossfire and can no longer access codeberg from my home address but can through a VPN. could you please help?
Als Antwort auf maple "mavica" syrup [6502]

@mavica_again Looking at your other post, this is likely unrelated. We only block by returning a "429 Too many requests" error screen, we never refuse connections early.
Als Antwort auf Codeberg.org

i've checked my end resolves DNS correctly as 217.197.91.145 for A and 2001:67c:1401:20f0::1: for AAAA, on v4 i get a connection timed out and v6 is unreachable... very curious if nothing is blocking my connection on the remote end, then
Als Antwort auf Codeberg.org

no ssh key so can't test that, IPv6 (to any host) seems to be a network issue on my end so diregard that and i'll try to fix it, but the v4 simply gives me 100% packet loss
Als Antwort auf Oleksandr Natalenko, MSE :verified:

@oleksandr After blocking the initial bunch of Russian IP addresses, more appeared in other parts of the world. Might have been a coincidence that part of a big botnet were Russian machines,

Diese Webseite verwendet Cookies. Durch die weitere Benutzung der Webseite stimmst du dieser Verwendung zu. https://inne.city/tos