![]() ![]() | tracepath from 192.108.47.12 (perfsonar2-de-kit.gridka.de) to 100.26.176.182 (ec2-100-26-176-182.compute-1.amazonaws.com) for 100.26.176.182CGI 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 perfsonar2-de-kit.gridka.de to the target, enter the desired target host.domain (e.g. www.yahoo.com) or Internet address (e.g. 137.138.28.228) 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 Traceroute servers, Monitoring tutorial, Internet monitoring 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 perfsonar2-de-kit.gridka.de 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 100.26.176.182) 1?: [LOCALHOST] pmtu 1500 1: def-gw-v471.gridka.de 0.711ms 1: def-gw-v471.gridka.de 0.651ms 2: tr-v740-rig2.gridka.de 0.981ms 3: tr-v706-rbocn1.gridka.de 0.610ms 4: tr-v1288-rbocs1.scc.kit.edu 11.054ms 5: kar-rz-a99-hu0-2-0-7.belwue.net 1.742ms 6: stu-nwz-a99-hu0-1-0-0.belwue.net 2.808ms 7: sgrt-b2-link.telia.net 2.481ms 8: ffm-bb2-link.telia.net 93.945ms asymm 14 9: prs-bb3-link.telia.net 94.896ms asymm 13 10: ash-bb3-link.telia.net 94.343ms 11: ash-b1-link.telia.net 94.890ms 12: vadata-ic-333121-ash-b1.c.telia.net 98.545ms asymm 13 13: