That's currently what I think is one of the most major shortcomings of Ping Plotter currenty - its inability to track/recover from route changes. Basically, once it gets a route, it just decides that route is correct - and keeps plugging in values. This means it has problems when the route has changed after a network failure - which is usually how network failures are recovered (by rerouting data packets).<br><br>I have the next release working with the ability to track changes. The problem is the user interface - how are these changes represented. I hope to get this handled pretty soon.<br><br>BTW, the latest beta (version 2.03.1 beta 4) handles *some* of these issues when the network comes back up with the same route - it should work correctly *most* of the time. It's still not right, though... <br><br>Thanks for the question - it's a good one!<br><br>Pete<br><br>