You cannot look at ping results in isolation. Its like taking temprature and declaring you have malaria or asking in the estate if somebody else has high fever. Look at other symptoms like traceroute results and utilisation of your link or errors on ur local interface. On 07/11/2009, Job Muriuki <muriukin@gmail.com> wrote:
Anyone from accesskenya on the list? You can shed some light on whats wrong with the service around jogoo road near eastleigh. The service has been poor for close to two weeks now. look at the ping test from 30 min ago
~ $ ping 4.2.2.2 PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data. 64 bytes from 4.2.2.2: icmp_seq=1 ttl=247 time=1068 ms 64 bytes from 4.2.2.2: icmp_seq=3 ttl=247 time=1218 ms 64 bytes from 4.2.2.2: icmp_seq=4 ttl=247 time=1158 ms 64 bytes from 4.2.2.2: icmp_seq=5 ttl=247 time=1257 ms 64 bytes from 4.2.2.2: icmp_seq=6 ttl=247 time=1231 ms 64 bytes from 4.2.2.2: icmp_seq=7 ttl=247 time=1231 ms 64 bytes from 4.2.2.2: icmp_seq=8 ttl=247 time=1240 ms 64 bytes from 4.2.2.2: icmp_seq=9 ttl=247 time=1209 ms 64 bytes from 4.2.2.2: icmp_seq=10 ttl=247 time=1264 ms 64 bytes from 4.2.2.2: icmp_seq=11 ttl=247 time=1208 ms 64 bytes from 4.2.2.2: icmp_seq=12 ttl=247 time=1128 ms 64 bytes from 4.2.2.2: icmp_seq=14 ttl=247 time=1251 ms 64 bytes from 4.2.2.2: icmp_seq=16 ttl=247 time=1266 ms 64 bytes from 4.2.2.2: icmp_seq=17 ttl=247 time=1174 ms 64 bytes from 4.2.2.2: icmp_seq=18 ttl=247 time=1259 ms 64 bytes from 4.2.2.2: icmp_seq=19 ttl=247 time=1147 ms 64 bytes from 4.2.2.2: icmp_seq=21 ttl=247 time=1036 ms 64 bytes from 4.2.2.2: icmp_seq=22 ttl=247 time=853 ms 64 bytes from 4.2.2.2: icmp_seq=23 ttl=247 time=808 ms 64 bytes from 4.2.2.2: icmp_seq=24 ttl=247 time=918 ms ^C --- 4.2.2.2 ping statistics --- 25 packets transmitted, 20 received, 20% packet loss, time 24025ms rtt min/avg/max/mdev = 808.607/1146.697/1266.385/136.449 ms, pipe 2
Anyone experiencing similar issues on access kenya link.
-- Sent from my mobile device