Packet loss/bad connection Rocket League

I took too long to provide information for my last post so it was locked.

I tend to have pretty intermittent packet loss/bad connection/lag in Rocket League and random points of the day. Was great last night and this morning but went bad early afternoon.

Here is an MTR test showing a bad connection to anything after my router. Will take more when the connection gets bad.

Any idea? Weak signal to my modem?

I have gigabit and SB8200. Everything is hardwired.

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.1.1 - 0 | 1243 | 1243 | 1 | 3 | 120 | 2 |

| 10.177.0.1 - 1 | 1239 | 1238 | 5 | 22 | 351 | 13 |

| 68.6.14.176 - 1 | 1235 | 1233 | 7 | 23 | 327 | 11 |

| 100.120.108.30 - 1 | 1235 | 1233 | 7 | 26 | 303 | 31 |

| langbprj01-ae1.rd.la.cox.net - 1 | 1204 | 1194 | 11 | 35 | 268 | 18 |

| 68.105.30.138 - 1 | 1235 | 1233 | 12 | 29 | 295 | 19 |

| ns2.i3d.global - 1 | 1235 | 1233 | 14 | 28 | 302 | 19 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

Responses

Accepted Solution

jearbear

Contributor

•

43 Messages

5 years ago

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.

9

I've had the exact same issues as you as well as contacted cox on multiple occasions. On my end they've told me countless different solutions that never worked and at this point they refuse to even help me. I plan on leaving them soon as well as I am through with this absurd internet service provider and customer service. How is AT&T so far? Are they reliable? I'll be looking back at this forum often so I'd appreciate it if you updated

Like

Reply

5 years ago

0

KevinM2

Former Moderator

•

1.5K Messages

@deorlol, we are detecting signal issues with your modem currently. Is there a splitter attached to the coaxial cable, where the modem is located in your home? Can you please make sure all connections are free of damage?

When gaming, are you doing so while hard-wired directly to the modem? -Kevin M. Cox Support Forum Moderator

Like

Reply

5 years ago

0

deorlol

New Contributor II

•

6 Messages

Yes, there is a splitter attached to the coaxial cable. It was put in by one of your technical assistants that came over to my place. I am on Ethernet cable as well when I am gaming. All connections are free of damage as I have not moved or done anything differently since the technician came.

Like

Reply

5 years ago

0

KevinM2

Former Moderator

•

1.5K Messages

Your signal levels look great now and I'm not seeing anything out of the ordinary. Would you be able to email us hard-wired traceroutes to the gaming server so we can have them reviewed? -Kevin M. Cox Support Forum Moderator

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

Hey deorlol,

I have had nothing but a solid internet connection going to AT&T. It is a bit slower but I have absolutely ZERO issues with gaming now even with a few folks playing different games at the same time. I consistently get 60mbps down / 15 up. If gaming is your main focus I would look into it.

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

6 years ago

One more, the lag is bad at the moment. Taken from a wireless PC so there is the loss to router. Playing hardwired.

ping spikes in the 4xx

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.1.1 - 1 | 795 | 794 | 1 | 4 | 85 | 2 |

| 10.177.0.1 - 1 | 795 | 794 | 5 | 36 | 431 | 111 |

| 68.6.14.176 - 1 | 791 | 789 | 7 | 37 | 437 | 119 |

| 100.120.108.30 - 1 | 795 | 794 | 5 | 40 | 422 | 104 |

| langbprj01-ae1.rd.la.cox.net - 1 | 772 | 765 | 15 | 48 | 317 | 88 |

| 68.105.30.138 - 1 | 791 | 789 | 12 | 45 | 434 | 120 |

| ns2.i3d.global - 1 | 791 | 789 | 11 | 43 | 393 | 137 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

0

jearbear

Contributor

•

43 Messages

6 years ago

current traceroute to langbprj01

traceroute to langbprj01-ae1.rd.la.cox.net (68.1.1.13), 64 hops max, 52 byte packets

1 192.168.1.1 (192.168.1.1) 4.105 ms 2.146 ms 2.300 ms

2 10.177.0.1 (10.177.0.1) 34.642 ms 21.920 ms 18.366 ms

3 68.6.14.178 (68.6.14.178) 19.514 ms 26.670 ms 85.403 ms

4 100.120.108.32 (100.120.108.32) 169.719 ms 25.668 ms 107.798 ms

5 * * *

6 * * *

7 * * *

8 * * *

9 langbprj01-ae1.rd.la.cox.net (68.1.1.13) 36.114 ms 23.925 ms 32.835 ms

5

0

MarkM1

Former Moderator

•

231 Messages

Jeabear,

The modem is testing fine at this time on our end. Are you able to bypass your router & plug a device into the modem to test the connection there at this time? We want to see the difference in the connection. Let us know if you can test this for us.

Mark M.
Cox Support Forums Moderator

Like

Reply

6 years ago

0

Tierdisogni

New Contributor II

•

5 Messages

You are not alone. Look through the first 3 pages of these forums and you'll see the same posts by different people. You'll also see the same copy paste response from forum moderators. I have the same issue as you for rocket league, today was so bad I couldn't get through a single match due to the packet loss/rubberbanding. I'm sorry to say I don't think you'll find any help here.

Like

Reply

6 years ago

jearbear

Contributor

•

43 Messages

