tracepath from 184.108.40.206 (iiap1.perfsonar.asnet.am) to 220.127.116.11 (ec2-3-237-178-91.compute-1.amazonaws.com) for 18.104.22.168CGI script maintainer: Les Cottrell, SLAC. Script version 6.51, 9/15/2014, Les Cottrell.
Download perl source code.
To perform a traceroute/ping/tracepath function from iiap1.perfsonar.asnet.am to the target, enter the desired target host.domain (e.g. www.yahoo.com) or Internet address (e.g. 22.214.171.124) in the box below. Note the fucntion is performed for the target's resolved Internet address. Lookup: domain name | Locating a Host | visual traceroute | Find AS's between hosts | Find AS of a host | contacting someone
|Related web sites|
What is my IP address?
Please note that traceroutes can appear similar
to port scans. If you see a suspected port scan alert,
for example from your firewall, with
a series of ports in the range 33434 - 33465, coming
from iiap1.perfsonar.asnet.am it is probably a reverse traceroute from our
web based reverse traceroute server. Please do NOT report this to
us, it will almost certainly be a waste of both of our times.
For more on this see|
Traceroute security issues.
Executing exec(tracepath 126.96.36.199) 1?: [LOCALHOST] pmtu 1500 1: iiap-grid-gw.grid-core-10g-mt.asnet.am (188.8.131.52) 0.987ms 1: iiap-grid-gw.grid-core-10g-mt.asnet.am (184.108.40.206) 1.176ms 2: 72-3-iiap-grid-to-jun-sw-rt.asnet.am (220.127.116.11) 0.356ms 3: 72-3-iiap-grid-to-72-1-pr-grid.asnet.am (18.104.22.168) 0.538ms 4: geant-mt-2-ps-pres.asnet.am (22.214.171.124) 0.838ms 5: no reply 6: 126.96.36.199 (188.8.131.52) 85.682ms asymm 12 7: 184.108.40.206 (220.127.116.11) 160.059ms asymm 17 8: no reply 9: ash-bb2-link.ip.twelve99.net (18.104.22.168) 172.743ms asymm 19 10: ash-b2-link.ip.twelve99.net (22.214.171.124) 160.093ms asymm 14 11: vadata-ic333118-ash-b2.ip.twelve99-cust.net (126.96.36.199) 159.760ms asymm 16 12: no reply 13: no reply 14: 188.8.131.52 (184.108.40.206) 152.609ms asymm 16 15: