Speed on 350mb package down to 40mb

[snakkles]

Hi,

I recently had an engineer visit who could not find / fix this issue. I have a Hub 4 in modem mode connected to a debian firewall. Until recently I have seen consistent speeds > 300mb on my 350mb package. As of a few days ago my speed seems to be stuck at around 40mb downstream (upstream remains consistently around 40mb as it always has).

Things I have tried:
1. Reboot hub 4. After a reboot, I do see fast speeds for a short amount of time - sometimes 5 minutes, sometimes 30, but they always then do come down to around 40mb which is where they stay.
2. Plug a laptop directly into Hub 4 using a different ethernet cable. Same symptoms as above.
3. Reboot / patch / restart my own firewall - no difference.

Anybody have any idea what I can try next? Connection stats follow...

[snakkles]

Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream

Cable Modem Status	Online	DOCSIS 3.1
Primary downstream channel	Locked	SC-QAM
DOCSIS 3.0 channels	31	4
DOCSIS 3.1 channels	1	0

[snakkles]

3.0 Downstream channels

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

37	426750000	6.3	39	QAM256	37
32	386750000	5.9	39	QAM256	32
33	394750000	5.9	39	QAM256	33
34	402750000	6.2	39	QAM256	34
35	410750000	6.2	40.4	QAM256	35
36	418750000	6.4	39	QAM256	36
0		0	0	QAM256	0
39	442750000	6.3	40.4	QAM256	39
40	450750000	6.1	39	QAM256	40
10	210750000	6.3	40.4	QAM256	10
11	218750000	5.9	40.9	QAM256	11
12	226750000	5.6	40.4	QAM256	12
13	234750000	5.2	40.4	QAM256	13
14	242750000	5.5	39	QAM256	14
15	250750000	6.4	39	QAM256	15
16	258750000	7.4	40.4	QAM256	16
17	266750000	7.9	40.9	QAM256	17
18	274750000	8.1	40.4	QAM256	18
19	282750000	8.3	40.9	QAM256	19
20	290750000	8.3	40.4	QAM256	20
21	298750000	7.9	40.9	QAM256	21
22	306750000	8	40.9	QAM256	22
23	314750000	7.9	40.9	QAM256	23
24	322750000	7.9	40.9	QAM256	24
25	330750000	7.8	40.4	QAM256	25
26	338750000	7.9	40.9	QAM256	26
27	346750000	7.9	40.4	QAM256	27
28	354750000	7.3	40.4	QAM256	28
29	362750000	6.6	39	QAM256	29
30	370750000	5.8	39	QAM256	30
31	378750000	5.6	40.4	QAM256	31

3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

37	Locked	38.983261	0	0
32	Locked	38.983261	0	0
33	Locked	38.983261	0	0
34	Locked	38.983261	0	0
35	Locked	40.366287	0	0
36	Locked	38.983261	0	0
0	NotLocked		0	0
39	Locked	40.366287	0	0
40	Locked	38.983261	0	0
10	Locked	40.366287	0	0
11	Locked	40.946209	0	0
12	Locked	40.366287	0	0
13	Locked	40.366287	0	0
14	Locked	38.983261	0	0
15	Locked	38.983261	0	0
16	Locked	40.366287	0	0
17	Locked	40.946209	0	0
18	Locked	40.366287	0	0
19	Locked	40.946209	0	0
20	Locked	40.366287	0	0
21	Locked	40.946209	0	0
22	Locked	40.946209	0	0
23	Locked	40.946209	0	0
24	Locked	40.946209	0	0
25	Locked	40.366287	0	0
26	Locked	40.946209	0	0
27	Locked	40.366287	0	0
28	Locked	40.366287	0	0
29	Locked	38.983261	0	0
30	Locked	38.983261	0	0
31	Locked	40.366287	0	0

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

159

96

4K

1840

QAM4096

759

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

159

Locked

41

4.2

475385714

0

[snakkles]

3.0 Upstream channels

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

1	53700000	47	5120 KSym/sec	QAM64	10
2	32600000	45.3	5120 KSym/sec	QAM64	13
3	39400000	45.8	5120 KSym/sec	QAM64	12
4	46200000	46.3	5120 KSym/sec	QAM64	11

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	0	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0

[snakkles]

General Configuration

Network access	true
Maximum Number of CPEs	1
Baseline Privacy	true
DOCSIS Mode	3.1
Config file	kfoA,.iyewrkldJKDHSUBsgvc

Primary Downstream Service Flow

SFID	1382
Max Traffic Rate	402500089
Max Traffic Burst	42600
Min Traffic Rate	0

Primary Upstream Service Flow

SFID	1381
Max Traffic Rate	38500089
Max Traffic Burst	42600
Min Traffic Rate	0
Max Concatenated Burst	42600
Scheduling Type	bestEffort

[snakkles]

Network Log

Time Priority Description

Fri 01/07/2022 15:41:48	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:41:41	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:41:13	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:41:11	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:38:42	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:38:33	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:38:15	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:38:09	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:37:24	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:37:23	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:37:16	6	CM-STATUS message sent. Event Type Code: 1; Chan ID: 38; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:37:15	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:37:04	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:37:01	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:36:52	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:36:47	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:36:44	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:36:39	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:36:26	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:36:15	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:35:57	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:35:35	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:35:34	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:34:59	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:34:36	6	CM-STATUS message sent. Event Type Code: 1; Chan ID: 38; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:34:35	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:34:27	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:34:17	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:32:53	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:32:37	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:31:32	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:31:15	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:30:08	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:30:03	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:29:33	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:29:25	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:28:57	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:28:45	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:28:31	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:28:27	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:28:21	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:28:13	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:27:43	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:27:39	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:27:19	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:27:07	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:26:56	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:26:47	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:24:36	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 01/07/2022 15:24:35	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[snakkles]

Just a polite bump in the hope someone has some idea for what I can try next?

[Tudor]

Bumping a post puts it a the bottom of the queue and is against forum rules. VM answer posts in date/time orders usually within 3 days. 

[David_Bn]

Good Evening @snakkles, thanks got your post on our Community Forums, and a very warm welcome to you!

Can you please provide us with an update on your services?

I've looked into the local area, and there appears to be no outages effecting the services.

The hub also appears to be in perfect health.

Kindest regards,

David_Bn

[snakkles]

Hi there @David_Bn,

No change here - still sitting around 40mb/s:

No sure what else to try...