Question Outbound Packet Loss (Wired Connection)

Cj87 · Apr 9, 2022

I have been PLAGUED with this outbound packet loss issue for as long as I can remember.

As for solutions: I have accumulated days in google searches, youtube videos, forum posts, hardware changes, service technicians out, pings, tracerts; anything you can think of.
Nothing I've done so far has brought me to a conclusion or answer and I'm kinda just lost at this point.

I frequently have 10-50% outbound packet loss in the middle of ANY game. This evidently spikes my ping (MS) up to the 100MS+ end on most games and up to even 500MS on minecraft for some reason. (Valorant, Apex Legends, CS:GO, You name it.) It's visible in everything I do gaming-wise even Twitch streams have been buffering. This happens to me the entire 30-40min matches and I am just over it. I can't enjoy anything that I have paid for regarding to my new computer and internet hardware.

Xfinity had 2 or 3 different visits to my house a few months back where they replaced a Coax running from the street to the house and I believe the Coax inside my room where the Modem & Router sit. On the last visit they arranged for a Bucket Truck to fix something with the Node on the Pole outside. However even after that I still continue to see issues on my end. To add to this I just had a 4th visit yesterday and the guy found 10+ year old Direct TV cables that were an old chewed up mess. He rerouted new cable around the house to the inside of the wall to my room being very confident this should fix my packet loss issue; however it did not.

Edit: They're even coming again Tuesday so they really seem interested in fixing the problem and every visit has been free.

My hardware:
RAX48 AX6 Netgear Router (aka Nighthawk AX5200)
CM1000 3.1 Netgear Modem

As for Internet Speed:

I've even gone as far as to use brand new CAT6 ethernet cables. I'm pretty much out of ideas and feel like I'm just dishing money down an endless abyss.

These are the power levels to my modem currently.. not sure what any of it means but yeah if theres any other info I can inject please let me know.

Cable Connection

Apply Cancel

Frequency start Value

This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.

Starting Frequency

Startup Procedure

Procedure	Status	Comment
Acquire Downstream Channel	711000000 Hz	Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Security	Enable	BPI+
IP Provisioning Mode	Honor MDD	IPv6 only

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR / MER	Unerrored Codewords	Correctable Codewords	Uncorrectable Codewords
1	Locked	QAM256	44	711000000 Hz	0.7 dBmV	45.2 dB	302986961	0	0
2	Locked	QAM256	13	525000000 Hz	0.6 dBmV	46.8 dB	301789846	0	0
3	Locked	QAM256	14	531000000 Hz	0.4 dBmV	46.6 dB	301793587	0	0
4	Locked	QAM256	15	537000000 Hz	0.5 dBmV	46.6 dB	301773730	0	0
5	Locked	QAM256	16	543000000 Hz	0.4 dBmV	46.4 dB	301801177	0	0
6	Locked	QAM256	17	549000000 Hz	0.3 dBmV	46.4 dB	301804509	0	0
7	Locked	QAM256	18	555000000 Hz	0.3 dBmV	46.3 dB	301808423	0	0
8	Locked	QAM256	19	561000000 Hz	0.2 dBmV	46.3 dB	301811886	0	0
9	Locked	QAM256	20	567000000 Hz	0.3 dBmV	46.2 dB	301816048	0	0
10	Locked	QAM256	21	573000000 Hz	0.1 dBmV	46.0 dB	301819816	0	0
11	Locked	QAM256	22	579000000 Hz	0.3 dBmV	46.3 dB	301823807	0	0
12	Locked	QAM256	23	585000000 Hz	0.1 dBmV	46.1 dB	301821746	0	0
13	Locked	QAM256	24	591000000 Hz	0.1 dBmV	45.9 dB	301825436	0	0
14	Locked	QAM256	25	597000000 Hz	0.2 dBmV	45.9 dB	301829513	0	0
15	Locked	QAM256	26	603000000 Hz	0.0 dBmV	45.8 dB	301832676	0	0
16	Locked	QAM256	27	609000000 Hz	0.1 dBmV	45.8 dB	301837210	0	0
17	Locked	QAM256	28	615000000 Hz	0.0 dBmV	45.7 dB	301840181	0	0
18	Locked	QAM256	29	621000000 Hz	0.0 dBmV	45.7 dB	301844224	0	0
19	Locked	QAM256	30	627000000 Hz	0.2 dBmV	45.6 dB	301847745	0	0
20	Locked	QAM256	31	633000000 Hz	0.1 dBmV	45.7 dB	301851936	0	0
21	Locked	QAM256	32	639000000 Hz	0.2 dBmV	45.8 dB	301855210	0	0
22	Locked	QAM256	33	645000000 Hz	0.2 dBmV	45.7 dB	301855683	0	0
23	Locked	QAM256	34	651000000 Hz	0.2 dBmV	45.7 dB	301861506	0	0
24	Locked	QAM256	35	657000000 Hz	0.3 dBmV	45.6 dB	301864532	0	0
25	Locked	QAM256	36	663000000 Hz	0.4 dBmV	45.8 dB	301870254	0	0
26	Locked	QAM256	37	669000000 Hz	0.4 dBmV	45.6 dB	301873745	0	0
27	Locked	QAM256	38	675000000 Hz	0.5 dBmV	44.8 dB	301877883	0	0
28	Locked	QAM256	39	681000000 Hz	0.4 dBmV	45.7 dB	301881163	0	0
29	Locked	QAM256	40	687000000 Hz	0.5 dBmV	45.6 dB	301885399	0	0
30	Locked	QAM256	41	693000000 Hz	0.6 dBmV	45.7 dB	301888713	0	0
31	Locked	QAM256	42	699000000 Hz	0.5 dBmV	45.6 dB	301910892	0	0
32	Locked	QAM256	43	705000000 Hz	0.6 dBmV	45.8 dB	301891402	0	0

Upstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power
1	Locked	ATDMA	1	35600000 Hz	46.0 dBmV
2	Locked	ATDMA	2	29200000 Hz	48.0 dBmV
3	Locked	ATDMA	3	22800000 Hz	45.8 dBmV
4	Locked	ATDMA	4	16400000 Hz	45.5 dBmV
5	Not Locked	Unknown	0	0 Hz	0.0 dBmV
6	Not Locked	Unknown	0	0 Hz	0.0 dBmV
7	Not Locked	Unknown	0	0 Hz	0.0 dBmV
8	Not Locked	Unknown	0	0 Hz	0.0 dBmV

Downstream OFDM Channels

Channel	Lock Status	Modulation / Profile ID	Channel ID	Frequency	Power	SNR / MER	Active Subcarrier Number Range	Unerrored Codewords	Correctable Codewords	Uncorrectable Codewords
1	Locked	0, 1	193	762000000 Hz	1.3 dBmV	44.3 dB	1108 ~ 2987	78206741	77724259	0
2	Not Locked	0	0	0 Hz	-0.2 dBmV	0.0 dB	0 ~ 4095	0	0	0

Upstream OFDMA Channels

Channel	Lock Status	Modulation / Profile ID	Channel ID	Frequency	Power
1	Not Locked	Unknown	0	0 Hz	0 dBmV
2	Not Locked	Unknown	0	0 Hz	0 dBmV

Current System Time: Sat Apr 09 19:12:46 2022

System Up Time: 1:51:30

EVENT LOGS:

Time	Priority	Description
2022-04-09, 22:24:51	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:90:f0:57:00:00;CM-QOS=1.1;CM-VER=3.1;
2022-04-09, 22:24:21	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1.;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:90:f0:57:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2022-04-09, 22:21:31	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:90:f0:57:00:00;CM-QOS=1.1;CM-VER=3.1;

bill001g · Apr 9, 2022

So why do you think it is "OUTBOUND" packet loss.

Generally if there is some issue with the upload path you will see high power values in upstream. Yours look very good.

There is some loss in the downstream on 2 channels. It seems there is some kind of interference near the 700mhz range.

If your ISP can actually see this you think they could fix it. Are there errors in the log on the modem. Things like sync error or ranging errors.

The ISP equipment gives much more detail about the quality of the connection that anything you can see. If they did not see issues they would not have replaced cables.

In any case there is not much you can do. If you can ping your router IP and never get loss that pretty much shows everything you are in control of works. You would want to ping the ISP first router,generally hop 2 in a trace. You would then show the ISP it is good to your router but has issuses to their router. If they are coming out again that generally means they can see the packet loss from their office. Normally if they test and see no issues it is very hard to convince them to come out.

Cj87 · Apr 9, 2022

bill001g said:
So why do you think it is "OUTBOUND" packet loss.

Generally if there is some issue with the upload path you will see high power values in upstream. Yours look very good.

There is some loss in the downstream on 2 channels. It seems there is some kind of interference near the 700mhz range.

If your ISP can actually see this you think they could fix it. Are there errors in the log on the modem. Things like sync error or ranging errors.

The ISP equipment gives much more detail about the quality of the connection that anything you can see. If they did not see issues they would not have replaced cables.

In any case there is not much you can do. If you can ping your router IP and never get loss that pretty much shows everything you are in control of works. You would want to ping the ISP first router,generally hop 2 in a trace. You would then show the ISP it is good to your router but has issuses to their router. If they are coming out again that generally means they can see the packet loss from their office. Normally if they test and see no issues it is very hard to convince them to come out.

Any competitive game has statistics to display these types of datas (Inbound Packet Loss, Outbound Packet Loss, Total Packet Loss, Etc..) And anytime the spike happens it is labeling it as Outbound Packet loss ranging up to 50%. This causes my MS to shoot up as well, creating rubberband and input lag. Do you want me to show these tables to Comcast? Because I have a thread with the same exact tables on their forums but nobody has responded anyways other than telling me to PM them which I have been for awhile. But yeah I forgot the commands for cmd to do the thing you want

Event Log

Time	Priority	Description
2022-04-09, 17:24:18	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:90:f0:57:00:00;CM-QOS=1.1;CM-VER=3.1;
2022-04-09, 17:22:00	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1.;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:90:f0:57:00:00;CM-QOS=1.1;CM-VER=3.1;
2022-04-09, 17:21:59	Critical (3)	REG RSP not received;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:90:f0:57:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:90:f0:57:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

[TD]

Clear Log Refresh

[/TD]

