tracepath from 184.108.40.206 (perfsonar.grena.ge) to 220.127.116.11 (ec2-3-236-239-91.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 perfsonar.grena.ge 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 perfsonar.grena.ge 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 1500 1: gateway 1249.697ms 2: 188.8.131.52 0.838ms 3: 184.108.40.206 20.554ms 4: 220.127.116.11 9.511ms 5: te0-2-0-1-5.agr41.fra03.atlas.cogentco.com 50.358ms 6: be3186.ccr41.fra03.atlas.cogentco.com 49.073ms 7: be2813.ccr41.ams03.atlas.cogentco.com 60.659ms 8: be12194.ccr41.lon13.atlas.cogentco.com 62.790ms 9: be2099.ccr31.bos01.atlas.cogentco.com 125.008ms 1: gateway 1038.763ms 10: 18.104.22.168 129.919ms 11: 22.214.171.124 132.654ms asymm 14 12: 126.96.36.199 125.082ms 13: 188.8.131.52 141.626ms asymm 26 14: no reply 15: no reply 16: no reply 17: no reply 18: 184.108.40.206 144.680ms asymm 20 19: no reply 20: no reply 21: no reply 22: no reply 23: no reply 24: no reply 25: no reply 26: no reply 27: no reply 28: no reply 29: 220.127.116.11 145.545ms asymm 15 30: no reply Too many hops: pmtu 1500 Resume: pmtu 1500