We are currently suffering from another network-level DDoS attack, connectivity via IPv4 is impacted.
If you are able to use IPv6 you should be able to have good connectivity to Codeberg.
We are currently working on a DDoS mitigation solution for the IPv4 route.
We have found a solution together with @as9136 that will likely provide sufficient protection for IPv4 users, and we have a good idea how a long-term setup can look like (but it will take a while to get there). Thanks a lot for all the networking and support!
The switch is awaiting DNS propagation (pending for > 30 minutes already, and might take another hour for some users. And indeed, we are not happy with the service quality of #namesilo).
@Codeberg is there anything we can do to help
@Codeberg Do we know why Codeberg is being targeted? Is it to do with the notification that was sent out recently?
@tripplehelix @Codeberg Codeberg hosts LGBTQ+ community software, so extrem-right groups are attacking it
The email issue and current DDoS are made by the same actors
@Codeberg I’m sorry people are being dipshits.
@Codeberg Damn, I'm so sorry :(
I don't know what else I could do/offer, but are donations needed to keep things going?
@jbowen We have received a lot of donations, and they will be put to good use in the long term.
Currently, the rate at which we can turn money into infrastructure improvements is the bottleneck.
However, we have found a potentially good solution with nice partners, but wait for DNS propagation.
If it is in some way tied to the recent comment spamming episode, I might be able to offer a possible reason for the targetings.
I was 'mentioned' in one of the incident postings [issue no. 121]. I have multiple repositories on #codeberg, but only one of them is not a fork or rewrite of another project. That one has a #CodeOfConduct attached, which leaves no uncertainty about #BadBehaviors for commenters or issue participants when it comes to inclusion or diversity.
@tripplehelix @Codeberg ... well, just a thought. Otherwise, I'm clueless why anyone would either be spamming or doing the DDoS stuff.
@lumiworx
They mentioned all codeberg users seemingly randomly, but the spam started in some specific repositories about #transrights and #humanrights, so it's probably connected to this.
@tripplehelix
@tripplehelix @lumiworx @Codeberg Same here. At the time, I had 3 repos on Codeberg, none with a code of conduct, and I still got the abusive email.
@tripplehelix @lumiworx @Codeberg (OTOH, I do have "pronouns in bio", so maybe that's one of the things that really gets these shitheads all riled up.)
@dpnash I believe it was "spray 'n pray" kind of targeting. Nothing like that can be found on my profile. No mutual project with others, no controversial info in bio nor repos.
@tripplehelix @lumiworx @Codeberg
@dpnash @tripplehelix @Codeberg ... it may very well be a combination, or and either/or. Whatever they can point to and say you're "one of _those_ people". In that case, I figure I'm in good company.
@dpnash @tripplehelix @Codeberg ... and since it matters... #ThankYou #Codeburg.
@Codeberg That's awful :(
@Codeberg I haven't noticed anything. But thanks!
@Codeberg Is that why the status page reports unavailability again or is it still the attack having a strain on your systems?
@Codeberg
I can recommend https://cloudns.net/ their speed and redundancy is very very good
@as9136
@Codeberg@social.anoxinon.de
Out of coursity, have you considered hosting your own dns, potentially with some additional replicas outside if your network?
I would be happy to help with that however and whenever I can.
@as9136@as9136.social
@minecraftchest1
We have considered this, but wanted to save the work when possible.
@Codeberg oh, you hate namesilo? chuckles hiiiiiii
@Codeberg@social.anoxinon.de @dns@donotsta.re servfail is more speedy than glauca hexdns
@frelsisbaratta Thank you. The situation seems to be under control now, but we saved a bookmark in case we face stronger attacks in the future.