Atlas traceroutes to 128.0.0.1 - Last Working Hop

Between 14-Dec-2011 00:00 UTC to 21-Dec-2011 UTC a total of 1110 unique
Atlas
probes conducted traceroutes to 128.0.0.1. 441 probes had one or more of these traceroutes failing. 302 out of the 441 never had succes tracing to 128.0.0.1 in this period.

To exclude problems which are not related to 128.0/16 we also performed traceroutes to 84.205.83.1, the pingable target in the RIS
De-bogon
anchor prefix 84.205.83/24. Because both 128.0/21 and the anchor prefix are announced from the same RIS route collector, it's fair to assume the probes who can reach 84.205.83.1 should also be able to complete a traceroute to 128.0.0.1. In the 7 day period from 14 to 21 december, 49 probes did not succeed with traceroutes to 84.205.83.1; these probes are excluded from further analysis.

The table lists the IP address and associated origin AS (as found in
RIS
) for the last working hop in traceroutes which failed to reach the 128.0.0.1 target. IP addresses in private address space (RFC1918) are not included in the table because it is less obvious where in the net the traceroute starts failing.

The table below lists the results of all traceoutes from RIPE Atlas probes between 5 and 9 December 2011 which failed to reach 128.0.0.1. For each trace, the IP of the last responsive hop is listed. In most cases traffic was blackholed after the last hop; network or host unreachable ICMP error messages were received on only a small percentage of the traces.

The IP addresses of the last hops were mapped to origin AS numbers with the
RISwhois
tool. Given an IP number, this find the best matching prefix in the routing tables collected by RIS.

The RIPE NCC uses cookies. Some of these cookies may have been set already. More information about our cookies can be found in our privacy policy. You can accept our cookies either by clicking here or by continuing to use the site.