Quote Originally Posted by Shinjo View Post
i would also rather look at the ip 195.82.50.230 with the high ms number.
Sorry, but you're misreading the data. A high ping there isn't necessarily a problem, especially as the node after it is just fine.

All we really care about is the latency that you get with the destination (195.82.50.9) which is 10-13 ms in your example. The main job of that 195.82.50.230 router is to forward the packets to the next node as quickly as possibly and it's doing that, because you only have that 10-13 ms.

However when you do a traceroute it sends a ping to each node along the way. Some nodes won't even respond to pings (but they still forward packets as they're supposed to) and others such as 195.82.50.230 don't prioritise ping replies so although you do get a reply, it's just delayed because it's focusing on forwarding the packets.

A traceroute is good for showing the path and seeing where the latency increases, but a single high node should be ignored, if subsequent nodes are still low because it means that node isn't causing any delays, only that it is slow to reply to pings.

I hope this helps to make sense?