[TD][/TD]

Cj87 · Apr 9, 2022

@bill001g
The other table was outdated this one is as of today. Sorry about that.

Cable Connection

Apply Cancel

Frequency start Value

This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.

Starting Frequency

Startup Procedure

Procedure	Status	Comment
Acquire Downstream Channel	711000000 Hz	Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Security	Enable	BPI+
IP Provisioning Mode	Honor MDD	IPv6 only

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR / MER	Unerrored Codewords	Correctable Codewords	Uncorrectable Codewords
1	Locked	QAM256	44	711000000 Hz	0.7 dBmV	45.2 dB	302986961	0	0
2	Locked	QAM256	13	525000000 Hz	0.6 dBmV	46.8 dB	301789846	0	0
3	Locked	QAM256	14	531000000 Hz	0.4 dBmV	46.6 dB	301793587	0	0
4	Locked	QAM256	15	537000000 Hz	0.5 dBmV	46.6 dB	301773730	0	0
5	Locked	QAM256	16	543000000 Hz	0.4 dBmV	46.4 dB	301801177	0	0
6	Locked	QAM256	17	549000000 Hz	0.3 dBmV	46.4 dB	301804509	0	0
7	Locked	QAM256	18	555000000 Hz	0.3 dBmV	46.3 dB	301808423	0	0
8	Locked	QAM256	19	561000000 Hz	0.2 dBmV	46.3 dB	301811886	0	0
9	Locked	QAM256	20	567000000 Hz	0.3 dBmV	46.2 dB	301816048	0	0
10	Locked	QAM256	21	573000000 Hz	0.1 dBmV	46.0 dB	301819816	0	0
11	Locked	QAM256	22	579000000 Hz	0.3 dBmV	46.3 dB	301823807	0	0
12	Locked	QAM256	23	585000000 Hz	0.1 dBmV	46.1 dB	301821746	0	0
13	Locked	QAM256	24	591000000 Hz	0.1 dBmV	45.9 dB	301825436	0	0
14	Locked	QAM256	25	597000000 Hz	0.2 dBmV	45.9 dB	301829513	0	0
15	Locked	QAM256	26	603000000 Hz	0.0 dBmV	45.8 dB	301832676	0	0
16	Locked	QAM256	27	609000000 Hz	0.1 dBmV	45.8 dB	301837210	0	0
17	Locked	QAM256	28	615000000 Hz	0.0 dBmV	45.7 dB	301840181	0	0
18	Locked	QAM256	29	621000000 Hz	0.0 dBmV	45.7 dB	301844224	0	0
19	Locked	QAM256	30	627000000 Hz	0.2 dBmV	45.6 dB	301847745	0	0
20	Locked	QAM256	31	633000000 Hz	0.1 dBmV	45.7 dB	301851936	0	0
21	Locked	QAM256	32	639000000 Hz	0.2 dBmV	45.8 dB	301855210	0	0
22	Locked	QAM256	33	645000000 Hz	0.2 dBmV	45.7 dB	301855683	0	0
23	Locked	QAM256	34	651000000 Hz	0.2 dBmV	45.7 dB	301861506	0	0
24	Locked	QAM256	35	657000000 Hz	0.3 dBmV	45.6 dB	301864532	0	0
25	Locked	QAM256	36	663000000 Hz	0.4 dBmV	45.8 dB	301870254	0	0
26	Locked	QAM256	37	669000000 Hz	0.4 dBmV	45.6 dB	301873745	0	0
27	Locked	QAM256	38	675000000 Hz	0.5 dBmV	44.8 dB	301877883	0	0
28	Locked	QAM256	39	681000000 Hz	0.4 dBmV	45.7 dB	301881163	0	0
29	Locked	QAM256	40	687000000 Hz	0.5 dBmV	45.6 dB	301885399	0	0
30	Locked	QAM256	41	693000000 Hz	0.6 dBmV	45.7 dB	301888713	0	0
31	Locked	QAM256	42	699000000 Hz	0.5 dBmV	45.6 dB	301910892	0	0
32	Locked	QAM256	43	705000000 Hz	0.6 dBmV	45.8 dB	301891402	0	0

Upstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power
1	Locked	ATDMA	1	35600000 Hz	46.0 dBmV
2	Locked	ATDMA	2	29200000 Hz	48.0 dBmV
3	Locked	ATDMA	3	22800000 Hz	45.8 dBmV
4	Locked	ATDMA	4	16400000 Hz	45.5 dBmV
5	Not Locked	Unknown	0	0 Hz	0.0 dBmV
6	Not Locked	Unknown	0	0 Hz	0.0 dBmV
7	Not Locked	Unknown	0	0 Hz	0.0 dBmV
8	Not Locked	Unknown	0	0 Hz	0.0 dBmV

Downstream OFDM Channels

Channel	Lock Status	Modulation / Profile ID	Channel ID	Frequency	Power	SNR / MER	Active Subcarrier Number Range	Unerrored Codewords	Correctable Codewords	Uncorrectable Codewords
1	Locked	0, 1	193	762000000 Hz	1.3 dBmV	44.3 dB	1108 ~ 2987	78206741	77724259	0
2	Not Locked	0	0	0 Hz	-0.2 dBmV	0.0 dB	0 ~ 4095	0	0	0

