Hi everyone!
-
Hi everyone! We are still fighting with an ongoing DDoS attack against our service on the network level. We do not yet have any ETA on recovery time, as we're still investigating different mitigation strategies.
As always, we are very grateful for your support and patience.
@codebergstatus fingers crossed for you
-
Hi everyone! We are still fighting with an ongoing DDoS attack against our service on the network level. We do not yet have any ETA on recovery time, as we're still investigating different mitigation strategies.
As always, we are very grateful for your support and patience.
@codebergstatus Good luck and thanks for all the help hosting my foss games!
-
Just a note to say I appreciate your efforts. I wouldn't host my code anywhere else.
-
@codebergstatus I bestow the curse of a never ending wipe on the attackers.
"May your arse forever itch and your arms be too short to reach."
-
Hi everyone! We are still fighting with an ongoing DDoS attack against our service on the network level. We do not yet have any ETA on recovery time, as we're still investigating different mitigation strategies.
As always, we are very grateful for your support and patience.
@codebergstatus already said it, but i find strange those attack started when high profile project moved out github.
Would learn microsoft is behind it i would not be surprised, when we see all illegal shit they already did in the pase to kill competition
-
Hi everyone! We are still fighting with an ongoing DDoS attack against our service on the network level. We do not yet have any ETA on recovery time, as we're still investigating different mitigation strategies.
As always, we are very grateful for your support and patience.
@codebergstatus maybe codeberg can (when and if) federation will be ready, to let user federate, so it make more difficult to anyone to actually ddos codeberg.
as biggest project would host themselve and federate, making codeberg a less attractive target. -
Hi everyone! We are still fighting with an ongoing DDoS attack against our service on the network level. We do not yet have any ETA on recovery time, as we're still investigating different mitigation strategies.
As always, we are very grateful for your support and patience.
@codebergstatus Oh god not again
-
Hi everyone! We are still fighting with an ongoing DDoS attack against our service on the network level. We do not yet have any ETA on recovery time, as we're still investigating different mitigation strategies.
As always, we are very grateful for your support and patience.
@codebergstatus good work on getting ssh access back up.
-
Hi everyone! We are still fighting with an ongoing DDoS attack against our service on the network level. We do not yet have any ETA on recovery time, as we're still investigating different mitigation strategies.
As always, we are very grateful for your support and patience.
We were able to restore IPv4 and IPv6 connectivity. Performance is still not optimal, and connections are occasionally dropping. We've taken measures to try and maintain uptime overnight (with a certain probability).
Routes protected by iocaine (crawler protection) may return 503 errors. Currently, it appears that these packets are also occasionally being lost.
It's 2:30am, and we require a good night's sleep before we can look into this further.
-
We were able to restore IPv4 and IPv6 connectivity. Performance is still not optimal, and connections are occasionally dropping. We've taken measures to try and maintain uptime overnight (with a certain probability).
Routes protected by iocaine (crawler protection) may return 503 errors. Currently, it appears that these packets are also occasionally being lost.
It's 2:30am, and we require a good night's sleep before we can look into this further.
@codebergstatus thanks for the hard work
Have a good and refreshing night of sleep 🥰 -
@codebergstatus This is low, even for GitHub.
-
We were able to restore IPv4 and IPv6 connectivity. Performance is still not optimal, and connections are occasionally dropping. We've taken measures to try and maintain uptime overnight (with a certain probability).
Routes protected by iocaine (crawler protection) may return 503 errors. Currently, it appears that these packets are also occasionally being lost.
It's 2:30am, and we require a good night's sleep before we can look into this further.
@codebergstatus Thank you for the overtime work. Much appreciated.
-
We were able to restore IPv4 and IPv6 connectivity. Performance is still not optimal, and connections are occasionally dropping. We've taken measures to try and maintain uptime overnight (with a certain probability).
Routes protected by iocaine (crawler protection) may return 503 errors. Currently, it appears that these packets are also occasionally being lost.
It's 2:30am, and we require a good night's sleep before we can look into this further.
@codebergstatus well done! Much appreciated!
-
We were able to restore IPv4 and IPv6 connectivity. Performance is still not optimal, and connections are occasionally dropping. We've taken measures to try and maintain uptime overnight (with a certain probability).
Routes protected by iocaine (crawler protection) may return 503 errors. Currently, it appears that these packets are also occasionally being lost.
It's 2:30am, and we require a good night's sleep before we can look into this further.
@codebergstatus Thanks!
-
We were able to restore IPv4 and IPv6 connectivity. Performance is still not optimal, and connections are occasionally dropping. We've taken measures to try and maintain uptime overnight (with a certain probability).
Routes protected by iocaine (crawler protection) may return 503 errors. Currently, it appears that these packets are also occasionally being lost.
It's 2:30am, and we require a good night's sleep before we can look into this further.
@codebergstatus
Well done and thank you. -
Hi everyone! We are still fighting with an ongoing DDoS attack against our service on the network level. We do not yet have any ETA on recovery time, as we're still investigating different mitigation strategies.
As always, we are very grateful for your support and patience.
@codebergstatus@social.anoxinon.de best wishes, sounds rough out there
-
We were able to restore IPv4 and IPv6 connectivity. Performance is still not optimal, and connections are occasionally dropping. We've taken measures to try and maintain uptime overnight (with a certain probability).
Routes protected by iocaine (crawler protection) may return 503 errors. Currently, it appears that these packets are also occasionally being lost.
It's 2:30am, and we require a good night's sleep before we can look into this further.
@codebergstatus thank you!!
-
Hi everyone! We are still fighting with an ongoing DDoS attack against our service on the network level. We do not yet have any ETA on recovery time, as we're still investigating different mitigation strategies.
As always, we are very grateful for your support and patience.
@codebergstatus Annoying.
Why not limiting access to users only when getting attacked? -
@codebergstatus I don't understand it; you're probably not causing relevant financial loss to anyone, so why pay for the attack?
Anyway I wish you peace of mind while dealing with the crap.@vojta001 @codebergstatus M$ spent a big buck to own the community they are currently losing.
-
Hi everyone! We are still fighting with an ongoing DDoS attack against our service on the network level. We do not yet have any ETA on recovery time, as we're still investigating different mitigation strategies.
As always, we are very grateful for your support and patience.
@codebergstatus Thanks a lot for providing this awesome service! May future attacks go towards bad actors instead of those working on a better world!