I see it all over the boards and nuts they won't do anything about it. Every online game ** big time for the most part and I tend to only get 200mbps with my gigablast most of the time and a 2mbps upload. Definitely not getting advertised speeds in the least. And the packet loss is ridiculous. Maybe it is fast but this is some of the worst internet I've used for gaming. I never had the issue before with Comcast but now with COX it is the worst. It is so bad I've even considered going to ATT for gaming only.

I must say packet loss was non existent for about 2 days after upgrading to gigablast. Now it is back to the lower tier quality. I thought it was because of a limited upload speed and some of my devices hogging the pipe so I upgraded everything but that is not the case.... I've had the issue for over the past year, ever since I signed up with their service.

markm1 I will plug my device direct into the modem. It is intermittent. Right now it is okay but later I am sure it will be terrible.

Like

Reply

6 years ago

0

jearbear

Contributor

•

43 Messages

can you take a look now? I am getting VERY BAD rubber banding and loss.

Like

Reply

6 years ago

0

Tierdisogni

New Contributor II

•

5 Messages

I had a tech out less than an hour ago. He found an issue, resolved it, ran tests and it all checked out. That was roughly 12pm PST, it's now 1:30 and I'm getting less than 100 mbps down. Tested all lines from tap to house and they checked out. I've noticed the same routing issue with ping plotter where signals getting sent to the east coast before making it's way back. I hope you can find some resolution on your end.

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

6 years ago

Here is the latest from today. WinMTR direct into the modem with IPs for the RL servers.

At 5% average packet loss!

Hardwired to modem
162.245.206.16
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.177.0.1 - 5 | 1328 | 1269 | 6 | 81 | 431 | 21 |
| 68.6.14.176 - 5 | 1328 | 1269 | 6 | 82 | 429 | 17 |
| 100.120.108.30 - 5 | 1328 | 1269 | 4 | 84 | 431 | 17 |
| langbprj01-ae1.rd.la.cox.net - 6 | 1296 | 1229 | 12 | 88 | 439 | 21 |
| 68.105.30.138 - 5 | 1332 | 1274 | 13 | 89 | 437 | 21 |
| hosted-by.i3d.net - 5 | 1328 | 1269 | 12 | 86 | 434 | 26 |
|________________________________________________|______|______|______|______|______|
______|
WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

107.182.228.217
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.177.0.1 - 5 | 612 | 587 | 6 | 59 | 407 | 21 |
| 68.6.14.178 - 5 | 608 | 582 | 7 | 62 | 411 | 23 |
| 100.120.108.32 - 5 | 612 | 587 | 7 | 64 | 414 | 58 |
| langbprj01-ae1.rd.la.cox.net - 5 | 600 | 572 | 11 | 70 | 415 | 43 |
| Request timed out. - 100 | 143 | 0 | 0 | 0 | 0 | 0 |
| 4.69.220.105 - 5 | 608 | 582 | 33 | 90 | 438 | 50 |
| 4.35.171.110 - 5 | 608 | 582 | 34 | 89 | 436 | 54 |
| 206.130.126.26.west-datacenter.net - 5 | 612 | 587 | 35 | 93 | 485 | 53 |
| 6bb6e4d9.setaptr.net - 5 | 612 | 587 | 34 | 88 | 435 | 58 |
|________________________________________________|______|______|______|______|______|
______|
WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

0

jearbear

Contributor

•

43 Messages

6 years ago

Still bad and unable to play. Here are my channel SNRs and the event log. Lots of errors.

Startup Procedure
Procedure	Status	Comment
Acquire Downstream Channel	831000000 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
9	Locked	QAM256	831000000 Hz	0.9 dBmV	40.5 dB	0	0
1	Locked	QAM256	783000000 Hz	1.0 dBmV	40.2 dB	0	0
2	Locked	QAM256	789000000 Hz	1.5 dBmV	40.5 dB	0	0
3	Locked	QAM256	795000000 Hz	1.6 dBmV	40.4 dB	0	0
4	Locked	QAM256	801000000 Hz	1.0 dBmV	40.3 dB	0	0
10	Locked	QAM256	837000000 Hz	1.1 dBmV	40.5 dB	0	0
11	Locked	QAM256	843000000 Hz	1.3 dBmV	40.7 dB	0	0
12	Locked	QAM256	849000000 Hz	0.6 dBmV	40.2 dB	0	0
17	Locked	QAM256	879000000 Hz	0.7 dBmV	40.4 dB	0	0
18	Locked	QAM256	885000000 Hz	1.1 dBmV	40.7 dB	0	0
19	Locked	QAM256	891000000 Hz	1.2 dBmV	41.0 dB	0	0
20	Locked	QAM256	897000000 Hz	0.9 dBmV	41.0 dB	0	0
21	Locked	QAM256	903000000 Hz	1.2 dBmV	41.2 dB	0	0
22	Locked	QAM256	909000000 Hz	1.1 dBmV	41.2 dB	0	0
25	Locked	QAM256	927000000 Hz	1.1 dBmV	41.2 dB	0	0
26	Locked	QAM256	933000000 Hz	0.8 dBmV	41.0 dB	0	0
27	Locked	QAM256	939000000 Hz	1.0 dBmV	41.1 dB	0	0
28	Locked	QAM256	945000000 Hz	0.8 dBmV	40.9 dB	0	0
29	Locked	QAM256	951000000 Hz	0.6 dBmV	41.0 dB	0	0
30	Locked	QAM256	957000000 Hz	0.5 dBmV	40.8 dB	0	0
33	Locked	QAM256	357000000 Hz	4.2 dBmV	41.3 dB	0	0
34	Locked	QAM256	363000000 Hz	4.0 dBmV	41.4 dB	0	0
35	Locked	QAM256	369000000 Hz	4.0 dBmV	41.3 dB	0	0
36	Locked	QAM256	375000000 Hz	3.6 dBmV	41.3 dB	0	0
37	Locked	QAM256	381000000 Hz	4.2 dBmV	41.4 dB	0	0
38	Locked	QAM256	387000000 Hz	4.1 dBmV	41.3 dB	0	0
41	Locked	QAM256	405000000 Hz	4.4 dBmV	41.5 dB	0	0
42	Locked	QAM256	411000000 Hz	4.2 dBmV	41.6 dB	0	0
43	Locked	QAM256	417000000 Hz	4.8 dBmV	41.8 dB	0	0
44	Locked	QAM256	423000000 Hz	4.5 dBmV	41.7 dB	0	0
45	Locked	QAM256	429000000 Hz	4.6 dBmV	41.7 dB	0	0
46	Locked	QAM256	435000000 Hz	5.0 dBmV	41.8 dB	0	0
159	Locked	Other	300000000 Hz	6.9 dBmV	42.0 dB	235685401	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	36.0 dBmV
4	4	Locked	SC-QAM Upstream	38600000 Hz	6400000 Hz	35.0 dBmV

