4 ms·
ISPs have a very decentralized network, that is, they have routers in a lot of places. If you sum up the available traffic capacity, you get a number that's fa
by perlgeek 5y ago
ISPs have a very decentralized network, that is, they have routers in a lot of places.
If you sum up the available traffic capacity, you get a number that's far bigger than 250 Gbit/s.
But that's not the right comparison to make. Much of that DDoS traffic goes through multiple of the ISP's routers, and if you're doing just a numbers comparison, you'd have to multiply the attack rate by the (average) number of hops.
But things are even more complicated in reality: many smaller links will have only 10Gbit/s or 20Gbit/s or 40Gbit/s capacity (or maybe even 1G), and saturating them not only causes increased latency, but also routing the traffic around causes more overall load on the network.
Then there are management systems behind firewalls, and if you DDoS them, it's typically the firewalls that give out first.
Finally, customers don't get the full throughput internally available to an ISP; if you DDoS a customer's IP, their link will be saturated, even if the ISP itself has plenty to spare.
(Not a network engineer myself, but working closely with some).
- Groxx 5y agoWouldn't that all be true of normal web traffic too, presumably already capable of rates beyond 250Gbps? Though they may not have that much free headroom on top of normal traffic.
- oars 5y agoSo in the case where the attackers are aiming their traffic at one of the ISP's routers to saturate a link, how do they get the IP address/domain name of this router?
- perlgeek 5y agoTraceroutes. Peering information is also often public. More sinister options like insider information or leaked/exfiltrated network plans are also an option, but usually you get pretty far with standard network diagnostic tools.