Consistent ~5% Packet Loss (Connecticut)
I'm a Cox customer living in CT. I have been experiencing packet loss for the past few weeks. It does not appear to be on my end. Below I'll post MTR results (I am pinging a Blizzard game server).
...
Forum Discussion
So, I experienced no packet loss at all during the past weekend (11/30 and 12/1). It was even fine this morning around 6:30 A.M.
However, as of 6:30 P.M. tonight (12/2), it is back to haunt me. I have not made any hardware or firmware changes to spur this on.
While this has occurred on some mornings, it seems to really only be an issue at prime time (evenings). Perhaps there is some sort of localized congestion/traffic. Based on the previous discussion and presented information, it doesn't appear to be any of my equipment. We previously discussed that I do not have any splitters or amplifiers installed.
Below is a fresh WinMTR (again over a hard-wired connection):
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 561 | 561 | 0 | 0 | 2 | 0 |
| 10.4.0.1 - 6 | 561 | 531 | 3 | 8 | 41 | 6 |
| 100.120.244.90 - 5 | 561 | 538 | 5 | 9 | 47 | 10 |
| 100.120.244.202 - 6 | 561 | 531 | 6 | 13 | 90 | 10 |
| nyrkbprj01-ae3.0.rd.ny.cox.net - 5 | 560 | 534 | 12 | 17 | 115 | 21 |
| 68.105.31.75 - 5 | 560 | 535 | 11 | 21 | 170 | 15 |
| ae1-br01-eqny8.as57976.net - 5 | 560 | 535 | 30 | 39 | 158 | 38 |
| et-0-0-2-br02-eqch2.as57976.net - 5 | 560 | 533 | 30 | 39 | 134 | 34 |
| be2-pe1-eqch2.as57976.net - 5 | 560 | 532 | 29 | 35 | 60 | 33 |
| chi-eqch2-ia-bons-02.as57976.net - 6 | 560 | 531 | 32 | 37 | 53 | 36 |
| 24.105.62.129 - 6 | 560 | 531 | 31 | 36 | 51 | 35 |
|________________________________________________|______|______|______|______|______|______|
Similar to previous experiences, I am experiencing a consistent 3-6% packet loss, starting with the second hop (whatever that is).
Edit: Could this be caused by the cold/stormy weather? Given that it has been somewhat cold the past few weeks, and snowy today, could a connection somewhere to the local node be messed up somehow?
