Tracert shows 2 hops request timed out

cwb1234

I have two hops request timed out can someone diagnose and this?

1 <1 ms <1 ms <1 ms 10.0.0.1
2 1 ms <1 ms <1 ms CR1000A.mynetworksettings.com [192.168.1.1]
3 6 ms 1 ms 3 ms lo0-100.NWRKNJ-VFTTP-333.verizon-gni.net [96.234.79.1]
4 4 ms 8 ms 6 ms G2-3-1-1.NYCMNY-LCR-21.verizon-gni.net [100.41.199.158]
5 * * * Request timed out.
6 * * * Request timed out.
7 7 ms 3 ms 3 ms ae2.3602.ear4.Newark1.net.lumen.tech [4.69.211.181]
8 5 ms 3 ms 3 ms sterling-fi.ear4.newark1.level3.net [4.28.184.166]
9 6 ms 3 ms 3 ms 104.193.251.251
10 6 ms 7 ms 7 ms 104.193.251.13

Capricorn1

Some routers won't respond to ICMP echo requests, though they will pass them forward to their destination. When this happens, the request times out at that node. Generally, that doesn't mean much in diagnosing network issues.

Not responding was considered more secure and a deterrent to ping-flood DDoS attacks. I used to not allow ping on any public-facing servers, but now I use ping rate limiting instead.

I'm not sure how you are issuing the tracert command, but I recommend looking into MTR utilities as well.