Current System Time: Mon Feb 10 16:14:46 2020

02/10/2020 15:50	2436694061	5	"Dynamic Range Window violation"
02/10/2020 15:50	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/10/2020 15:50	84000500	3	"SYNC Timing Synchronization failure - Loss of Sync;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/10/2020 15:38	2436694061	5	"Dynamic Range Window violation"
02/10/2020 15:38	82001200	5	"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the 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/10/2020 15:38	2436694061	5	"Dynamic Range Window violation"
02/10/2020 15:38	82001200	5	"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the 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/10/2020 15:38	2436694061	5	"Dynamic Range Window violation"
02/10/2020 15:38	82001200	5	"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the 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/10/2020 15:38	2436694061	5	"Dynamic Range Window violation"
02/10/2020 15:38	82001200	5	"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the 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/10/2020 15:38	2436694061	5	"Dynamic Range Window violation"
02/10/2020 15:38	82001200	5	"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the 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/10/2020 15:38	2436694061	5	"Dynamic Range Window violation"
02/10/2020 15:38	82001200	5	"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the 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/10/2020 15:38	2436694061	5	"Dynamic Range Window violation"
02/10/2020 15:38	82001200	5	"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the 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/10/2020 15:38	2436694061	5	"Dynamic Range Window violation"
02/10/2020 15:38	82001200	5	"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the 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/10/2020 15:38	2436694061	5	"Dynamic Range Window violation"
02/10/2020 15:38	82001200	5	"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the 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/10/2020 15:38	67061600	6	"DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;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/10/2020 15:38	73040100	6	"TLV-11 - unrecognized OID;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/10/2020 15:38	68000300	5	"DHCP WARNING - Non-critical field invalid in response ;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=2c:ab:eb:27:a1:5d;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:00	2436694066	6	"Honoring MDD; IP provisioning mode = IPv4"
01/01/1970 00:00	82000200	3	"No Ranging 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;"
01/01/1970 00:00	84000100	3	"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
02/04/2020 11:10	82000200	3	"No Ranging 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;"
02/04/2020 11:09	82000200	3	"No Ranging 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;"
02/04/2020 11:12	82000200	3	"No Ranging 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;"
02/04/2020 11:10	84000100	3	"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;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/04/2020 11:10	84000100	3	"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;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/02/2020 15:58	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;"
01/25/2020 16:56	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;"
01/24/2020 02:50	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;"
01/23/2020 19:25	82000800	3	"16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=2c:ab:eb:27:a1:5d;CM-QOS=1.1;CM-VER=3.1;"
01/23/2020 19:25	82000600	3	"Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=2c:ab:eb:27:a1:5d;CM-QOS=1.1;CM-VER=3.1;"
01/23/2020 19:25	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;"
01/23/2020 19:17	82000800	3	"16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=2c:ab:eb:27:a1:5d;CM-QOS=1.1;CM-VER=3.1;"
01/23/2020 19:17	82000600	3	"Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=2c:ab:eb:27:a1:5d;CM-QOS=1.1;CM-VER=3.1;"
01/23/2020 19:17	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;"
01/23/2020 18:43	82000200	3	"No Ranging 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;"
01/23/2020 18:43	82000800	3	"16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=2c:ab:eb:27:a1:5d;CM-QOS=1.1;CM-VER=3.1;"
01/23/2020 18:43	82000600	3	"Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=2c:ab:eb:27:a1:5d;CM-QOS=1.1;CM-VER=3.1;"
01/23/2020 18:43	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;"
01/23/2020 16:34	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;"
01/23/2020 15:41	82000800	3	"16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=2c:ab:eb:27:a1:5d;CM-QOS=1.1;CM-VER=3.1;"
01/23/2020 15:41	82000600	3	"Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:00:1c:e9;CMTS-MAC=2c:ab:eb:27:a1:5d;CM-QOS=1.1;CM-VER=3.1;"
01/23/2020 15:41	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;"
01/23/2020 15: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;"

