Question Outbound Packet Loss (Wired Connection)

[Cj87]

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

 

[Cj87]

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.

No sketch that I know of.. I mean the guy removed like 3 splitters, the original coax that was then re-routed outside, instead of them before just changing it from the inside of the house to the modem. They have confirmed there to be an issue with the Node for our area they just can't pinpoint where its coming from because the noise spike happens abruptly and goes away and comes back. I don't know I'm just relaying what I'm told and what I see tbh. Dealing with this stuff has been a massive migraine.

For the Wyze rejections It was due to me factory resetting everything. They were trying to connect via the wrong password/ID because it all goofs up when you reset. That was fixed. But there may be a device left unchecked. However my logs are constantly filled with fraggle attack/RST scans ever since I got the Nighthawk. I do not communicate with any neighbors really. I've whoisdomained one of the IPs and it came up as comcast: https://whois.domaintools.com/98.52.123.154