Here's what appears to be strictly a "cosmetic" bug...<br><br>When Ping Plotter reaches the last hop of a trace, it continues the trace, adding the last hop as another hop again and again, until the next pass starts. It then clears out those additional hops during the next pass (except for one occasionally, which is cleared at the *next* pass).<br><br>You may not see this if your "Time interval between hop traces" is high enough and the route your tracing is long the next pass may have already started before the last hop was reached. Ping Plotter stops adding duplicate last-hops once the next pass has started.<br><br>A good way to duplicate this is to trace the localhost address, (which is your own machine).<br><br>