Что творится с провайдером?

0

0

не совсем по теме раздела, но жутко интересно, что ж творится такое... Никогда не видел такого.

[elf@lapotop (~)]$ ping -n google.com
PING google.com (64.233.167.99) 56(84) bytes of data.
64 bytes from 64.233.167.99: icmp_seq=1 ttl=239 time=230 ms
64 bytes from 64.233.167.99: icmp_seq=2 ttl=239 time=217 ms
64 bytes from 64.233.167.99: icmp_seq=1 ttl=239 time=2518 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=1 ttl=239 time=3638 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=1 ttl=239 time=7235 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=2 ttl=239 time=6273 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=1 ttl=239 time=9804 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=2 ttl=239 time=8887 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=1 ttl=239 time=10308 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=2 ttl=239 time=9309 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=1 ttl=239 time=12711 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=2 ttl=239 time=11749 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=1 ttl=239 time=15774 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=2 ttl=239 time=14799 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=1 ttl=239 time=22174 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=2 ttl=239 time=21324 ms (DUP!)
64 bytes from 64.233.167.99: icmp_seq=24 ttl=239 time=263 ms
64 bytes from 64.233.167.99: icmp_seq=25 ttl=239 time=300 ms
64 bytes from 64.233.167.99: icmp_seq=26 ttl=239 time=263 ms
64 bytes from 64.233.167.99: icmp_seq=27 ttl=239 time=203 ms
64 bytes from 64.233.167.99: icmp_seq=28 ttl=239 time=229 ms

Откуда столько dup'ов?