Well I had ATT installed yesterday. Night and day difference. Zero lag or latency issues anymore. Latency to the servers is a fairly rock solid 26ms.
Just rechecked the ground and it is actually there.
Played some Rocket League as soon as I got home and there was still some lag. It is a very intermittent issue. I can go an hour without anything and then bam, it becomes unplayable.
See below for test results. Direct connect to modem with a fresh reboot. Did MTR, status log, and a ping plotter right after each other. Same culprit of langbprj01-ae1.rd.la.cox.net every time...
Errors only on one channel now which is good. I tend to see 0 errors without the 3db attenuator IIRC.
162.245.206.16
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.177.0.1 - 0 | 2013 | 2013 | 4 | 15 | 179 | 10 |
| 68.6.14.178 - 0 | 2013 | 2013 | 6 | 16 | 195 | 8 |
| 100.120.108.32 - 0 | 2013 | 2013 | 6 | 19 | 211 | 9 |
| langbprj01-ae1.rd.la.cox.net - 1 | 1968 | 1956 | 10 | 24 | 278 | 13 |
| 68.105.30.138 - 0 | 2013 | 2013 | 11 | 24 | 186 | 11 |
| hosted-by.i3d.net - 0 | 2013 | 2013 | 10 | 22 | 227 | 11 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)
|
Startup Procedure |
||
|
Procedure |
Status |
Comment |
|
Acquire Downstream Channel |
909000000 Hz |
Locked |
|
Connectivity State |
OK |
Operational |
|
Boot State |
OK |
Operational |
|
Configuration File |
OK |
|
|
Security |
Enabled |
BPI+ |
|
DOCSIS Network Access Enabled |
Allowed |
|
|
Downstream Bonded Channels |
|||||||
|
Channel ID |
Lock Status |
Modulation |
Frequency |
Power |
SNR/MER |
Corrected |
Uncorrectables |
|
22 |
Locked |
QAM256 |
909000000 Hz |
2.2 dBmV |
41.1 dB |
0 |
0 |
|
1 |
Locked |
QAM256 |
783000000 Hz |
2.2 dBmV |
40.3 dB |
0 |
0 |
|
2 |
Locked |
QAM256 |
789000000 Hz |
2.3 dBmV |
40.5 dB |
0 |
0 |
|
3 |
Locked |
QAM256 |
795000000 Hz |
2.0 dBmV |
40.3 dB |
0 |
0 |
|
4 |
Locked |
QAM256 |
801000000 Hz |
1.9 dBmV |
40.3 dB |
0 |
0 |
|
9 |
Locked |
QAM256 |
831000000 Hz |
1.7 dBmV |
40.4 dB |
0 |
0 |
|
10 |
Locked |
QAM256 |
837000000 Hz |
1.7 dBmV |
40.5 dB |
0 |
0 |
|
11 |
Locked |
QAM256 |
843000000 Hz |
1.9 dBmV |
40.6 dB |
0 |
0 |
|
12 |
Locked |
QAM256 |
849000000 Hz |
1.4 dBmV |
40.2 dB |
0 |
0 |
|
17 |
Locked |
QAM256 |
879000000 Hz |
2.0 dBmV |
40.3 dB |
0 |
0 |
|
18 |
Locked |
QAM256 |
885000000 Hz |
2.4 dBmV |
40.8 dB |
0 |
0 |
|
19 |
Locked |
QAM256 |
891000000 Hz |
2.2 dBmV |
40.9 dB |
0 |
0 |
|
20 |
Locked |
QAM256 |
897000000 Hz |
2.3 dBmV |
41.0 dB |
1527 |
3 |
|
21 |
Locked |
QAM256 |
903000000 Hz |
2.4 dBmV |
41.4 dB |
0 |
0 |
|
25 |
Locked |
QAM256 |
927000000 Hz |
2.3 dBmV |
41.2 dB |
0 |
0 |
|
26 |
Locked |
QAM256 |
933000000 Hz |
2.1 dBmV |
41.3 dB |
0 |
0 |
|
27 |
Locked |
QAM256 |
939000000 Hz |
2.1 dBmV |
41.2 dB |
0 |
0 |
|
28 |
Locked |
QAM256 |
945000000 Hz |
2.0 dBmV |
41.1 dB |
0 |
0 |
|
29 |
Locked |
QAM256 |
951000000 Hz |
1.8 dBmV |
41.0 dB |
0 |
0 |
|
30 |
Locked |
QAM256 |
957000000 Hz |
1.8 dBmV |
41.0 dB |
0 |
0 |
|
33 |
Locked |
QAM256 |
357000000 Hz |
5.1 dBmV |
41.3 dB |
0 |
0 |
|
34 |
Locked |
QAM256 |
363000000 Hz |
5.0 dBmV |
41.4 dB |
0 |
0 |
|
35 |
Locked |
QAM256 |
369000000 Hz |
4.7 dBmV |
41.3 dB |
0 |
0 |
|
36 |
Locked |
QAM256 |
375000000 Hz |
4.7 dBmV |
41.5 dB |
0 |
0 |
|
37 |
Locked |
QAM256 |
381000000 Hz |
4.9 dBmV |
41.4 dB |
0 |
0 |
|
38 |
Locked |
QAM256 |
387000000 Hz |
4.7 dBmV |
41.3 dB |
0 |
0 |
|
41 |
Locked |
QAM256 |
405000000 Hz |
5.0 dBmV |
41.5 dB |
0 |
0 |
|
42 |
Locked |
QAM256 |
411000000 Hz |
5.2 dBmV |
41.6 dB |
0 |
0 |
|
43 |
Locked |
QAM256 |
417000000 Hz |
5.3 dBmV |
41.6 dB |
0 |
0 |
|
44 |
Locked |
QAM256 |
423000000 Hz |
5.5 dBmV |
41.7 dB |
0 |
0 |
|
45 |
Locked |
QAM256 |
429000000 Hz |
5.6 dBmV |
41.8 dB |
0 |
0 |
|
46 |
Locked |
QAM256 |
435000000 Hz |
5.6 dBmV |
41.9 dB |
0 |
0 |
|
159 |
Locked |
Other |
300000000 Hz |
7.7 dBmV |
42.0 dB |
246385740 |
0 |
|
Upstream Bonded Channels |
||||||
|
Channel |
Channel ID |
Lock Status |
US Channel Type |
Frequency |
Width |
Power |
|
1 |
3 |
Locked |
SC-QAM Upstream |
32200000 Hz |
6400000 Hz |
35.0 dBmV |
|
2 |
1 |
Locked |
SC-QAM Upstream |
19400000 Hz |
6400000 Hz |
35.0 dBmV |
|
3 |
2 |
Locked |
SC-QAM Upstream |
25800000 Hz |
6400000 Hz |
35.0 dBmV |
|
4 |
4 |
Locked |
SC-QAM Upstream |
38600000 Hz |
6400000 Hz |
35.0 dBmV |
Current System Time: Thu Feb 13 17:08:23 2020
Hi Chris,
Not sure if you're trolling but in that ping plotter there is .4% PL across the board and 2.5% shown at the hop I'm talking about. The .4% across the board leads my to believe a weak connection to my modem. The MTR shows minor packet loss at the hop I'm talking about as well. Happens intermittently which is frustrating when playing video games online. Also there is a good amount of jitter and ping spikes intermittently. All of these things are EXTREMELY noticeable when playing Rocket League.
I need to mention that my connection did improve after removing the splitter and installing a coupler. Things are better and I'm not seeing constant T3 timeouts on the log. Before I was at ~5% PL at times but now it seems to be <1%.
Here is another ping plotter over a 30m period which shows a large amount of jitter and ping spikes all of which are noticeable in Rocket League.
In the past I have had issues with streaming YouTube TV and Netflix. I'd often have times where the quality would drop out and pixelate and then come back. I would often get ~5-10mbps upload instead of the 35mbps advertised. Right now I am sitting around 33mbps since removing the splitter. I need my upload since I often WFH.
Here is also the latest event log from the modem. Fairly quiet until this morning when I got a T3 timeout.
| 02/14/2020 07:42 | 2436694061 | 5 | "Dynamic Range Window violation" |
| 02/14/2020 07:42 | 82001100 | 5 | "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=2c:ab:eb:27:a1:5d;CM-QOS=1.1;CM-VER=3.1;" |
| 02/14/2020 03:39 | 82000500 | 3 | "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=2c:ab:eb:27:a1:5d;CM-QOS=1.1;CM-VER=3.1;" |
Trust me when I say this. I have done the same thing you are doing right now with more evidence with the spikes and packetloss but hear me out.. They wont tell you there is a problem. They are playing blind. I had to battle with them for a good month with clear evidences yet they sway or ignore the obvious loss from their servers. There's a lot of us having the same problem but Cox isn't doing anything. I hope you can fix your issue though and good luck fighting with them.
