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.

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.

@Codeberg 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?

@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.

@Codeberg 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

@mavica_again Can you ping the IP address? Or `ssh -T git@codeberg.org` in case you have set up an SSH key?

Follow

@Codeberg 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

@Codeberg traceroute to the ipv4 seems to end at my ISP, very weird. at any rate now i'm pretty sure it's not on your end

Sign in to participate in the conversation
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!