wingnut771
Honorary Master
Possibly inherited from the exchange.
A ping to that hop will need to done to confirm any issues there.
As an example, here's an output I just ran. Shows packet loss, but when doing a ping directly to that hop it shows there is none.
Code:sudo mtr --report -n google.co.za HOST: Loss% Snt Last Avg Best Wrst StDev 1.|-- 192.168.1.2 0.0% 10 0.4 0.3 0.2 0.4 0.0 2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 3.|-- 169.1.5.105 20.0% 10 19.0 18.9 17.9 19.4 0.5 4.|-- 169.1.5.106 0.0% 10 18.1 19.1 18.1 20.4 0.7 5.|-- 169.1.5.128 0.0% 10 19.1 20.3 18.5 28.4 2.9 6.|-- 41.164.52.40 0.0% 10 18.7 19.4 18.2 22.1 1.1 7.|-- 172.18.1.162 0.0% 10 39.4 43.0 39.4 67.9 8.8 8.|-- 72.14.194.206 0.0% 10 41.1 41.6 40.2 47.6 2.1 9.|-- 72.14.237.239 0.0% 10 40.1 40.5 39.9 41.3 0.5 10.|-- 216.58.223.3 0.0% 10 40.5 40.5 39.6 41.2 0.5 ping -c 10 169.1.5.105 PING 169.1.5.105 (169.1.5.105): 56 data bytes 64 bytes from 169.1.5.105: icmp_seq=0 ttl=58 time=19.641 ms 64 bytes from 169.1.5.105: icmp_seq=1 ttl=58 time=18.763 ms 64 bytes from 169.1.5.105: icmp_seq=2 ttl=58 time=19.164 ms 64 bytes from 169.1.5.105: icmp_seq=3 ttl=58 time=18.271 ms 64 bytes from 169.1.5.105: icmp_seq=4 ttl=58 time=18.974 ms 64 bytes from 169.1.5.105: icmp_seq=5 ttl=58 time=18.413 ms 64 bytes from 169.1.5.105: icmp_seq=6 ttl=58 time=18.827 ms 64 bytes from 169.1.5.105: icmp_seq=7 ttl=58 time=18.337 ms 64 bytes from 169.1.5.105: icmp_seq=8 ttl=58 time=18.405 ms 64 bytes from 169.1.5.105: icmp_seq=9 ttl=58 time=18.504 ms --- 169.1.5.105 ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 18.271/18.730/19.641/0.414 ms
If it was at the exchange, you would see packet loss all the way through the hops, but anyway, you said there's nothing wrong.