Stanford University seal SLAC logo, click here to learn more about SLAC

traceroute from 207.98.65.105 (ptck-perf1.nero.net) to 54.210.223.150 (ec2-54-210-223-150.compute-1.amazonaws.com) for 54.210.223.150

CGI script maintainer: Les Cottrell, SLAC. Script version 7.0, 7/30/2016, Les Cottrell.
Download perl source code.
To perform a traceroute/ping/tracepath function from ptck-perf1.nero.net 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.
Enter target name or address: then push 'Enter' key.
Lookup: domain name | Locating a Host | visual traceroute | Find AS's between hosts | 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 ptck-perf1.nero.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(traceroute -m 30 -q 3 54.210.223.150 140)
traceroute to 54.210.223.150 (54.210.223.150), 30 hops max, 140 byte packets
 1  ptck-noc-gw.nero.net (207.98.65.97)  1.228 ms  1.354 ms  1.628 ms
 2  ptck-p1-gw.nero.net (207.98.64.156)  8.280 ms  8.266 ms  8.248 ms
 3  ptck-pe2-gw.nero.net (207.98.64.82)  0.147 ms  0.155 ms ptck-pe1-gw.nero.net (207.98.64.78)  0.456 ms
 4  ptck-pe1-gw.nero.net (199.165.177.4)  0.452 ms ptck-pe2-gw.nero.net (199.165.177.6)  0.204 ms  0.214 ms
 5  hundredge-0-0-0-24.701.core1.port.net.internet2.edu (198.71.45.218)  0.991 ms ptck-p1-gw.nero.net (207.98.64.83)  8.021 ms ptck-p2-gw.nero.net (207.98.64.85)  2.121 ms
 6  ptck-pe1-gw.nero.net (199.165.177.4)  0.507 ms  0.468 ms  0.459 ms
 7  hundredge-0-0-0-24.701.core1.port.net.internet2.edu (198.71.45.218)  2.751 ms  2.739 ms  2.555 ms
 8  fourhundredge-0-0-0-1.4079.core2.seat.net.internet2.edu (163.253.1.231)  54.266 ms * *
 9  fourhundredge-0-0-0-16.4079.core1.seat.net.internet2.edu (163.253.2.54)  53.246 ms fourhundredge-0-0-0-18.4079.core1.seat.net.internet2.edu (163.253.2.50)  52.864 ms fourhundredge-0-0-0-17.4079.core1.seat.net.internet2.edu (163.253.2.52)  52.805 ms
10  fourhundredge-0-0-0-0.4079.core1.kans.net.internet2.edu (163.253.1.243)  54.721 ms * *
11  fourhundredge-0-0-0-0.4079.core1.denv.net.internet2.edu (163.253.1.170)  53.898 ms  53.846 ms *
12  fourhundredge-0-0-0-3.4079.core2.eqch.net.internet2.edu (163.253.2.19)  55.303 ms fourhundredge-0-0-0-0.4079.core1.kans.net.internet2.edu (163.253.1.243)  53.966 ms  53.982 ms
13  fourhundredge-0-0-0-50.4079.agg1.eqch.net.internet2.edu (163.253.1.221)  54.333 ms fourhundredge-0-0-0-3.4079.core2.chic.net.internet2.edu (163.253.1.244)  54.153 ms *
14  fourhundredge-0-0-0-3.4079.core2.eqch.net.internet2.edu (163.253.2.19)  53.867 ms 99.82.179.50 (99.82.179.50)  51.921 ms  51.955 ms
15  52.93.249.131 (52.93.249.131)  52.841 ms  52.184 ms fourhundredge-0-0-0-50.4079.agg1.eqch.net.internet2.edu (163.253.1.221)  53.327 ms
16  52.95.62.35 (52.95.62.35)  51.747 ms 150.222.212.55 (150.222.212.55)  51.612 ms 150.222.212.39 (150.222.212.39)  51.690 ms
17  52.93.249.105 (52.93.249.105)  52.743 ms * *
18  52.95.62.31 (52.95.62.31)  53.060 ms * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * 52.93.28.190 (52.93.28.190)  70.678 ms *
24  * * *
25  52.93.28.188 (52.93.28.188)  67.965 ms * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
traceroute -m 30 -q 3 54.210.223.150 140 took 15secs. Total time=15secs. user=apache