The only way this would be successful is if the "customer IP's" were spread accross separate networks, and the announcement for the attacked network was sent somewhere else.
Assigning customers across lots of IP's in the same /24 isn't going to do anything. A volumetric attack is still going to succeed there.
In this landscape of ever-dwindling portable IPv4 subnets, it's harder and harder to get a /24. You won't get an assignment if your justification is "to fight a DDoS."
Comments
The only way this would be successful is if the "customer IP's" were spread accross separate networks, and the announcement for the attacked network was sent somewhere else.
Assigning customers across lots of IP's in the same /24 isn't going to do anything. A volumetric attack is still going to succeed there.
In this landscape of ever-dwindling portable IPv4 subnets, it's harder and harder to get a /24. You won't get an assignment if your justification is "to fight a DDoS."
So namecheap would need a few different, separate IPv4 subnets.
Like the ones they already have?
http://bgp.he.net/AS22612#_prefixes
Good point. They should be spreading things around more.