Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
New Member

Diff. between traceroutes and pings

While running a basic ping to data center site, i get full pings not delays,


Reply from bytes=32 time=35ms

Reply from bytes=32 time=35ms

however when i run a traceroute, i get request timeouts but the nexthop, i will get a response time of 35 ms-so it kinda looks like this


2. * * * Request time out

3 * * * Request time out

4. 35 ms

5 * * * Request time out


could the only reason the be happeing are firewalls?

Hall of Fame Super Bronze

Re: Diff. between traceroutes and pings

Intermediate devices aren't responding to ICMPs either because they are blocking it (Firewalls) or they/or/you don't have a route to you/or/them.

On a traceroute, every transit device will respond back to you with an ICMP while with a ping, only the destination device need to respond.




Re: Diff. between traceroutes and pings


PING where the request is sent between the source and destination and the response is just seen interms of Reply.

The Devices behind the scenes are hidden in the Output. So only the Destination device Reply the Query.

Int Traceroute, every device has to respond to the ICMP Request in the path to reach the Destination.

Hope this Helps. Do Rate all HELPFUL POSTS

Best Regards,

Guru Prasad R

Re: Diff. between traceroutes and pings

In addition to the already mentioned reasons, another instance when RTO is reflected in traceroute is when the intermediate device is unmanaged or dont have IP.

Cisco Employee

Re: Diff. between traceroutes and pings

Hi Narayana,

As you mentioned when the intermediate device does not have an ip or unmanaged it may retuen RTO but is it true that any device which does not have an ip will be considered as a hop by traceroute, I doubt!!



New Member

Re: Diff. between traceroutes and pings

since I am using a VPN tunnel to my destination- I can assume the devices that are not responding are my ISP's?

Hall of Fame Super Bronze

Re: Diff. between traceroutes and pings

If you have a VPN, ISP's devices won't be shown in the path. A VPN makes the end-to-end connection look like a directly connected network while having multiple devices in the path.

Since you mentioned VPN, perhaps the hops that aren't replying are the tunnel interfaces from those VPN devices. Often, you don't want to advertise tunnel interfaces into your global routing.




CreatePlease to create content