If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. /bill Neca eos omnes. Deus suos agnoscet.
On 2014.05.27. 20:28, manning bill wrote:
If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following:
2001:500:84::b
Thanks in advance.
/bill Neca eos omnes. Deus suos agnoscet.
There should be a tool for this kind of thing! :-) https://atlas.ripe.net/atlas/udm.html?msm_id=1666831 or just the data (~1MB): https://atlas.ripe.net/api/v1/measurement/1666831/result/ Cheers, Robert
On 27.05.14 20:45 , Robert Kisteleki wrote:
On 2014.05.27. 20:28, manning bill wrote:
If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following:
2001:500:84::b
Thanks in advance.
/bill Neca eos omnes. Deus suos agnoscet.
There should be a tool for this kind of thing! :-)
If you analyse these results with using http://labske.org:8765/lara-traceroute/ you discover that local connectivity is through HE and Los Nettos. Further you can see that about half the HE packets are sent via Los Nettos, so the amount of redundancy that local traffic distribution among upstreams may suggest is not really there. If you like we can run this again with more probes. Of course you can also just get an account and run it yourself.... Daniel
On 28.05.14 8:55 , Daniel Karrenberg wrote:
... you discover that local connectivity is through HE and Los Nettos. ....
Ouch! I just got hit by my own wrong default of excluding hops with no response. There is no direct link to HE evident from the traceroutes. I wish ICMP "TTL Exceeded" responses were more reliable ... Correct graph with * hops included. Daniel
If you wouldn't mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. traceroute6 to 2001:500:84::b (2001:500:84::b) from 2a04:b900::1:0:0:15, 64 hops max, 12 byte packets 1 office.bijgepunt.nlnetlabs.nl 0.333 ms 0.314 ms 0.308 ms 2 2a02:d28:5580:e:1000::245 0.589 ms 0.611 ms 0.507 ms 3 eth1-1.core1.ams1.nl.as5580.net 0.554 ms 0.549 ms 0.536 ms 4 eth1-8.r1.ams2.nl.as5580.net 0.694 ms 13.099 ms 4.514 ms 5 30gigabitethernet1-3.core1.ams1.he.net 8.437 ms 1.450 ms 1.651 ms 6 100ge9-1.core1.lon2.he.net 17.578 ms 7.245 ms 17.896 ms 7 100ge1-1.core1.nyc4.he.net 86.636 ms 82.937 ms 103.756 ms 8 10ge10-3.core1.lax1.he.net 159.165 ms 164.547 ms 153.020 ms 9 10ge1-3.core1.lax2.he.net 158.396 ms 153.472 ms 152.610 ms 10 2001:504:13::210:43 153.222 ms 154.124 ms 153.499 ms 11 2001:1878::181:177 153.629 ms 153.891 ms 153.103 ms 12 2001:500:84::b 153.426 ms 153.167 ms 152.977 ms
On 5/27/14, 8:28 PM, manning bill wrote:
If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following:
2001:500:84::b
hi, first choice is ripe atlas, as already suggested. btw, find here attached results obtained via ring.nlnog.net -- antonio
participants (5)
-
Antonio Prado -
Daniel Karrenberg -
Jaap Akkerhuis -
manning bill -
Robert Kisteleki