1

0

jearbear

Contributor

•

43 Messages

My previous test was without the 3db attenuator Cox installed, I was trying some different things to see if it was better.

Here it is with it installed again. Arris recommends a minimum of 45 dBmV but I only see 38 dBmV on the upstream channels.

Startup Procedure
Procedure	Status	Comment
Acquire Downstream Channel	831000000 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
9	Locked	QAM256	831000000 Hz	-1.9 dBmV	40.1 dB	0	0
1	Locked	QAM256	783000000 Hz	-1.5 dBmV	39.8 dB	10	0
2	Locked	QAM256	789000000 Hz	-1.0 dBmV	40.1 dB	682	989
3	Locked	QAM256	795000000 Hz	-1.2 dBmV	40.2 dB	829	1179
4	Locked	QAM256	801000000 Hz	-1.8 dBmV	40.1 dB	777	1225
10	Locked	QAM256	837000000 Hz	-1.7 dBmV	40.0 dB	765	1026
11	Locked	QAM256	843000000 Hz	-1.4 dBmV	40.1 dB	670	877
12	Locked	QAM256	849000000 Hz	-2.3 dBmV	39.5 dB	632	879
17	Locked	QAM256	879000000 Hz	-1.7 dBmV	40.0 dB	718	1131
18	Locked	QAM256	885000000 Hz	-1.4 dBmV	40.4 dB	698	1120
19	Locked	QAM256	891000000 Hz	-1.3 dBmV	40.4 dB	681	1115
20	Locked	QAM256	897000000 Hz	-1.6 dBmV	40.6 dB	727	1032
21	Locked	QAM256	903000000 Hz	-1.2 dBmV	40.8 dB	644	1160
22	Locked	QAM256	909000000 Hz	-1.4 dBmV	40.7 dB	668	1268
25	Locked	QAM256	927000000 Hz	-1.4 dBmV	40.9 dB	675	1241
26	Locked	QAM256	933000000 Hz	-1.7 dBmV	40.8 dB	692	1222
27	Locked	QAM256	939000000 Hz	-1.5 dBmV	41.0 dB	849	1098
28	Locked	QAM256	945000000 Hz	-1.8 dBmV	40.7 dB	833	1180
29	Locked	QAM256	951000000 Hz	-1.8 dBmV	40.8 dB	776	1039
30	Locked	QAM256	957000000 Hz	-1.8 dBmV	40.8 dB	681	1029
33	Locked	QAM256	357000000 Hz	1.7 dBmV	41.3 dB	1877	4067
34	Locked	QAM256	363000000 Hz	1.4 dBmV	41.4 dB	1620	3669
35	Locked	QAM256	369000000 Hz	1.6 dBmV	41.4 dB	1489	2915
36	Locked	QAM256	375000000 Hz	1.2 dBmV	41.3 dB	1612	3204
37	Locked	QAM256	381000000 Hz	1.6 dBmV	41.5 dB	1507	3090
38	Locked	QAM256	387000000 Hz	1.5 dBmV	41.2 dB	1296	2888
41	Locked	QAM256	405000000 Hz	1.7 dBmV	41.4 dB	1724	3604
42	Locked	QAM256	411000000 Hz	1.6 dBmV	41.5 dB	1634	3504
43	Locked	QAM256	417000000 Hz	2.2 dBmV	41.7 dB	1670	3264
44	Locked	QAM256	423000000 Hz	1.9 dBmV	41.6 dB	1572	2745
45	Locked	QAM256	429000000 Hz	2.0 dBmV	41.7 dB	1359	2477
46	Locked	QAM256	435000000 Hz	2.4 dBmV	41.8 dB	1308	2436
159	Locked	Other	300000000 Hz	4.5 dBmV	42.0 dB	290140811	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	38.0 dBmV
2	1	Locked	SC-QAM Upstream	19400000 Hz	6400000 Hz	38.0 dBmV
3	2	Locked	SC-QAM Upstream	25800000 Hz	6400000 Hz	39.0 dBmV
4	4	Locked	SC-QAM Upstream	38600000 Hz	6400000 Hz	38.0 dBmV

Current System Time: Mon Feb 10 16:28:06 2020

Like

Reply

6 years ago

0

jearbear

Contributor

•

43 Messages

5 years ago

I've reached out to cox.help@cox.com. We are communicating. Time to create a Twitch account to highlight my Rocket League experience. 🙂

1

0

jearbear

Contributor

•

43 Messages

They said they see no issue with my router or connection and am wondering about my speeds since I mentioned I don't get the full 1gbps. I get 700 down and 35 up but I don't care about that, I want my latency to be good.

My modem has out of spec upload power according to the manufacturer. No problem there or do they even address it. My MTR that showed 5% packet loss to two Rocket League servers was not even addressed.

I can only think it has to do with their old infrastructure. This seems like a redo of the early days of cable internet. Bad connection when everyone in the neighborhood was on. I'm curious at how aged their infrastructure is.... $$$$$$$ to fix.

At this point I'd pay extra or drop to a 100mbps/35mbps plan with good latency for the same price. I'm seriously looking at AT&T plans for gaming only, it is that bad. $60/month to fix this problem.

With how many widespread issues are reported on this forum I'm wondering why there hasn't been a class action lawsuit yet.

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

5 years ago