Upstream OFDMA Channels

Channel	Lock Status	Modulation / Profile ID	Channel ID	Frequency	Power
1	Not Locked	Unknown	0	0 Hz	0 dBmV
2	Not Locked	Unknown	0	0 Hz	0 dBmV

Current System Time: Sat Apr 09 19:12:46 2022

System Up Time: 1:51:30

[TD][/TD]

vov4ik_il · Apr 9, 2022

Looks like cable uplink problem, might be anything from a bad modem or coax connector to a bad CMTS interface card.

Cj87 · Apr 9, 2022

vov4ik_il said:
Looks like cable uplink problem, might be anything from a bad modem or coax connector to a bad CMTS interface card.

Every Coax in or outside of the building was replaced yesterday.
Well funny thing is the issue was here with my old Router and Modem and is Still here with a brand new $400 netgear router & modem. However what is a CMTS Interface Card? Where is this located or is it an ISP thing?

Cj87 · Apr 10, 2022

kanewolf said:
That says you have a couple of Wyze devices and maybe an Alexa or Fire (tablet, TV, etc) device that don't have the correct WIFI credentials.

Ah I was leaning towards that lol. Just recently restored to factory settings on both my modem and router hoping a refresh would do something. Still packet loss issue. And even after a brand new computer/coax cables from xfinity/cat6 ethernet coords/modem/router you'd think something would have been found by now. They want to come again for free which would be a 5th visit... fingers crossed I can't even think of anything else they could do

Also customer support was unable to Send a Refresh Signal or Reboot if you will and I figure it's due to these errors below.

2022-04-09, 22:24:51	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:90:f0:57:00:00;CM-QOS=1.1;CM-VER=3.1;
2022-04-09, 22:24:21	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1.;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:90:f0:57:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2022-04-09, 22:21:31	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c💿d6:8e:3d:64;CMTS-MAC=00:90:f0:57:00:00;CM-QOS=1.1;CM-VER=3.1;

vov4ik_il · Apr 10, 2022

Cj87 said:
However what is a CMTS Interface Card? Where is this located or is it an ISP thing?

CMTS cage is on the ISP side, terminating endpoint modems (like yours), it is not complicated but lots of hassle to go test every segment between your house.
The log is not very useful, need rf tap/analyzer to verify two way communication between the modem and cmts in every junction on the way. It is a job…

Cj87 · Apr 10, 2022

vov4ik_il said:
CMTS cage is on the ISP side, terminating endpoint modems (like yours), it is not complicated but lots of hassle to go test every segment.

Gotcha. Well I'd figure it'd be a hassle to have to come out to my house 5 times for free that they'd maybe want to look deeper. Online gaming was pretty much impossible today too the worst its been.

bill001g · Apr 10, 2022

I would be careful about using stuff games tell you about network. Many times the game code itself is having a problem or there is some problem in say the game company ISP. I mean if I was your ISP I could just as easily blame a bad cable in the game companies ISP.

To really test this you want a simple ping command. Just run tracert to 8.8.8.8 and then leave a constant ping run to ip in hop2. That almost always is the ISP equipment near your house and tests the cable between your house and the ISP.

You should also see very few if any things like sync errors in the log. These almost always are a ISP problem especially if you replaced the modem.

Cj87 · Apr 10, 2022

bill001g said:
I would be careful about using stuff games tell you about network. Many times the game code itself is having a problem or there is some problem in say the game company ISP. I mean if I was your ISP I could just as easily blame a bad cable in the game companies ISP.

To really test this you want a simple ping command. Just run tracert to 8.8.8.8 and then leave a constant ping run to ip in hop2. That almost always is the ISP equipment near your house and tests the cable between your house and the ISP.

You should also see very few if any things like sync errors in the log. These almost always are a ISP problem especially if you replaced the modem.

Ok not sure if this is right but am I using the right IP? https://prnt.sc/k438nHZ8tF1Z

https://prnt.sc/BTI2vyFBAMaP seems like it is dropping connection constantly now

bill001g · Apr 10, 2022

You got lucky/unlucky with that trace and it show packet loss. Many times the loss is so random it does not show.

In any case it is hop 2 that you want to run constant ping on. Hopefully it will respond to ping commands, sometime the ISP has disabled this.

This looks pretty bad when it shows on the trace like this. In addition to getting loss, "the * means loss", you are getting random higher random latency on that hop. Key here is because hop 1 is good and hop 2 is bad it pretty much proves there is a ISP line problem. With simple commands the ISP can not blame the game or another ISP

Cj87 · Apr 10, 2022

bill001g said:
You got lucky/unlucky with that trace and it show packet loss. Many times the loss is so random it does not show.

In any case it is hop 2 that you want to run constant ping on. Hopefully it will respond to ping commands, sometime the ISP has disabled this.

This looks pretty bad when it shows on the trace like this. In addition to getting loss, "the * means loss", you are getting random higher random latency on that hop. Key here is because hop 1 is good and hop 2 is bad it pretty much proves there is a ISP line problem. With simple commands the ISP can not blame the game or another ISP

Okay. So I did do it right? Or no haha? https://prnt.sc/cFaHKRoaBKW- I crossed out my IP hopefully. I will show this to comcast.

bill001g · Apr 10, 2022

Would be better if there router with the 10.x.x.x IP responded but this does show the problem. The problem still is likely between your house and 10.x.x.x router but you have not way to test that when the ISP block ping to that device.

kanewolf · Apr 10, 2022

bill001g said:
Would be better if there router with the 10.x.x.x IP responded but this does show the problem. The problem still is likely between your house and 10.x.x.x router but you have not way to test that when the ISP block ping to that device.

Unusual that a 10.x.y.z would be first hop with Xfiniti cable. I guess they are running out of IP addresses.

Cj87 · Apr 10, 2022

Well I sent over the prnscr to them to attach to notes for the technician. They said they're very diligent on fixing this problem

Meanwhile: This just happened while frozen in place in a game https://prnt.sc/M0BuGHB6AGsJ and my resource monitor: https://prnt.sc/DTTD4pKfApse

Cj87 · Apr 23, 2022

I compiled a notepad file of my power levels through out letting it go all day til it starts making me lag and then rebooting and rechecking the channels.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 567000000 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
20 Locked QAM256 567000000 Hz -1 dBmV 45 dB 0 0
13 Locked QAM256 525000000 Hz -1 dBmV 45 dB 0 0
14 Locked QAM256 531000000 Hz -1 dBmV 45 dB 0 0
15 Locked QAM256 537000000 Hz -1 dBmV 45 dB 0 0
16 Locked QAM256 543000000 Hz -1 dBmV 45 dB 0 0
17 Locked QAM256 549000000 Hz -1 dBmV 45 dB 0 0
18 Locked QAM256 555000000 Hz -1 dBmV 45 dB 0 0
19 Locked QAM256 561000000 Hz -1 dBmV 45 dB 0 0
21 Locked QAM256 573000000 Hz -1 dBmV 45 dB 0 0
22 Locked QAM256 579000000 Hz -1 dBmV 45 dB 0 0
23 Locked QAM256 585000000 Hz -1 dBmV 45 dB 0 0
24 Locked QAM256 591000000 Hz -1 dBmV 45 dB 0 0
25 Locked QAM256 597000000 Hz -1 dBmV 45 dB 0 0
26 Locked QAM256 603000000 Hz -1 dBmV 45 dB 0 0
27 Locked QAM256 609000000 Hz -1 dBmV 45 dB 0 0
28 Locked QAM256 615000000 Hz -1 dBmV 45 dB 0 0
29 Locked QAM256 621000000 Hz -1 dBmV 45 dB 0 0
30 Locked QAM256 627000000 Hz -1 dBmV 45 dB 0 0
31 Locked QAM256 633000000 Hz -1 dBmV 45 dB 0 0
32 Locked QAM256 639000000 Hz -1 dBmV 45 dB 0 0
33 Locked QAM256 645000000 Hz -1 dBmV 45 dB 0 0
34 Locked QAM256 651000000 Hz -1 dBmV 45 dB 0 0
35 Locked QAM256 657000000 Hz -1 dBmV 45 dB 0 0
36 Locked QAM256 663000000 Hz -1 dBmV 45 dB 0 0
37 Locked QAM256 669000000 Hz -1 dBmV 45 dB 0 0
38 Locked QAM256 675000000 Hz -1 dBmV 44 dB 0 0
39 Locked QAM256 681000000 Hz -1 dBmV 45 dB 0 0
40 Locked QAM256 687000000 Hz -1 dBmV 45 dB 0 0
41 Locked QAM256 693000000 Hz -1 dBmV 45 dB 0 0
42 Locked QAM256 699000000 Hz -1 dBmV 45 dB 0 0
43 Locked QAM256 705000000 Hz -1 dBmV 44 dB 0 0
44 Locked QAM256 711000000 Hz -1 dBmV 44 dB 0 0
193 Locked OFDM PLC 762000000 Hz 0 dBmV 44 dB 270942456 0

Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
1 Locked SC-QAM 35600000 Hz 6400000 45.3 dBmV
2 Locked SC-QAM 29200000 Hz 6400000 45.3 dBmV
3 Locked SC-QAM 22800000 Hz 6400000 45.3 dBmV
4 Locked SC-QAM 16400000 Hz 6400000 45.3 dBmV

Current System Time:Sat Apr 23 11:10:01 2022

