Strange Performance Issues on Gig1

[EhsanWaheed]

I'm on Gig1 and have the new Hub 5. And performance has been up and down recently. I have switched the router into modem mode to take advantage of my Nighthawk MK83 Mesh system for better range. Occasionally my Wi-Fi speed will drop to 450-550mb but after a restart of the modem I can get over 650mb. Another strange issue is connected to a gigabit switch is my PS5 which gets an average download of 450mb instead of the 900mb it should be getting. Cables have been changed modem and routers have been reset. The issue for the PS5 ethernet did resolve temporarily but it's gone back down again. A restart of the modem allows me to reach optimal Wi-Fi speeds of over 600mb but why do I have to do these restarts and what's causing my Ethernet performance to choke. I have even switched out the gigabit switch as well at one point with no difference.

So to summarise:

1. Slower Wi-Fi performance than usual. Until modem is rebooted.

2. Slow ethernet performance from PS5 speed test.

[legacy1]

Do a speed test by wire on PC check WAN IP when speed is slow copy the MAC of your Nighthawk to the hub on to your PC and connect PC to hub in place of the Nighthawk check IP then do a speed to see if its slow.

[EhsanWaheed]

Speed test on PC is fine at the moment reporting around 900+ usually around 930mbps.

[EhsanWaheed]

Main issue is the occasional drop in performance which doesn't resolve until modem is rebooted. This usually resolves the Wi-Fi speed issue. The PS5 ethernet speed issue I have no idea why that is so slow.

[EhsanWaheed]

Here is some stats from modem at the moment for anyone to see if they're optimal.
Modem Status is as follows at the moment:

Item Status Comments

Acquired Downstream Channel(Hz)	339000000	Locked
Ranged Upstream Channel(Hz)	49600000	Ranged
Provisioning State	Online	Operational

Downstream Channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	339000000	8.1	42	QAM 256	26
2	139000000	9.2	42	QAM 256	1
3	147000000	9.1	42	QAM 256	2
4	155000000	9.3	42	QAM 256	3
5	163000000	9.4	42	QAM 256	4
6	171000000	9.2	42	QAM 256	5
7	179000000	8.8	42	QAM 256	6
8	187000000	8.5	42	QAM 256	7
9	195000000	8.5	42	QAM 256	8
10	203000000	8.5	42	QAM 256	9
11	211000000	8.8	42	QAM 256	10
12	219000000	8.8	42	QAM 256	11
13	227000000	8.5	42	QAM 256	12
14	235000000	8.1	42	QAM 256	13
15	243000000	7.6	42	QAM 256	14
16	251000000	7.1	42	QAM 256	15
17	259000000	7.1	42	QAM 256	16
18	267000000	7.2	42	QAM 256	17
19	275000000	7.5	42	QAM 256	18
20	283000000	8.5	42	QAM 256	19
21	291000000	8.9	42	QAM 256	20
22	299000000	8.3	42	QAM 256	21
23	307000000	7.9	42	QAM 256	22
24	315000000	7.9	42	QAM 256	23
25	323000000	8	42	QAM 256	24
26	331000000	8.1	42	QAM 256	25
27	347000000	7.8	42	QAM 256	27
28	355000000	7.4	42	QAM 256	28
29	363000000	7.3	42	QAM 256	29
30	371000000	7.4	42	QAM 256	30
31	379000000	7.5	42	QAM 256	31

Upstream Channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

0	49600000	41.5	5120	QAM 64	9
1	43100000	41.5	5120	QAM 64	10
2	36600000	42	5120	QAM 64	11
3	30100000	41.5	5120	QAM 64	12
4	23600000	41	5120	QAM 64	13

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file

Allowed

1

Enabled

3.1

fd;kfoA,.iyewrkldJKDHSUBs

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic Rate

9818

1200000450 bps

42600bytes

0 bps

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type

9817

55000270 bps

42600bytes

0 bps

42600bytes

Best Effort

Network Log

Time Priority Description

18-11-2022 12:57:22	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:57:22	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:57:18	notice	REGISTRATION COMPLETE - Waiting for Operational status
18-11-2022 12:57:13	warning	Dynamic Range Window violation
18-11-2022 12:57:13	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:57:13	warning	Dynamic Range Window violation
18-11-2022 12:57:13	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:57:13	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:57:13	warning	Dynamic Range Window violation
18-11-2022 12:57:12	warning	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:57:07	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:57:04	notice	TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:57:01	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:56:59	notice	Honoring MDD; IP provisioning mode = IPv4
18-11-2022 12:56:59	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:56:54	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:56:54	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:56:54	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:56:50	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-11-2022 12:56:42	critical	Cable Modem Reboot due to power button reset
18-11-2022 12:56:38	critical	Cable Modem Reboot due to master console reset
18-11-2022 12:56:37	critical	Cable Modem Reboot due to master console reset
18-11-2022 12:56:37	critical	Cable Modem Reboot due to master console reset
18-11-2022 12:56:37	critical	Cable Modem Reboot due to master console reset
10-11-2022 12:57:33	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-11-2022 12:57:32	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-11-2022 12:57:15	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-11-2022 12:57:07	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-11-2022 12:57:05	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[legacy1]

Without powering off hub unplug ethernet cable for 5min and back in see what speed you get

[EhsanWaheed]

Same at the moment. Even unplugged the gigabit switch for a few seconds too.

[legacy1]

So your speed is slow?

[EhsanWaheed]

Yes. Just wondering if anyone else is having speed issues with the PS5 on gig1.

[legacy1]

Well if a reboot fixes it then its likely a problem with the rate limiter or as you push 1Gb out the port it has to drop packets maybe limit in your router QoS/BWM to limit to 900Mb