nonstop dynamic range violations

02/11/2020 21:40	2436694061	5	"Dynamic Range Window violation"
02/11/2020 21:40	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/11/2020 21:35	2436694061	5	"Dynamic Range Window violation"
02/11/2020 21:35	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/11/2020 20:51	2436694061	5	"Dynamic Range Window violation"
02/11/2020 20:51	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/11/2020 20:45	2436694061	5	"Dynamic Range Window violation"
02/11/2020 20:45	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/11/2020 20:40	2436694061	5	"Dynamic Range Window violation"
02/11/2020 20:40	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/11/2020 20:35	2436694061	5	"Dynamic Range Window violation"
02/11/2020 20:35	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/11/2020 20:29	2436694061	5	"Dynamic Range Window violation"
02/11/2020 20:29	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/11/2020 20:24	2436694061	5	"Dynamic Range Window violation"
02/11/2020 20:24	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/11/2020 20:19	2436694061	5	"Dynamic Range Window violation"
02/11/2020 20:19	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/11/2020 20:13	2436694061	5	"Dynamic Range Window violation"
02/11/2020 20:13	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/11/2020 20:08	2436694061	5	"Dynamic Range Window violation"
02/11/2020 20:08	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/11/2020 20:03	2436694061	5	"Dynamic Range Window violation"
02/11/2020 20:03	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/11/2020 19:57	2436694061	5	"Dynamic Range Window violation"
02/11/2020 19:57	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/11/2020 19:52	2436694061	5	"Dynamic Range Window violation"
02/11/2020 19:52	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/11/2020 19:47	2436694061	5	"Dynamic Range Window violation"
02/11/2020 19:47	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/11/2020 19:41	2436694061	5	"Dynamic Range Window violation"
02/11/2020 19:41	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/11/2020 19:36	2436694061	5	"Dynamic Range Window violation"
02/11/2020 19:36	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/11/2020 19:31	2436694061	5	"Dynamic Range Window violation"
02/11/2020 19:31	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/11/2020 19:25	2436694061	5	"Dynamic Range Window violation"
02/11/2020 19:25	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/11/2020 19:20	2436694061	5	"Dynamic Range Window violation"
02/11/2020 19:20	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/11/2020 19:15	2436694061	5	"Dynamic Range Window violation"
02/11/2020 19:15	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/11/2020 19:06	2436694061	5	"Dynamic Range Window violation"
02/11/2020 19:06	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/11/2020 17:27	2436694061	5	"Dynamic Range Window violation"
02/11/2020 17:27	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/11/2020 17:27	2436694061	5	"Dynamic Range Window violation"
02/11/2020 17:27	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/11/2020 17:14	2436694061	5	"Dynamic Range Window violation"
02/11/2020 17:14	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;"

1

0

KevinM2

Former Moderator

•

1.5K Messages

@jearbear, we responded to your email regarding the traceroutes you've provided. Thank you for allowing us the opportunity to work with you on this. -Kevin

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

5 years ago

Thanks Kevin for reaching out. Playing early this morning and doing traceroute and no sign of latency issues. Seems like it is load related with the system. I will take more traceroutes tonight to see where it gets bad.

Will post my MTR overnight results. Too large of a data set to identify a specifically bad time but there is 1% of packet loss across the board (except router).

Have a feeling it is an aging system and it is what it is......

0

jearbear

Contributor

•

43 Messages

5 years ago

MTR from this morning. Common theme is lost packets @ langbprj01-ae1.rd.la.cox.net across EVERY MTR test as well as high Wrst pings.

That server looks to be owned by Cox in Virginia. The routing based off the last couple IPs are Atlanta, New York, Virginia... all East Coast. I could be wrong on the routing but I find that very interesting I'm having to hit the East Coast to play on the West Coast....

Going to dig in more...

835am 2/12/2020

162.245.206.16

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.1.1 - 0 | 4040 | 4040 | 0 | 0 | 12 | 0 |

| 10.177.0.1 - 0 | 4041 | 4041 | 4 | 10 | 220 | 9 |

| 68.6.14.178 - 1 | 4030 | 4027 | 3 | 11 | 209 | 5 |

| 100.120.108.32 - 0 | 4041 | 4041 | 4 | 13 | 206 | 15 |

| langbprj01-ae1.rd.la.cox.net - 1 | 3950 | 3926 | 9 | 18 | 272 | 13 |

| 68.105.30.138 - 0 | 4040 | 4040 | 9 | 18 | 180 | 14 |

| hosted-by.i3d.net - 0 | 4040 | 4040 | 9 | 16 | 191 | 20 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

2

0

JonathanJ

Former Moderator

•

1.9K Messages

@Jearbear

We're still seeing the 192 IP. Please bypass the router and hardwired directly to the modem and perform the traceroute.

Jonathan J
Cox Moderator

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

I will perform another tonight. It is hard for me to get the network offline for an hour. My first MTR was direct bypassing router and saw the worst packet loss.

Will perform traceroute + ping plotter.

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

5 years ago

I removed the splitter and installed a coupler. Also removed the 3db attenuator from the modem as an attempt to improve this. Things seem better. Still feels dirty but not sewage dirty. Need to look at logs and run some tests before anything conclusive.

This makes me think the power gain from removing the splitter is helping a bit... maybe. Packet loss was GOOD and now it is back to normal levels. Seems shorter lived the bad patches....

