08-31-2018, 06:51 PM
I think the suggestions, especially from some of whom are called 'staff', here are lacking in technical detail by about 100% and it's quite sad.
There isn't anything you can do once the attackers have your address to stop the incoming bandwidth. If you shut your container down they can still attack you and cause grief on the provider's routers. Taking the ip address 'offline' has no effect either. The datacenter of your provider can null route your specific address at their edge but then they will be tanking the attack for you. Your address has to be nullrouted at all of the datacenter's upstreams too for there to be any reduction in load/bandwidth on someones routers.
Someone is getting charged for your traffic if your container is on or not. If the attacker is persistent enough that address will be ruined for a long while.
There isn't anything you can do once the attackers have your address to stop the incoming bandwidth. If you shut your container down they can still attack you and cause grief on the provider's routers. Taking the ip address 'offline' has no effect either. The datacenter of your provider can null route your specific address at their edge but then they will be tanking the attack for you. Your address has to be nullrouted at all of the datacenter's upstreams too for there to be any reduction in load/bandwidth on someones routers.
Someone is getting charged for your traffic if your container is on or not. If the attacker is persistent enough that address will be ruined for a long while.