============================================================================================================================================================================

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 567000000 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
20 Locked QAM256 567000000 Hz -1 dBmV 45 dB 0 0
1 Locked QAM256 447000000 Hz 0 dBmV 46 dB 0 0
2 Locked QAM256 453000000 Hz 0 dBmV 46 dB 0 0
3 Locked QAM256 459000000 Hz 0 dBmV 46 dB 0 0
4 Locked QAM256 465000000 Hz 0 dBmV 46 dB 0 0
5 Locked QAM256 471000000 Hz 0 dBmV 46 dB 0 0
6 Locked QAM256 477000000 Hz 0 dBmV 46 dB 0 0
7 Locked QAM256 483000000 Hz 0 dBmV 46 dB 0 0
8 Locked QAM256 489000000 Hz 0 dBmV 45 dB 0 0
9 Locked QAM256 495000000 Hz 0 dBmV 45 dB 0 0
10 Locked QAM256 507000000 Hz -1 dBmV 45 dB 0 0
11 Locked QAM256 513000000 Hz -1 dBmV 45 dB 0 0
12 Locked QAM256 519000000 Hz -1 dBmV 45 dB 0 0
13 Locked QAM256 525000000 Hz -1 dBmV 45 dB 0 0
14 Locked QAM256 531000000 Hz -1 dBmV 45 dB 0 0
15 Locked QAM256 537000000 Hz -1 dBmV 45 dB 0 0
16 Locked QAM256 543000000 Hz -1 dBmV 45 dB 0 0
17 Locked QAM256 549000000 Hz -1 dBmV 45 dB 0 0
18 Locked QAM256 555000000 Hz -1 dBmV 45 dB 0 0
19 Locked QAM256 561000000 Hz -1 dBmV 45 dB 0 0
21 Locked QAM256 573000000 Hz -1 dBmV 45 dB 0 0
22 Locked QAM256 579000000 Hz -1 dBmV 45 dB 0 0
23 Locked QAM256 585000000 Hz -1 dBmV 45 dB 0 0
24 Locked QAM256 591000000 Hz -1 dBmV 45 dB 0 0
25 Locked QAM256 597000000 Hz -1 dBmV 45 dB 0 0
26 Locked QAM256 603000000 Hz -1 dBmV 45 dB 0 0
27 Locked QAM256 609000000 Hz -1 dBmV 45 dB 0 0
28 Locked QAM256 615000000 Hz -1 dBmV 45 dB 0 0
29 Locked QAM256 621000000 Hz -1 dBmV 45 dB 0 0
30 Locked QAM256 627000000 Hz -1 dBmV 45 dB 0 0
31 Locked QAM256 633000000 Hz -1 dBmV 45 dB 0 0
32 Locked QAM256 639000000 Hz -1 dBmV 45 dB 0 0
193 Locked OFDM PLC 762000000 Hz 0 dBmV 44 dB 923508 0

Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
1 Locked SC-QAM 35600000 Hz 6400000 45.5 dBmV
2 Locked SC-QAM 29200000 Hz 6400000 45.3 dBmV
3 Locked SC-QAM 22800000 Hz 6400000 45.8 dBmV
4 Locked SC-QAM 16400000 Hz 6400000 45.3 dBmV

Current System Time:Sat Apr 23 11:15:37 2022

Cj87 · Apr 23, 2022

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 465000000 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 465000000 Hz 0 dBmV 46 dB 154 719
1 Locked QAM256 447000000 Hz 0 dBmV 46 dB 0 0
2 Locked QAM256 453000000 Hz 0 dBmV 46 dB 0 0
3 Locked QAM256 459000000 Hz 0 dBmV 45 dB 0 0
5 Locked QAM256 471000000 Hz 0 dBmV 46 dB 0 0
6 Locked QAM256 477000000 Hz 0 dBmV 45 dB 0 0
7 Locked QAM256 483000000 Hz 0 dBmV 46 dB 0 0
8 Locked QAM256 489000000 Hz 0 dBmV 45 dB 6 0
9 Locked QAM256 495000000 Hz 0 dBmV 45 dB 116 0
10 Locked QAM256 507000000 Hz 0 dBmV 46 dB 15 0
11 Locked QAM256 513000000 Hz 0 dBmV 45 dB 0 0
12 Locked QAM256 519000000 Hz 0 dBmV 45 dB 0 0
13 Locked QAM256 525000000 Hz 0 dBmV 45 dB 0 0
14 Locked QAM256 531000000 Hz 0 dBmV 45 dB 0 0
15 Locked QAM256 537000000 Hz 0 dBmV 45 dB 0 0
16 Locked QAM256 543000000 Hz 0 dBmV 45 dB 0 0
17 Locked QAM256 549000000 Hz 0 dBmV 45 dB 0 0
18 Locked QAM256 555000000 Hz 0 dBmV 45 dB 0 0
19 Locked QAM256 561000000 Hz 0 dBmV 45 dB 0 0
20 Locked QAM256 567000000 Hz 0 dBmV 45 dB 0 0
21 Locked QAM256 573000000 Hz 0 dBmV 45 dB 0 0
22 Locked QAM256 579000000 Hz 0 dBmV 45 dB 0 0
23 Locked QAM256 585000000 Hz 0 dBmV 45 dB 0 0
24 Locked QAM256 591000000 Hz 0 dBmV 45 dB 0 0
25 Locked QAM256 597000000 Hz 0 dBmV 45 dB 0 0
26 Locked QAM256 603000000 Hz 0 dBmV 45 dB 0 0
27 Locked QAM256 609000000 Hz 0 dBmV 45 dB 0 0
28 Locked QAM256 615000000 Hz 0 dBmV 45 dB 0 0
29 Locked QAM256 621000000 Hz 0 dBmV 45 dB 0 0
30 Locked QAM256 627000000 Hz 0 dBmV 45 dB 0 0
31 Locked QAM256 633000000 Hz 0 dBmV 45 dB 0 0
32 Locked QAM256 639000000 Hz 0 dBmV 45 dB 0 0
193 Locked OFDM PLC 762000000 Hz 1 dBmV 45 dB 450226662 0

Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
1 Locked SC-QAM 35600000 Hz 6400000 45.0 dBmV
2 Locked SC-QAM 29200000 Hz 6400000 45.3 dBmV
3 Locked SC-QAM 22800000 Hz 6400000 45.5 dBmV
4 Locked SC-QAM 16400000 Hz 6400000 45.3 dBmV

Current System Time:Tue Apr 19 17:16:20 2022

============================================================================================================================================================================

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 465000000 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 465000000 Hz 0 dBmV 46 dB 0 0
1 Locked QAM256 447000000 Hz 0 dBmV 46 dB 0 0
2 Locked QAM256 453000000 Hz 0 dBmV 46 dB 0 0
3 Locked QAM256 459000000 Hz 0 dBmV 46 dB 0 0
5 Locked QAM256 471000000 Hz 0 dBmV 45 dB 0 0
6 Locked QAM256 477000000 Hz 0 dBmV 45 dB 0 0
7 Locked QAM256 483000000 Hz 0 dBmV 45 dB 0 0
8 Locked QAM256 489000000 Hz 0 dBmV 45 dB 2 0
9 Locked QAM256 495000000 Hz 0 dBmV 45 dB 78 0
10 Locked QAM256 507000000 Hz 0 dBmV 45 dB 12 0
11 Locked QAM256 513000000 Hz 0 dBmV 46 dB 0 0
12 Locked QAM256 519000000 Hz 0 dBmV 45 dB 0 0
13 Locked QAM256 525000000 Hz 0 dBmV 45 dB 0 0
14 Locked QAM256 531000000 Hz 0 dBmV 45 dB 0 0
15 Locked QAM256 537000000 Hz 0 dBmV 45 dB 0 0
16 Locked QAM256 543000000 Hz 0 dBmV 45 dB 0 0
17 Locked QAM256 549000000 Hz 0 dBmV 45 dB 0 0
18 Locked QAM256 555000000 Hz 0 dBmV 45 dB 0 0
19 Locked QAM256 561000000 Hz 0 dBmV 45 dB 0 0
20 Locked QAM256 567000000 Hz 0 dBmV 45 dB 0 0
21 Locked QAM256 573000000 Hz 0 dBmV 45 dB 0 0
22 Locked QAM256 579000000 Hz 0 dBmV 45 dB 0 0
23 Locked QAM256 585000000 Hz 0 dBmV 45 dB 0 0
24 Locked QAM256 591000000 Hz 0 dBmV 45 dB 0 0
25 Locked QAM256 597000000 Hz 0 dBmV 45 dB 0 0
26 Locked QAM256 603000000 Hz 0 dBmV 45 dB 0 0
27 Locked QAM256 609000000 Hz 0 dBmV 45 dB 0 0
28 Locked QAM256 615000000 Hz 0 dBmV 45 dB 0 0
29 Locked QAM256 621000000 Hz 0 dBmV 45 dB 0 0
30 Locked QAM256 627000000 Hz 0 dBmV 45 dB 0 0
31 Locked QAM256 633000000 Hz 0 dBmV 45 dB 0 0
32 Locked QAM256 639000000 Hz 0 dBmV 45 dB 0 0
193 Locked OFDM PLC 762000000 Hz 1 dBmV 45 dB 371861585 0

Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
1 Locked SC-QAM 35600000 Hz 6400000 45.0 dBmV
2 Locked SC-QAM 29200000 Hz 6400000 45.0 dBmV
3 Locked SC-QAM 22800000 Hz 6400000 45.3 dBmV
4 Locked SC-QAM 16400000 Hz 6400000 45.3 dBmV

Current System Time:Wed Apr 20 17:41:01 2022

Cj87 · Apr 23, 2022

Does all of this seem right? All at the same time I'm getting T3 Timeouts no response received/ranging maintenance in the event logs as well. Lag spikes in game and robot mic in discord throughout the day per usual. Seems to stay stable enough to play only through the LATE night A.M. hours. I've also grown tired of the service visits telling me everything looks fine so I forwarded an informal complaint with FCC and got a call the next day from Comcast Corporate but have struggled to reach back with work. Will update when I can on that.

bill001g · Apr 23, 2022

Those numbers look almost perfect. I am not sure what the one on channel 193 is but all the errors are correctable even though that is a big number. I forget what this channel is used for it might be a control channel, the data normally goes over the ones you see number 1-32'

It depends on how many t3 error you get and it seems there are a couple of variations. On mine I will see one t3 timeout between 8-12hrs after the modem does a DHCP renew message. This happens almost exactly in 1 week intervals. The constant ping I run has never detected it.

I suspect you can not see the problem if it is truly outbound. All you can tell is the data is fine when you send it. It is not a simple signal level issue because your output power would be closer to 50. This is where fiber is nice sometimes because there tends to be no electronic between you and the ISP cabinet. With cable in larger installs they sometime put in things like powered amplifiers in the path. Only the cable tech will know this and not likely even the first level cable tech that comes out to the house. I know last time I had issues the first level guy just came out and confirmed there was data loss and the other guy came out and fixed something far away from my house.

Cj87 · Apr 23, 2022

bill001g said:
Those numbers look almost perfect. I am not sure what the one on channel 193 is but all the errors are correctable even though that is a big number. I forget what this channel is used for it might be a control channel, the data normally goes over the ones you see number 1-32'

It depends on how many t3 error you get and it seems there are a couple of variations. On mine I will see one t3 timeout between 8-12hrs after the modem does a DHCP renew message. This happens almost exactly in 1 week intervals. The constant ping I run has never detected it.

I suspect you can not see the problem if it is truly outbound. All you can tell is the data is fine when you send it. It is not a simple signal level issue because your output power would be closer to 50. This is where fiber is nice sometimes because there tends to be no electronic between you and the ISP cabinet. With cable in larger installs they sometime put in things like powered amplifiers in the path. Only the cable tech will know this and not likely even the first level cable tech that comes out to the house. I know last time I had issues the first level guy just came out and confirmed there was data loss and the other guy came out and fixed something far away from my house.

I see that everything is perfect but it is perfect during the am hours until 11a.m. hits its garbage for the rest of the day.
Your issue seems to be what I have going on and its been a thing for a long time. Too long. I don't know why its taken this long to get anybody capable of fixing the problem. So hopefully this Corporate call will get the ball rolling.

bill001g · Apr 23, 2022

This could be one of your neighbors has some kind of defective equipment and when they use it causes issues. The ISP would have to be looking at the connection during that time to see it. I know if you hook moca up without a filter it will get back into the ISP network but I am unsure exactly what problems that will cause.

Cj87 · Apr 24, 2022

On the bright side they have waived off every single fee per visit and are offering a credit for the amount of time I've been with issues. They are sending their expert here this time Tuesday.

Cj87 · Apr 28, 2022

An update to the situation. Issues persist. The technician who came over had pinged the node and received 100% loss almost instantly so he submitted a Refer To Maintenance; their term for a bucket truck to come out. 2 of them showed up the same day after being told I may not see anybody. Some time later one of them walked over and asked me what my issues were and that they weren't seeing it but they would monitor it from then. Someone returned the next morning and replaced something up there and support chat had told me it was a cable wire or some sort they replaced with the ticket marked complete. So I evaluated the internet for the day and lo and behold the issue persisted. So I contacted the number I was given from the Technician that visited who would be his Supervisor. We have chitchatted and he has seen the issue himself when looking into my account and said he would create a new ticket for the next day; fast forward to the next day; He said there's another RTM open that he didn't even have to create. Meaning they definitely found intermittency issues. He said it seems ok at times and others it doesn't. Whenever the noise spikes it spikes big time then just goes away then comes back, seems like they are struggling to find where these spikes are coming from he says. Mentioned he'll do what he can to try to resolve it for me... So if they can't then what? Switch ISPs or am I just SOL?

�

Startup Procedure
Procedure	Status	Comment
Acquire Downstream Channel	567000000 Hz	Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Configuration File	OK
Security	Enabled	BPI+
DOCSIS Network Access Enabled	Allowed

https://prnt.sc/l3E8AzkQexYE

https://prnt.sc/2whaIFFDwsGK

Had to take screenshots because the table just breaks when I paste it from modem

Ralston18 · Apr 29, 2022

Interesting.

Two things caught my eye:

1) "the guy found 10+ year old Direct TV cables that were an old chewed up mess. He rerouted new cable around the house to the inside of the wall to my room being very confident this should fix my packet loss issue; however it did not. " (Post #1)

Where was that new cable connected in?

Is there some sketch or diagram showing all of the Xfinity cables to your house and within your house? Showing all cables, splitters, barrel connectors and verified that any given cable end is truly connected to what is believed to be the "other end". No splitters or anything else somewhere between? No rogue or unaccounted for coax cables in place. Likewise for Ethernet cables for that matter.

[Side note: Are all unused coax connections properly terminated with a terminator cap versus a dust cap? ]

2) "I see that everything is perfect but it is perfect during the am hours until 11a.m. hits its garbage for the rest of the day. " (Post #21.)

The router's logs show some WLAN being rejected from MAC's probably not your devices. And MACs can be spoofed. I would still make a list of those MACs and determine the manufacturer's thereof. Could prove revealing.

For example one randomly chosen MAC was listed to Wyze Labs, Inc. Is there some real device in the network that accounts for that MAC? Or the other MACs that appear.

Still do the router's show increases in those rejections starting around 11:00 a.m. or so? Do the problems/rejections also seem to stop whenever Xfinity is around? What MAC or MACs are being rejected?

Noted in Post #22 that @bill001g mentioned a neighbor with defective equipment. I am wondering if the problem goes beyond that.....

How well do you know your neighbor(s)?

Thinking outside of the box a bit at the risk of falling out. Still no harm, no foul. Would be remiss otherwise.

Question Outbound Packet Loss (Wired Connection)

Distinguished

Titan

Distinguished

Distinguished

Admirable

Distinguished

Distinguished

Admirable

Distinguished

Titan

Distinguished

Titan

Distinguished

Titan

Titan

Distinguished

Distinguished

Distinguished

Distinguished

Titan

Distinguished

Titan

Distinguished

Distinguished

Titan

Share this page