Question Outbound Packet Loss (Wired Connection)

Cj87

Honorable
Jul 31, 2015
21
0
10,510
0
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
ProcedureStatusComment
Acquire Downstream Channel711000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnableBPI+
IP Provisioning ModeHonor MDDIPv6 only
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNR / MERUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1LockedQAM25644711000000 Hz0.7 dBmV45.2 dB30298696100
2LockedQAM25613525000000 Hz0.6 dBmV46.8 dB30178984600
3LockedQAM25614531000000 Hz0.4 dBmV46.6 dB30179358700
4LockedQAM25615537000000 Hz0.5 dBmV46.6 dB30177373000
5LockedQAM25616543000000 Hz0.4 dBmV46.4 dB30180117700
6LockedQAM25617549000000 Hz0.3 dBmV46.4 dB30180450900
7LockedQAM25618555000000 Hz0.3 dBmV46.3 dB30180842300
8LockedQAM25619561000000 Hz0.2 dBmV46.3 dB30181188600
9LockedQAM25620567000000 Hz0.3 dBmV46.2 dB30181604800
10LockedQAM25621573000000 Hz0.1 dBmV46.0 dB30181981600
11LockedQAM25622579000000 Hz0.3 dBmV46.3 dB30182380700
12LockedQAM25623585000000 Hz0.1 dBmV46.1 dB30182174600
13LockedQAM25624591000000 Hz0.1 dBmV45.9 dB30182543600
14LockedQAM25625597000000 Hz0.2 dBmV45.9 dB30182951300
15LockedQAM25626603000000 Hz0.0 dBmV45.8 dB30183267600
16LockedQAM25627609000000 Hz0.1 dBmV45.8 dB30183721000
17LockedQAM25628615000000 Hz0.0 dBmV45.7 dB30184018100
18LockedQAM25629621000000 Hz0.0 dBmV45.7 dB30184422400
19LockedQAM25630627000000 Hz0.2 dBmV45.6 dB30184774500
20LockedQAM25631633000000 Hz0.1 dBmV45.7 dB30185193600
21LockedQAM25632639000000 Hz0.2 dBmV45.8 dB30185521000
22LockedQAM25633645000000 Hz0.2 dBmV45.7 dB30185568300
23LockedQAM25634651000000 Hz0.2 dBmV45.7 dB30186150600
24LockedQAM25635657000000 Hz0.3 dBmV45.6 dB30186453200
25LockedQAM25636663000000 Hz0.4 dBmV45.8 dB30187025400
26LockedQAM25637669000000 Hz0.4 dBmV45.6 dB30187374500
27LockedQAM25638675000000 Hz0.5 dBmV44.8 dB30187788300
28LockedQAM25639681000000 Hz0.4 dBmV45.7 dB30188116300
29LockedQAM25640687000000 Hz0.5 dBmV45.6 dB30188539900
30LockedQAM25641693000000 Hz0.6 dBmV45.7 dB30188871300
31LockedQAM25642699000000 Hz0.5 dBmV45.6 dB30191089200
32LockedQAM25643705000000 Hz0.6 dBmV45.8 dB30189140200
Upstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPower
1LockedATDMA135600000 Hz46.0 dBmV
2LockedATDMA229200000 Hz48.0 dBmV
3LockedATDMA322800000 Hz45.8 dBmV
4LockedATDMA416400000 Hz45.5 dBmV
5Not LockedUnknown00 Hz0.0 dBmV
6Not LockedUnknown00 Hz0.0 dBmV
7Not LockedUnknown00 Hz0.0 dBmV
8Not LockedUnknown00 Hz0.0 dBmV
Downstream OFDM Channels
ChannelLock StatusModulation / Profile IDChannel IDFrequencyPowerSNR / MERActive Subcarrier Number RangeUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1Locked0, 1193762000000 Hz1.3 dBmV44.3 dB1108 ~ 298778206741777242590
2Not Locked000 Hz-0.2 dBmV0.0 dB0 ~ 4095000
Upstream OFDMA Channels
ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower
1Not LockedUnknown00 Hz0 dBmV
2Not LockedUnknown00 Hz0 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;​
 
Last edited:
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

Honorable
Jul 31, 2015
21
0
10,510
0
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

