2 ms·
From an ISP perspective this is really hard to hide. If somebody announces my /16 from Pakistan and traffic goes there, it's going to get noticed. Like the time
by walrus01 8y ago
From an ISP perspective this is really hard to hide. If somebody announces my /16 from Pakistan and traffic goes there, it's going to get noticed. Like the time PTCL broke YouTube...
You basically can't bgp hijack without breaking basic internet connectivity for the legit users of the IP space (where it is intended to be announced to peers and transits), so anything lasting more than 30 seconds will generate a huge flurry of phone calls and noc emails.
There are third party services you can pay, and software you can set up yourself to watch for bgp announcements for "your" Arin/ripe/apnic/whatever prefixes, and generate alerts based on that. Pretty common stuff with Linux based systems (FRR, etc) that can hold the entire global v4+v6 routing table in RAM and do quick analysis on it.
Google "bgp hijack", this is a well known issue in the ISP operational community. RPKI validation of announced routes and best common practices for what you accept from your bgp neighbors go a long way.