A route that I commonly trace now has major changes every time it is traced (only 6 out of 14 or 16 hops stay the same each time, going through entirely different networks with different numbers of hops), so I set an IP mask of ALL. This does not seem to ignore route changes, but does change the behavior so that instead of updating the list of hops, it redraws them all (like when you stop and resume the trace).<br><br>Othe anomalies that I have noticed since the route changes became so major is that random timeline graphs appear (I checked pingplotter.ini and there was no matching entry there), and node names change (I assume both these are a timing thing - by the time pingplotter gets the name, the route has changed and hop 15 is no longer the same address)<br><br>