tracepath from 126.96.36.199 (maddash.bc.net) to 188.8.131.52 (ec2-3-214-224-224.compute-1.amazonaws.com) for 184.108.40.206CGI 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 maddash.bc.net to the target, enter the desired target host.domain (e.g. www.yahoo.com) or Internet address (e.g. 220.127.116.11) 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 maddash.bc.net 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 18.104.22.168) 1?: [LOCALHOST] pmtu 1500 1: gateway 0.167ms 1: gateway 0.214ms 2: 22.214.171.124 0.464ms 3: ix-cr1-cu-all.kmlp8.bc.net 0.663ms 4: cr1-100g-ix456ae9.vncv1.bc.net 6.529ms 5: vncv1rtr2.canarie.ca 58.092ms asymm 18 6: no reply 7: no reply 8: no reply 9: no reply 10: no reply 11: no reply 12: no reply 13: 126.96.36.199 95.314ms asymm 26 14: 188.8.131.52 89.063ms asymm 30 15: 184.108.40.206 84.767ms asymm 29 16: no reply 17: no reply 18: no reply 19: no reply 20: 220.127.116.11 84.406ms asymm 24 21: no reply 22: no reply 23: no reply 24: no reply 25: no reply 26: 18.104.22.168 83.902ms asymm 20 27: no reply 28: no reply 29: no reply 30: no reply Too many hops: pmtu 1500 Resume: pmtu 1500