3

0

Allan

Moderator

•

2.3K Messages

@Jearbear, Please let us know the results of your tests. We will be here to help. -Allan, Cox Support Forums Moderator.

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

Did an overnight test of MTR but still connected to my router. No packet loss at the router but still packet loss in the usual areas although a lower percentage. When I get some time today I will do tracerts direct through modem.

I have no new events in my log on the modem as well as 0/0 for correctable and uncorrectable errors. Lag is still present but in shorter bursts.

Power levels below. I will replace the attenuator to help with the upstream power level.

Channel ID	Lock Status	Modulation	Frequency	Power	SNR/MER	Corrected	Uncorrectables
4	Locked	QAM256	801000000 Hz	5.5 dBmV	40.9 dB	0	0
1	Locked	QAM256	783000000 Hz	5.6 dBmV	40.6 dB	0	0
2	Locked	QAM256	789000000 Hz	5.5 dBmV	40.8 dB	0	0
3	Locked	QAM256	795000000 Hz	5.7 dBmV	41.0 dB	0	0
9	Locked	QAM256	831000000 Hz	5.0 dBmV	40.8 dB	0	0
10	Locked	QAM256	837000000 Hz	5.1 dBmV	40.8 dB	0	0
11	Locked	QAM256	843000000 Hz	5.1 dBmV	41.0 dB	0	0
12	Locked	QAM256	849000000 Hz	4.9 dBmV	40.8 dB	0	0
17	Locked	QAM256	879000000 Hz	4.8 dBmV	40.6 dB	0	0
18	Locked	QAM256	885000000 Hz	4.9 dBmV	40.9 dB	0	0
19	Locked	QAM256	891000000 Hz	4.9 dBmV	41.0 dB	0	0
20	Locked	QAM256	897000000 Hz	5.0 dBmV	41.1 dB	0	0
21	Locked	QAM256	903000000 Hz	5.1 dBmV	41.5 dB	0	0
22	Locked	QAM256	909000000 Hz	5.2 dBmV	41.5 dB	0	0
25	Locked	QAM256	927000000 Hz	5.4 dBmV	41.6 dB	0	0
26	Locked	QAM256	933000000 Hz	5.4 dBmV	41.6 dB	0	0
27	Locked	QAM256	939000000 Hz	4.9 dBmV	41.5 dB	0	0
28	Locked	QAM256	945000000 Hz	5.2 dBmV	41.5 dB	0	0
29	Locked	QAM256	951000000 Hz	5.3 dBmV	41.5 dB	0	0
30	Locked	QAM256	957000000 Hz	4.6 dBmV	41.3 dB	0	0
33	Locked	QAM256	357000000 Hz	8.0 dBmV	41.6 dB	0	0
34	Locked	QAM256	363000000 Hz	7.9 dBmV	41.7 dB	0	0
35	Locked	QAM256	369000000 Hz	7.7 dBmV	41.5 dB	0	0
36	Locked	QAM256	375000000 Hz	7.5 dBmV	41.6 dB	0	0
37	Locked	QAM256	381000000 Hz	7.8 dBmV	41.6 dB	0	0
38	Locked	QAM256	387000000 Hz	7.7 dBmV	41.5 dB	0	0
41	Locked	QAM256	405000000 Hz	8.0 dBmV	41.6 dB	0	0
42	Locked	QAM256	411000000 Hz	8.0 dBmV	41.7 dB	0	0
43	Locked	QAM256	417000000 Hz	8.1 dBmV	41.8 dB	0	0
44	Locked	QAM256	423000000 Hz	8.4 dBmV	41.9 dB	0	0
45	Locked	QAM256	429000000 Hz	8.4 dBmV	41.9 dB	0	0
46	Locked	QAM256	435000000 Hz	8.5 dBmV	42.0 dB	0	0
159	Locked	Other	300000000 Hz	10.5 dBmV	42.2 dB	333562332	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	32.0 dBmV
2	1	Locked	SC-QAM Upstream	19400000 Hz	6400000 Hz	32.0 dBmV
3	2	Locked	SC-QAM Upstream	25800000 Hz	6400000 Hz	32.0 dBmV
4	4	Locked	SC-QAM Upstream	38600000 Hz	6400000 Hz	31.0 dBmV

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

Here is log after 3db attenuator. Upstream is still on the very cusp. Speeds are a bit better. I still feel there is something wonky with my line into the house or old wiring... I know the ground tap isn't grounded, would that be causing issues?

Startup Procedure
Procedure	Status	Comment
Acquire Downstream Channel	801000000 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
4	Locked	QAM256	801000000 Hz	1.6 dBmV	40.3 dB	0	0
1	Locked	QAM256	783000000 Hz	2.0 dBmV	40.3 dB	0	0
2	Locked	QAM256	789000000 Hz	2.1 dBmV	40.4 dB	204	621
3	Locked	QAM256	795000000 Hz	1.8 dBmV	40.2 dB	301	809
9	Locked	QAM256	831000000 Hz	1.4 dBmV	40.4 dB	229	715
10	Locked	QAM256	837000000 Hz	1.5 dBmV	40.3 dB	262	727
11	Locked	QAM256	843000000 Hz	1.9 dBmV	40.6 dB	178	576
12	Locked	QAM256	849000000 Hz	1.4 dBmV	40.3 dB	191	630
17	Locked	QAM256	879000000 Hz	1.3 dBmV	40.2 dB	202	695
18	Locked	QAM256	885000000 Hz	1.6 dBmV	40.5 dB	193	651
19	Locked	QAM256	891000000 Hz	1.4 dBmV	40.7 dB	192	761
20	Locked	QAM256	897000000 Hz	1.7 dBmV	40.8 dB	223	668
21	Locked	QAM256	903000000 Hz	1.8 dBmV	41.1 dB	214	651
22	Locked	QAM256	909000000 Hz	1.7 dBmV	41.0 dB	202	785
25	Locked	QAM256	927000000 Hz	1.9 dBmV	41.2 dB	196	824
26	Locked	QAM256	933000000 Hz	1.7 dBmV	41.2 dB	218	716
27	Locked	QAM256	939000000 Hz	1.7 dBmV	41.2 dB	152	653
28	Locked	QAM256	945000000 Hz	1.7 dBmV	41.0 dB	220	771
29	Locked	QAM256	951000000 Hz	1.5 dBmV	41.1 dB	191	807
30	Locked	QAM256	957000000 Hz	1.5 dBmV	41.1 dB	159	686
33	Locked	QAM256	357000000 Hz	5.0 dBmV	41.4 dB	226	1061
34	Locked	QAM256	363000000 Hz	4.8 dBmV	41.5 dB	234	1040
35	Locked	QAM256	369000000 Hz	4.5 dBmV	41.3 dB	206	1007
36	Locked	QAM256	375000000 Hz	4.4 dBmV	41.3 dB	200	983
37	Locked	QAM256	381000000 Hz	4.6 dBmV	41.4 dB	211	1020
38	Locked	QAM256	387000000 Hz	4.5 dBmV	41.3 dB	184	1038
41	Locked	QAM256	405000000 Hz	4.9 dBmV	41.3 dB	205	1052
42	Locked	QAM256	411000000 Hz	5.0 dBmV	41.6 dB	184	1002
43	Locked	QAM256	417000000 Hz	5.1 dBmV	41.7 dB	192	1025
44	Locked	QAM256	423000000 Hz	5.3 dBmV	41.8 dB	200	997
45	Locked	QAM256	429000000 Hz	5.4 dBmV	41.8 dB	168	940
46	Locked	QAM256	435000000 Hz	5.5 dBmV	41.8 dB	173	924
159	Locked	Other	300000000 Hz	7.6 dBmV	42.0 dB	336629180	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

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

5 years ago

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 |

|------------------------------------------------|------|------|------|------|------|------|

| 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

6

0

ChrisL

Former Moderator

•

7.1K Messages

The results don't appear to show any loss at the hop you're concerned about. If loss were occurring you would see it indicated all the way through to the destination. Do you notice any performance issues outside of gaming?

-Chris

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

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;"

Like

Reply

5 years ago

0

glefever2181

New Contributor III

•

14 Messages

Packet loss and ridiculous latency on your last hop and still "we don't see anything wrong" Now I know that saying is company policy.

Like

Reply

5 years ago

0

Bruce_Niere

New Contributor III

•

37 Messages

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.

Like

Reply

5 years ago

KevinM2

Former Moderator

•

1.5K Messages

@jearbear, we are not seeing any latency issues with the ping plotter provided, nor are we see seeing any intermittent packet loss. If issues persist once the technician leaves the home, please reach out to us again in the forums or through email. -Kevin M. Cox Support Forum Moderator

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

5 years ago

Tech just left. He ran a bunch of tests and concluded there is something going on in the neighborhood wiring. He is scheduling a tech to come and inspect the neighborhood.

Directly connected to the block up the telephone pole his tester first timed out for the upload and then only got 3mbps upload. He said it should be around 38mbps.

Upload was 869mbps and he said a good reading was 1.1gbps.

Will update after the tech comes on out.

BTW here are my latest power levels. lots of errors but the upstream power is much improved. Downstream power is a little over the place.

