tracepath from 184.108.40.206 (ps.sdsc.xsede.org) to 220.127.116.11 (ec2-44-210-21-70.compute-1.amazonaws.com) for 18.104.22.168CGI script maintainer: Les Cottrell, SLAC. Script version 7.7, 8/9/2018, Les Cottrell.
Download perl source code.
To perform a traceroute/ping/tracepath function from ps.sdsc.xsede.org 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 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 ps.sdsc.xsede.org 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(/bin/tracepath 126.96.36.199) 1?: [LOCALHOST] pmtu 9000 1: mystery-router-1.sdsc.edu 1.700ms 1: mystery-router-1.sdsc.edu 0.442ms 2: medusa-mx960.sdsc.edu 5.183ms 3: 188.8.131.52 0.556ms 4: dc-sdg-agg4--sdsc-100ge.cenic.net 0.703ms 5: dc-tus-agg8--sdg-agg4-300g.cenic.net 3.787ms asymm 6 6: dc-lax-agg8--tus-agg8-300g.cenic.net 3.912ms 7: 184.108.40.206 3.628ms pmtu 1500 7: no reply 8: no reply 9: no reply 10: no reply 11: no reply 12: no reply 13: no reply 14: