Why are the MTR times so extremely different? Why some addresses skipped? (image below)

SOLVED
MicJameson
Here to help

Why are the MTR times so extremely different? Why some addresses skipped? (image below)

Hello.

Device = MX64W

Please see image below. (MTR and traceroute taken immediately back to back)

Why are the ping times to same address so extremely different between MTR tool, and Traceroute?

Why are some IP addresses not listed in MTR?

Thank you!

 

MicJameson_0-1653919375102.png

 

1 ACCEPTED SOLUTION
RaphaelL
Kind of a big deal
Kind of a big deal

Traceroute is ICMP based , many hops on the Internet will process ICMP with a ultra low priority. MTR is often tcp/udp/icmp based and since they are both different , you will recevied different results.

 

Here is a great explanation : https://www.cloudflare.com/learning/network-layer/what-is-mtr/

View solution in original post

4 REPLIES 4
RaphaelL
Kind of a big deal
Kind of a big deal

Traceroute is ICMP based , many hops on the Internet will process ICMP with a ultra low priority. MTR is often tcp/udp/icmp based and since they are both different , you will recevied different results.

 

Here is a great explanation : https://www.cloudflare.com/learning/network-layer/what-is-mtr/

ww
Kind of a big deal
Kind of a big deal

Response times of both look around the same to me. Can you give a example

Compare the MTR times to the traceroute times. They are many seconds in difference. 

Though above poster seems to have provided solution-- the MTR uses many protocols, an also monitors flow over time before producing results.

ww
Kind of a big deal
Kind of a big deal

Its all in ms (millisecond)

For example 3rd Row is both 12.x ms

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels