packet latency and loss

What data do you have that shows the latency? Are you going by the Ping number in a game? Pingtest.net? A tracert? Could you post it?

Also, how are you connecting to the internet? Wired or wireless? What modem and router do you have?

I had to ping my work system,  I have a wired connection,  I have a box that says Arris, and one that says Ubee,  i dont know which one does what  here's the avg on the ping test  http://gyazo.com/c6a1200552456fe34c3de03cf7591df2

I think I might step this one out. Good luck! 

I'm seeing this too, on the RI system (Connecticut). 

Here's the standard deviation for ping times for a few sites:

That's not the ping time—it's the standard deviation across ten pings, the variability in ping times. 90 ms is getting a bit high. 300 ms is absurd, and a sign of equipment failure somewhere. Pinging Google should not result in ten results ranging from 44 ms (normal) to 1039 ms (extremely abnormal). 1,000 ms is the ping time you'd expect from a spacecraft that's one third of the way to the moon, not a Google server someplace on the same continent as you...

robl@murphy:/home/robl % ping -c 10 www.macwhiz.com

PING macwhiz.com (67.210.126.100): 56 data bytes

64 bytes from 67.210.126.100: icmp_seq=0 ttl=54 time=103.838 ms

64 bytes from 67.210.126.100: icmp_seq=1 ttl=54 time=152.213 ms

64 bytes from 67.210.126.100: icmp_seq=2 ttl=54 time=289.305 ms

64 bytes from 67.210.126.100: icmp_seq=3 ttl=54 time=1088.489 ms

64 bytes from 67.210.126.100: icmp_seq=4 ttl=54 time=891.626 ms

64 bytes from 67.210.126.100: icmp_seq=5 ttl=54 time=318.757 ms

64 bytes from 67.210.126.100: icmp_seq=6 ttl=54 time=130.996 ms

64 bytes from 67.210.126.100: icmp_seq=7 ttl=54 time=140.065 ms

64 bytes from 67.210.126.100: icmp_seq=8 ttl=54 time=1089.287 ms

64 bytes from 67.210.126.100: icmp_seq=9 ttl=54 time=716.430 ms

--- macwhiz.com ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 103.838/492.101/1089.287/389.105 ms

robl@murphy:/home/robl % traceroute www.macwhiz.com

traceroute to macwhiz.com (67.210.126.100), 64 hops max, 52 byte packets

 1  10.4.56.1 (10.4.56.1)  11.633 ms  19.105 ms  19.981 ms

 2  ip98-190-162-112.ri.ri.cox.net (98.190.162.112)  20.778 ms  21.386 ms  17.903 ms

 3  ip98-190-33-82.ri.ri.cox.net (98.190.33.82)  21.384 ms  19.225 ms  19.739 ms

 4  ip98-190-33-24.ri.ri.cox.net (98.190.33.24)  20.982 ms  21.077 ms  17.963 ms

 5  nyrkbprj01-ae3.0.rd.ny.cox.net (68.1.5.157)  28.369 ms  37.105 ms  21.638 ms

 6  68.105.31.78 (68.105.31.78)  20.379 ms  36.253 ms  19.583 ms

 7  ae8.cr1.lga5.us.zip.zayo.com (64.125.26.161)  20.781 ms  20.625 ms  26.203 ms

 8  ae5.cr1.dca2.us.zip.zayo.com (64.125.26.97)  42.768 ms  33.584 ms  41.847 ms

 9  ae5.cr1.iah1.us.zip.zayo.com (64.125.20.186)  68.605 ms  61.077 ms  58.014 ms

10  ae2.cr1.lax112.us.zip.zayo.com (64.125.20.210)  90.721 ms * *

11  ae3.mpr1.lax103.us.zip.zayo.com (64.125.20.226)  97.056 ms  100.661 ms  96.452 ms

12  64.125.192.154.t01440-01.above.net (64.125.192.154)  100.174 ms  97.433 ms  99.974 ms

13  817.ae3.irv01-mls-dc-core-b.irv01.latisys.net (207.38.15.70)  102.266 ms  97.535 ms

    815.ae3.irv01-mls-dc-core-a.irv01.latisys.net (207.38.15.66)  101.590 ms

14  819.ae7.irv02-mls-dc-core-a.irv02.latisys.net (207.38.15.74)  95.630 ms

    849.ae8.irv02-mls-dc-core-a.irv02.latisys.net (207.38.15.82)  97.773 ms

    819.ae7.irv02-mls-dc-core-a.irv02.latisys.net (207.38.15.74)  104.337 ms

15  923.po3.irv02-mls-dc-dist-a.irv02.latisys.net (207.38.15.30)  94.364 ms

    922.po14.irv02-mls-dc-dist-a.irv02.latisys.net (207.38.15.26)  99.095 ms  101.206 ms

16  207.38.44.82 (207.38.44.82)  94.880 ms

    207.38.44.74 (207.38.44.74)  100.505 ms  96.193 ms

17  neptune.lunarpages.com (67.210.126.100)  96.888 ms  101.146 ms  100.464 ms

robl@murphy:/home/robl % ping -c 10 www.google.com

PING www.google.com (173.194.219.147): 56 data bytes

64 bytes from 173.194.219.147: icmp_seq=0 ttl=44 time=79.440 ms

64 bytes from 173.194.219.147: icmp_seq=1 ttl=44 time=142.511 ms

64 bytes from 173.194.219.147: icmp_seq=2 ttl=44 time=1037.583 ms

64 bytes from 173.194.219.147: icmp_seq=3 ttl=44 time=582.586 ms

64 bytes from 173.194.219.147: icmp_seq=4 ttl=44 time=81.888 ms

64 bytes from 173.194.219.147: icmp_seq=5 ttl=44 time=1039.222 ms

64 bytes from 173.194.219.147: icmp_seq=6 ttl=44 time=226.068 ms

64 bytes from 173.194.219.147: icmp_seq=7 ttl=44 time=65.330 ms

64 bytes from 173.194.219.147: icmp_seq=8 ttl=44 time=44.393 ms

64 bytes from 173.194.219.147: icmp_seq=9 ttl=44 time=127.500 ms

--- www.google.com ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 44.393/342.652/1039.222/377.993 ms

robl@murphy:/home/robl % traceroute www.google.com

traceroute: Warning: www.google.com has multiple addresses; using 173.194.219.104

traceroute to www.google.com (173.194.219.104), 64 hops max, 52 byte packets

 1  10.4.56.1 (10.4.56.1)  83.214 ms  241.702 ms  17.893 ms

 2  ip98-190-163-112.ri.ri.cox.net (98.190.163.112)  6.698 ms  2288.114 ms  27.402 ms

 3  ip98-190-33-84.ri.ri.cox.net (98.190.33.84)  33.024 ms  34.307 ms  692.791 ms

 4  ip98-190-33-34.ri.ri.cox.net (98.190.33.34)  68.244 ms  939.952 ms  31.739 ms

 5  nyrkbprj01-ae3.0.rd.ny.cox.net (68.1.5.157)  63.433 ms  637.669 ms  1044.564 ms

 6  68.105.31.87 (68.105.31.87)  55.439 ms  228.604 ms  1389.282 ms

 7  216.239.50.106 (216.239.50.106)  54.762 ms

    209.85.255.68 (209.85.255.68)  158.260 ms

    216.239.50.106 (216.239.50.106)  21.810 ms

 8  209.85.249.212 (209.85.249.212)  117.728 ms

    209.85.246.4 (209.85.246.4)  1059.188 ms

    72.14.236.208 (72.14.236.208)  53.066 ms

 9  209.85.249.11 (209.85.249.11)  43.633 ms  49.455 ms

    209.85.143.222 (209.85.143.222)  292.925 ms

10  72.14.235.12 (72.14.235.12)  165.316 ms

    216.239.48.160 (216.239.48.160)  894.313 ms

    64.233.174.11 (64.233.174.11)  962.220 ms

11  72.14.239.66 (72.14.239.66)  400.983 ms  40.457 ms

    216.239.48.151 (216.239.48.151)  56.724 ms

12  209.85.142.157 (209.85.142.157)  41.652 ms

    209.85.143.193 (209.85.143.193)  111.493 ms

    209.85.143.201 (209.85.143.201)  399.593 ms

13  * * *

14  173.194.219.104 (173.194.219.104)  734.959 ms  446.913 ms  131.912 ms

robl@murphy:/home/robl % ping -c 10 www.cnn.com

PING fallback.global-ssl.fastly.net (199.27.76.184): 56 data bytes

64 bytes from 199.27.76.184: icmp_seq=0 ttl=58 time=209.533 ms

64 bytes from 199.27.76.184: icmp_seq=1 ttl=58 time=256.440 ms

64 bytes from 199.27.76.184: icmp_seq=2 ttl=58 time=643.952 ms

64 bytes from 199.27.76.184: icmp_seq=3 ttl=58 time=168.590 ms

64 bytes from 199.27.76.184: icmp_seq=4 ttl=59 time=319.601 ms

64 bytes from 199.27.76.184: icmp_seq=5 ttl=58 time=118.762 ms

64 bytes from 199.27.76.184: icmp_seq=6 ttl=58 time=966.693 ms

64 bytes from 199.27.76.184: icmp_seq=7 ttl=59 time=707.557 ms

64 bytes from 199.27.76.184: icmp_seq=8 ttl=59 time=40.960 ms

64 bytes from 199.27.76.184: icmp_seq=9 ttl=58 time=125.365 ms

--- fallback.global-ssl.fastly.net ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 40.960/355.745/966.693/292.573 ms

robl@murphy:/home/robl % traceroute 199.27.76.184

traceroute to 199.27.76.184 (199.27.76.184), 64 hops max, 52 byte packets

 1  10.4.56.1 (10.4.56.1)  55.207 ms  16.623 ms  87.414 ms

 2  ip98-190-163-112.ri.ri.cox.net (98.190.163.112)  18.297 ms  106.725 ms  173.755 ms

 3  ip98-190-33-84.ri.ri.cox.net (98.190.33.84)  101.907 ms  1161.792 ms  1496.438 ms

 4  ip98-190-33-34.ri.ri.cox.net (98.190.33.34)  117.231 ms  111.818 ms  112.131 ms

 5  nyrkbprj02-ae3.0.rd.ny.cox.net (68.1.5.161)  110.937 ms  17.532 ms  113.938 ms

 6  te-0-5-0-8-pe02.111eighthave.ny.ibone.comcast.net (173.167.58.101)  111.206 ms  43.569 ms  69.891 ms

 7  he-1-2-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.86.249)  101.624 ms  46.141 ms

    he-1-5-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.85.17)  45.057 ms

 8  he-0-11-0-1-pe03.111eighthave.ny.ibone.comcast.net (68.86.83.102)  64.487 ms  122.861 ms  114.426 ms

 9  * * *

10  * * *

11  * * *

robl@murphy:/home/robl % ping -c 10 www.wfsb.com

PING a948.w5.akamai.net (184.29.105.67): 56 data bytes

64 bytes from 184.29.105.67: icmp_seq=0 ttl=59 time=359.635 ms

64 bytes from 184.29.105.67: icmp_seq=1 ttl=59 time=38.676 ms

64 bytes from 184.29.105.67: icmp_seq=2 ttl=59 time=27.115 ms

64 bytes from 184.29.105.67: icmp_seq=3 ttl=59 time=36.024 ms

64 bytes from 184.29.105.67: icmp_seq=4 ttl=59 time=59.062 ms

64 bytes from 184.29.105.67: icmp_seq=5 ttl=59 time=20.140 ms

64 bytes from 184.29.105.67: icmp_seq=6 ttl=59 time=67.240 ms

