Regarding the new route changes detection: is there any way to detect a hop that is multi-homed or using load balancing? For example, our provider is using load-balancing on 4 T-1's between their POP (which we're connected to) and their backbone. Nearly every packet sent travels over a different T-1 on it's way out, making the "Route Changes" unusable. That one hop keeps changing because the addresses of the interfaces on each T-1 at their backbone is different.<br><br>My experience tells me that it would not be possible to detect such a thing without wrecking some real routing changes. So...would it be possible to have an "exception list", where the user could enter an IP address somewhere that tells PingPlotter to ignore changes at the hop after that address (but continue to monitor changes beyond there)?<br><br>Thanks for your time and brain-power. :-)<br><br>