Honorable
Jul 31, 2015
21
0
10,510
0
@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
ProcedureStatusComment
Acquire Downstream Channel711000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnableBPI+
IP Provisioning ModeHonor MDDIPv6 only
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNR / MERUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1LockedQAM25644711000000 Hz0.7 dBmV45.2 dB30298696100
2LockedQAM25613525000000 Hz0.6 dBmV46.8 dB30178984600
3LockedQAM25614531000000 Hz0.4 dBmV46.6 dB30179358700
4LockedQAM25615537000000 Hz0.5 dBmV46.6 dB30177373000
5LockedQAM25616543000000 Hz0.4 dBmV46.4 dB30180117700
6LockedQAM25617549000000 Hz0.3 dBmV46.4 dB30180450900
7LockedQAM25618555000000 Hz0.3 dBmV46.3 dB30180842300
8LockedQAM25619561000000 Hz0.2 dBmV46.3 dB30181188600
9LockedQAM25620567000000 Hz0.3 dBmV46.2 dB30181604800
10LockedQAM25621573000000 Hz0.1 dBmV46.0 dB30181981600
11LockedQAM25622579000000 Hz0.3 dBmV46.3 dB30182380700
12LockedQAM25623585000000 Hz0.1 dBmV46.1 dB30182174600
13LockedQAM25624591000000 Hz0.1 dBmV45.9 dB30182543600
14LockedQAM25625597000000 Hz0.2 dBmV45.9 dB30182951300
15LockedQAM25626603000000 Hz0.0 dBmV45.8 dB30183267600
16LockedQAM25627609000000 Hz0.1 dBmV45.8 dB30183721000
17LockedQAM25628615000000 Hz0.0 dBmV45.7 dB30184018100
18LockedQAM25629621000000 Hz0.0 dBmV45.7 dB30184422400
19LockedQAM25630627000000 Hz0.2 dBmV45.6 dB30184774500
20LockedQAM25631633000000 Hz0.1 dBmV45.7 dB30185193600
21LockedQAM25632639000000 Hz0.2 dBmV45.8 dB30185521000
22LockedQAM25633645000000 Hz0.2 dBmV45.7 dB30185568300
23LockedQAM25634651000000 Hz0.2 dBmV45.7 dB30186150600
24LockedQAM25635657000000 Hz0.3 dBmV45.6 dB30186453200
25LockedQAM25636663000000 Hz0.4 dBmV45.8 dB30187025400
26LockedQAM25637669000000 Hz0.4 dBmV45.6 dB30187374500
27LockedQAM25638675000000 Hz0.5 dBmV44.8 dB30187788300
28LockedQAM25639681000000 Hz0.4 dBmV45.7 dB30188116300
29LockedQAM25640687000000 Hz0.5 dBmV45.6 dB30188539900
30LockedQAM25641693000000 Hz0.6 dBmV45.7 dB30188871300
31LockedQAM25642699000000 Hz0.5 dBmV45.6 dB30191089200
32LockedQAM25643705000000 Hz0.6 dBmV45.8 dB30189140200
Upstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPower
1LockedATDMA135600000 Hz46.0 dBmV
2LockedATDMA229200000 Hz48.0 dBmV
3LockedATDMA322800000 Hz45.8 dBmV
4LockedATDMA416400000 Hz45.5 dBmV
5Not LockedUnknown00 Hz0.0 dBmV
6Not LockedUnknown00 Hz0.0 dBmV
7Not LockedUnknown00 Hz0.0 dBmV
8Not LockedUnknown00 Hz0.0 dBmV
Downstream OFDM Channels
ChannelLock StatusModulation / Profile IDChannel IDFrequencyPowerSNR / MERActive Subcarrier Number RangeUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1Locked0, 1193762000000 Hz1.3 dBmV44.3 dB1108 ~ 298778206741777242590
2Not Locked000 Hz-0.2 dBmV0.0 dB0 ~ 4095000
Upstream OFDMA Channels
ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower
1Not LockedUnknown00 Hz0 dBmV
2Not LockedUnknown00 Hz0 dBmV
Current System Time: Sat Apr 09 19:12:46 2022
System Up Time: 1:51:30
[TD][/TD]​
 

Cj87

Honorable
Jul 31, 2015
21
0
10,510
0
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

Honorable
Jul 31, 2015
21
0
10,510
0
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;​
 
Last edited:
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…
 
Last edited:

Cj87

Honorable
Jul 31, 2015
21
0
10,510
0
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.
 
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

Honorable
Jul 31, 2015
21
0
10,510
0
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
 
Last edited:
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
 
Reactions: Cj87

Cj87

Honorable
Jul 31, 2015
21
0
10,510
0
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.
 
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

Titan
Moderator
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

Honorable
Jul 31, 2015
21
0
10,510
0
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

Honorable
Jul 31, 2015
21
0
10,510
0
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
 
Last edited:

Cj87

Honorable
Jul 31, 2015
21
0
10,510
0
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.
 
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

Honorable
Jul 31, 2015
21
0
10,510
0
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.
 
Last edited:
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

Honorable
Jul 31, 2015
21
0
10,510
0
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

Honorable
Jul 31, 2015
21
0
10,510
0
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
ProcedureStatusComment
Acquire Downstream Channel567000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration FileOK
SecurityEnabledBPI+
DOCSIS Network Access EnabledAllowed

https://prnt.sc/l3E8AzkQexYE

https://prnt.sc/2whaIFFDwsGK

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

Ralston18

Titan
Moderator
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.
 

ASK THE COMMUNITY