64 bytes from 184.29.105.67: icmp_seq=7 ttl=59 time=24.835 ms

64 bytes from 184.29.105.67: icmp_seq=8 ttl=59 time=19.414 ms

64 bytes from 184.29.105.67: icmp_seq=9 ttl=59 time=106.679 ms

--- a948.w5.akamai.net ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 19.414/75.882/359.635/98.018 ms

robl@murphy:/home/robl % traceroute 184.29.105.67

traceroute to 184.29.105.67 (184.29.105.67), 64 hops max, 52 byte packets

 1  10.4.56.1 (10.4.56.1)  109.986 ms  89.267 ms  37.942 ms

 2  ip98-190-162-112.ri.ri.cox.net (98.190.162.112)  1007.266 ms  1017.550 ms  1784.142 ms

 3  ip98-190-33-82.ri.ri.cox.net (98.190.33.82)  39.432 ms  529.288 ms  722.454 ms

 4  ip98-190-33-24.ri.ri.cox.net (98.190.33.24)  142.953 ms  720.533 ms  1474.164 ms

 5  nyrkbprj01-ae3.0.rd.ny.cox.net (68.1.5.157)  262.237 ms  24.786 ms  798.815 ms

 6  68.105.31.126 (68.105.31.126)  903.465 ms  24.994 ms  64.148 ms

 7  a184-29-105-67.deploy.static.akamaitechnologies.com (184.29.105.67)  27.897 ms  46.379 ms  31.985 ms

Also seeing substantial uncorrectables on the modem, less than two hours after reboot:

@ChrisL: Yes, I'm still seeing massive latency spikes. As best I can tell from traceroutes, they're occurring close to me network-wise. If I ping the first hop in my traceroute (local node? hubsite?) I'm seeing the issue:

robl@murphy:/etc % ping -c 10 10.4.56.1

PING 10.4.56.1 (10.4.56.1): 56 data bytes

64 bytes from 10.4.56.1: icmp_seq=0 ttl=255 time=30.112 ms

64 bytes from 10.4.56.1: icmp_seq=1 ttl=255 time=93.806 ms

64 bytes from 10.4.56.1: icmp_seq=2 ttl=255 time=88.947 ms

64 bytes from 10.4.56.1: icmp_seq=3 ttl=255 time=12.417 ms

64 bytes from 10.4.56.1: icmp_seq=4 ttl=255 time=8.898 ms

64 bytes from 10.4.56.1: icmp_seq=5 ttl=255 time=982.096 ms

64 bytes from 10.4.56.1: icmp_seq=6 ttl=255 time=911.200 ms

64 bytes from 10.4.56.1: icmp_seq=7 ttl=255 time=98.414 ms

64 bytes from 10.4.56.1: icmp_seq=8 ttl=255 time=85.507 ms

--- 10.4.56.1 ping statistics ---

10 packets transmitted, 9 packets received, 10.0% packet loss

round-trip min/avg/max/stddev = 8.898/256.822/982.096/370.589 ms

Same story with almost any destination IP. Ping times spiking up over one second. NTP can't get a solid lock, there's too much jitter in the latency to keep good time. Online games like Diablo III are unplayable. VoIP is unusable.

By the way: I've noticed my modem occasionally spiking its upstream power over 50 dBmV; I understand that's out-of-spec for DOCSIS 3.0. My drop is underground RG-11 installed less than two years ago. It runs to one Cox-installed amplifier; one leg of the amp output goes to the modem (via the power inserter). The other leg goes to the TVs.

We've had a lot of outages lately. Does Cox need to replace some equipment in this area or something?

Outage: Feb 24 2015 00:40:22 EST

Outage: Mar  9 2015 00:37:12 EDT

Outage: Mar 13 2015 01:00:12 EDT

Outage: Mar 15 2015 22:37:12 EDT

Outage: Mar 16 2015 01:35:12 EDT

The fact that this issue started after the most recent Sunday/Monday outages seems suspicious.