> But this is a rather entirely different case. In this case, it seems that > one very notable peering that -did- in fact exist, between AS205869 and > AS6939, was not reported at all on the bgp.he.net page linked to above.
HE usually learn these hijacked routes from IX peering and route servers. bgp.he.net tends not to report on IX peering. To their credit, HE have an extremely open peering policy. To their detriment, this means their customers see the large majority of hijacked routes due to poor filtering on many IX route servers.
