AS 5547 currently leaks 80.0.0.0/8 and 2.0.0.0/8 (IANA unassigned). As it appears, only Oregon-IX (of the 6-7 route-servers I looked at) seems to accept a larger number of routes from that AS right now, many seem to be filtering this AS at this point. Network Next Hop Metric LocPrf Weight Path *> 2.0.0.0 167.142.3.6 0 5056 701 3491 20485 5547 ? *> 80.0.0.0 167.142.3.6 0 5056 701 3491 20485 5547 ? I think someone should work on AS 3491 (cais.net) with a mallet for running no inbound prefix filtering with AS 20485 (transtelecom.net, a russian ISP, one that can apparently be trusted even less than CAIS) - a situation that calls for instant de-peering, if you ask me. Also: 2.0.0.0/8 from AS: 5547 (upstreams: 20485) 80.0.0.0/8 from AS: 5547 (upstreams: 20485) 195.161.13.0/24 from AS: 5547 (upstreams: 20485) 195.161.19.0/24 from AS: 5547 (upstreams: 20485) 195.161.68.0/24 from AS: 5547 (upstreams: 20485) 195.161.236.0/24 from AS: 5547 (upstreams: 20485) 195.161.236.0/22 from AS: 5547 (upstreams: 20485) 195.161.237.0/24 from AS: 5547 (upstreams: 20485) 195.161.238.0/24 from AS: 5547 (upstreams: 20485) 195.208.8.0/24 from AS: 5547 (upstreams: 20485) 195.208.8.0/21 from AS: 5547 (upstreams: 20485) 195.208.10.0/24 from AS: 5547 (upstreams: 20485) 195.208.11.0/24 from AS: 5547 (upstreams: 20485) 195.208.12.0/24 from AS: 5547 (upstreams: 20485) 195.208.13.0/24 from AS: 5547 (upstreams: 20485) 195.208.14.0/24 from AS: 5547 (upstreams: 20485) 213.59.129.0/24 from AS: 5547 (upstreams: 20485) 213.59.130.0/24 from AS: 5547 (upstreams: 20485) 213.59.131.0/24 from AS: 5547 (upstreams: 20485) 213.59.132.0/24 from AS: 5547 (upstreams: 20485) 213.59.133.0/24 from AS: 5547 (upstreams: 20485) 213.59.134.0/24 from AS: 5547 (upstreams: 20485) 213.59.135.0/24 from AS: 5547 (upstreams: 20485) 213.59.234.0/24 from AS: 5547 (upstreams: 20485) 217.107.38.0/24 from AS: 5547 (upstreams: 20485) 217.107.39.0/24 from AS: 5547 (upstreams: 20485)
participants (1)
-
Kai Schlichting