For a week or so, my speeds were AWESOME. I was averaging 130+Mbps on my 150Mbps service.
Then, my wife called me and said the service was out, and she noticed several maintenance trucks around the area.
Ever since they "fixed" whatever the heck they fixed, I've had poor service, iffy speeds.
break19@blackbeast ~ % ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.311 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.301 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.301 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.294 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.312 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.380 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=0.307 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.310 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=0.302 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=0.325 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=0.318 ms
^C
--- 192.168.0.1 ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 9997ms
rtt min/avg/max/mdev = 0.294/0.314/0.380/0.029 ms
break19@blackbeast ~ % ping 10.188.190.1
PING 10.188.190.1 (10.188.190.1) 56(84) bytes of data.
64 bytes from 10.188.190.1: icmp_seq=1 ttl=254 time=8.31 ms
64 bytes from 10.188.190.1: icmp_seq=2 ttl=254 time=22.3 ms
64 bytes from 10.188.190.1: icmp_seq=3 ttl=254 time=12.9 ms
64 bytes from 10.188.190.1: icmp_seq=4 ttl=254 time=7.17 ms
64 bytes from 10.188.190.1: icmp_seq=5 ttl=254 time=24.1 ms
64 bytes from 10.188.190.1: icmp_seq=6 ttl=254 time=7.06 ms
64 bytes from 10.188.190.1: icmp_seq=9 ttl=254 time=7.85 ms
64 bytes from 10.188.190.1: icmp_seq=10 ttl=254 time=7.04 ms
64 bytes from 10.188.190.1: icmp_seq=12 ttl=254 time=7.28 ms
64 bytes from 10.188.190.1: icmp_seq=13 ttl=254 time=8.04 ms
64 bytes from 10.188.190.1: icmp_seq=14 ttl=254 time=28.6 ms
64 bytes from 10.188.190.1: icmp_seq=15 ttl=254 time=7.94 ms
64 bytes from 10.188.190.1: icmp_seq=16 ttl=254 time=6.74 ms
64 bytes from 10.188.190.1: icmp_seq=17 ttl=254 time=20.1 ms
64 bytes from 10.188.190.1: icmp_seq=18 ttl=254 time=8.07 ms
64 bytes from 10.188.190.1: icmp_seq=19 ttl=254 time=21.8 ms
64 bytes from 10.188.190.1: icmp_seq=21 ttl=254 time=19.9 ms
64 bytes from 10.188.190.1: icmp_seq=22 ttl=254 time=6.90 ms
64 bytes from 10.188.190.1: icmp_seq=24 ttl=254 time=8.24 ms
64 bytes from 10.188.190.1: icmp_seq=25 ttl=254 time=20.9 ms
64 bytes from 10.188.190.1: icmp_seq=26 ttl=254 time=8.20 ms
64 bytes from 10.188.190.1: icmp_seq=27 ttl=254 time=7.88 ms
64 bytes from 10.188.190.1: icmp_seq=28 ttl=254 time=8.65 ms
64 bytes from 10.188.190.1: icmp_seq=30 ttl=254 time=7.45 ms
64 bytes from 10.188.190.1: icmp_seq=31 ttl=254 time=8.07 ms
64 bytes from 10.188.190.1: icmp_seq=32 ttl=254 time=8.68 ms
64 bytes from 10.188.190.1: icmp_seq=33 ttl=254 time=7.65 ms
^C
--- 10.188.190.1 ping statistics ---
33 packets transmitted, 27 received, 18% packet loss, time 32058ms
rtt min/avg/max/mdev = 6.740/11.789/28.675/6.633 ms
--
18% packet loss to the default gateway? Seriously?? Notice the ping times to my own router? That's my network, which is obviously working just fine.
--
However, looking at the signal levels and the MER/SNR levels of the modem, it would appear that the plant-side of things is also A-OK. (I worked for you guys as a field tech for about 5 years, until just about 2 years ago, I know what to look for with regards to signal and noise levels)
↧