tracert forums.anandtech.com
Tracing route to dra7275p949yj.cloudfront.net [13.249.184.110]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms RT-AX3000-FEB8 [192.168.50.1]
2 7 ms 7 ms 8 ms XX.XX.64.49
3 7 ms 8 ms 8 ms XX.XX.158.73
4 8 ms 9 ms 8 ms XX.XX.157.149
5 10 ms 9 ms 9 ms be-65-ar01.needham.ma.boston.comcast.net [68.85.69.165]
6 11 ms 14 ms 11 ms be-1003-pe02.onesummer.ma.ibone.comcast.net [68.86.90.173]
7 10 ms 9 ms 9 ms 66.208.228.190
8 * * * Request timed out.
9 14 ms 15 ms 15 ms 150.222.71.79
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 14 ms 14 ms 20 ms server-13-249-184-110.bos50.r.cloudfront.net [13.249.184.110]
Trace complete.
That is normal. Even trying to trace google will give you that. Some ISP routers, servers, and gateways are configured to not respond back to ICMP or traceroute messages/requests. This is an intended safety measure.Tracing the route, I get 5 timeouts on unknown addresses while connecting to server-13-249-184-110.bos50.r.cloudfront.net (Boston) from Manchester NH. Bizarre.
Code:tracert forums.anandtech.com Tracing route to dra7275p949yj.cloudfront.net [13.249.184.110] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms RT-AX3000-FEB8 [192.168.50.1] 2 7 ms 7 ms 8 ms XX.XX.64.49 3 7 ms 8 ms 8 ms XX.XX.158.73 4 8 ms 9 ms 8 ms XX.XX.157.149 5 10 ms 9 ms 9 ms be-65-ar01.needham.ma.boston.comcast.net [68.85.69.165] 6 11 ms 14 ms 11 ms be-1003-pe02.onesummer.ma.ibone.comcast.net [68.86.90.173] 7 10 ms 9 ms 9 ms 66.208.228.190 8 * * * Request timed out. 9 14 ms 15 ms 15 ms 150.222.71.79 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 14 ms 14 ms 20 ms server-13-249-184-110.bos50.r.cloudfront.net [13.249.184.110] Trace complete.
Brilliant posts router's public address on an internet forum
FTFYSeems better now though. May we need to post in this thread towakefeed the hamsters?