Hi everyone!
-
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!
-
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
more support
-
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 Sometimes it is ok to block the IP range of an entire country as a treat.
-
R relay@relay.infosec.exchange shared this topic