Startup Procedure
Procedure	Status	Comment
Acquire Downstream Channel	831000000 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
9	Locked	QAM256	831000000 Hz	0.9 dBmV	40.5 dB	36	163
1	Locked	QAM256	783000000 Hz	1.3 dBmV	40.3 dB	344	1505
2	Locked	QAM256	789000000 Hz	1.4 dBmV	40.4 dB	331	1417
3	Locked	QAM256	795000000 Hz	1.2 dBmV	40.4 dB	383	1473
4	Locked	QAM256	801000000 Hz	1.1 dBmV	40.4 dB	371	1439
10	Locked	QAM256	837000000 Hz	0.9 dBmV	40.4 dB	398	1425
11	Locked	QAM256	843000000 Hz	1.1 dBmV	40.8 dB	371	1427
12	Locked	QAM256	849000000 Hz	0.8 dBmV	40.3 dB	370	1445
17	Locked	QAM256	879000000 Hz	0.5 dBmV	40.2 dB	814	2064
18	Locked	QAM256	885000000 Hz	0.9 dBmV	40.7 dB	316	1378
19	Locked	QAM256	891000000 Hz	0.8 dBmV	40.7 dB	343	1380
20	Locked	QAM256	897000000 Hz	0.8 dBmV	40.9 dB	289	1357
21	Locked	QAM256	903000000 Hz	1.1 dBmV	41.2 dB	333	1358
22	Locked	QAM256	909000000 Hz	0.8 dBmV	41.0 dB	420	1518
25	Locked	QAM256	927000000 Hz	1.0 dBmV	41.1 dB	304	1284
26	Locked	QAM256	933000000 Hz	0.7 dBmV	41.0 dB	345	1399
27	Locked	QAM256	939000000 Hz	0.7 dBmV	41.0 dB	338	1209
28	Locked	QAM256	945000000 Hz	0.6 dBmV	40.9 dB	338	1355
29	Locked	QAM256	951000000 Hz	0.5 dBmV	40.8 dB	274	1325
30	Locked	QAM256	957000000 Hz	0.4 dBmV	41.1 dB	375	1358
33	Locked	QAM256	357000000 Hz	4.4 dBmV	41.4 dB	404	1765
34	Locked	QAM256	363000000 Hz	4.2 dBmV	41.5 dB	418	1633
35	Locked	QAM256	369000000 Hz	3.9 dBmV	41.4 dB	394	1563
36	Locked	QAM256	375000000 Hz	4.0 dBmV	41.3 dB	407	1699
37	Locked	QAM256	381000000 Hz	4.2 dBmV	41.6 dB	383	1645
38	Locked	QAM256	387000000 Hz	4.1 dBmV	41.4 dB	352	1581
41	Locked	QAM256	405000000 Hz	4.5 dBmV	41.4 dB	319	1608
42	Locked	QAM256	411000000 Hz	4.7 dBmV	41.7 dB	353	1644
43	Locked	QAM256	417000000 Hz	4.7 dBmV	41.8 dB	426	1576
44	Locked	QAM256	423000000 Hz	4.9 dBmV	41.8 dB	350	1526
45	Locked	QAM256	429000000 Hz	5.0 dBmV	41.9 dB	390	1630
46	Locked	QAM256	435000000 Hz	5.0 dBmV	41.9 dB	384	1578
159	Locked	Other	300000000 Hz	6.9 dBmV	42.0 dB	518010997	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	44.0 dBmV
2	1	Locked	SC-QAM Upstream	19400000 Hz	6400000 Hz	44.0 dBmV
3	2	Locked	SC-QAM Upstream	25800000 Hz	6400000 Hz	44.0 dBmV
4	4	Locked	SC-QAM Upstream	38600000 Hz	6400000 Hz	44.0 dBmV

0

jearbear

Contributor

•

43 Messages

5 years ago

Everybody

Ping plotter update here. This is on my WIFI with a MacBook Pro, the results are obvious. The reseating of everything and QC on the pole at the block was a huge help. Cox, not to be a total D, this is why just a line tech coming out is a huge deal in these aging neighborhoods.

Look at this (the latency is so AVERAGE!):

2

0

KevinM2

Former Moderator

•

1.5K Messages

Jearbear, please reach out to us once the maintenance team completes the work in the area if you're still experiencing issues with our service. I am not seeing any issues with the PingPlotter or traceroute you've provided. -Kevin M. Cox Support Forum Moderator

Like

Reply

5 years ago

0

Bruce_Niere

New Contributor III

•

37 Messages

I was going to point out that you have 2 packet losses there and huge ping spikes. those ruin games.

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

5 years ago

Well I was completely unable to play any games online last night due to lag and packet loss. Looks like my good times were short lived.

Here is my ping plotter. I'll upload a couple more once I look through the graph as I am testing for 24 hours.

Hopefully that maintenance crew comes out sooner rather than later.......

0

jearbear

Contributor

•

43 Messages

5 years ago

Well I can't play any games tonight either. Nonstop packet loss and lag and my speeds seem to be all over the place. Ping plotters from my Mac hardwired to router since I can't give up wifi for hours.

This is ludicrous.

Here is a 24 hour ping plotter. Quiet from 12a-830a or so, looks like congestion... Cox - what is happening from 12a - 830a?

3

KevinM2

Former Moderator

•

1.5K Messages

Hi Jearbear, this is still being investigated and worked on by our maintenance teams. -Kevin M. Cox Support Forum Moderator

Like

Reply

5 years ago

0

jearbear

Contributor

•

43 Messages

Cool thanks for the update. For now I'll be posting 24 hour plotters to help diagnose the problem.

Like

Reply

5 years ago

0

anon247

New Contributor

•

3 Messages

Where are you located? I have the same hardware as you (SB8200) and just upgraded to Gigablast 2 weeks ago. Ever since upgrading, I have noticed packet loss at similar times that you are experiencing them. I didn't have issues before when I was paying less for slower speed. Last night I couldn't hold a steady connection and dc'ed from multiple games. This has been happening on and off for 2 weeks straight.

Like

Reply

5 years ago

0

Welcome to the Cox Community

jearbear

Packet loss/bad connection Rocket League

jearbear

deorlol

KevinM2

deorlol

KevinM2

jearbear

jearbear

jearbear

MarkM1

Tierdisogni

jearbear

jearbear

Tierdisogni

jearbear

jearbear

jearbear

jearbear

jearbear

jearbear

KevinM2

jearbear

jearbear

JonathanJ

jearbear

jearbear

Allan

jearbear

jearbear

jearbear

ChrisL

jearbear

glefever2181

Bruce_Niere

KevinM2

jearbear

jearbear

KevinM2

Bruce_Niere

jearbear

jearbear

KevinM2

jearbear

anon247

Related Content

Recent Discussions