why does speed drop from 110mb to 40mb but restarting Hub solves it , sneakily speed capping ?

[uscool]

Hi, I've had this for maybe over a year or longer on 100mb broadband , this feels like I get speed capped if use certain amount of data ? mostly I wouldnt notice when streaming unless I download something or do speedtest and see the speed 

almost feels like this is done sneakily to reduce load on the network without customers noticing unless they monitor or check by doing speed tests 

everytime I restart the HUB it goes back to 110mb and the cycle continues gets annoying having to restart HUB every 1-2 days , I even tested didnt restart HUB when it reduced to 40mb for few days but it never went back to 110mb untill I restarted hub

I remember years back used to have some kind of policy if you used certain amount of data was different for off peak and on peak and the speed would reduce and later would go back to normal

I dont see anything about speed capping policy now ? just feels this is done sneakily most customers probably wont notice the speeds capped for general browsing or streaming and takes load off the network

I have the HUB 5 in Modem only and use my own router Asus AX88U 

its not wifi issue , I have few on wifi 6 and PC connected by ethernet cable had the same issue when I had the Hub 2

Thanks

[Andrew-G]

Sounds like a power or noise problem.  Restarting the hub makes it renegotiate all channels, and that usually gets a clean connection.  Over time that can drift off as your hub and all the other kit connected to VM's local network negotiate changes in frequency and power levels, and the slow speeds can return.

Pull up the log in page for the hub.  But don't log in, just click on the link "Check router status"  That'll bring up a window with five tabs.  Open the Downstream tab.  Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots.  Post that, do the same for the Upstream and Network log.  You'll get an error message when you post the Network log, just click on "post" a second time.  Then we can check for any obvious problems with power, noise or error counts.

Usually problems like this are an easy fix, but if you can make sure the hub has been running for 12-24 hours without a restart before posting the status data that increases the chance we'll spot a resolvable problem.

[uscool]

thanks for the quick response it has been running for over 12 hours thats for sure

Downstream bonded channels

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

1	227000000	-2.9	39	QAM 256	12
2	211000000	-2.4	40	QAM 256	10
3	219000000	-2.7	39	QAM 256	11
4	235000000	-3.1	40	QAM 256	13
5	243000000	-3.5	39	QAM 256	14
6	251000000	-4	39	QAM 256	15
7	259000000	-4.3	39	QAM 256	16
8	267000000	-3.6	39	QAM 256	17
9	275000000	-3.3	39	QAM 256	18
10	283000000	-3.2	39	QAM 256	19
11	291000000	-3.2	39	QAM 256	20
12	299000000	-3.2	39	QAM 256	21
13	307000000	-3.4	39	QAM 256	22
14	315000000	-3.6	39	QAM 256	23
15	323000000	-4	39	QAM 256	24
16	331000000	-4.3	39	QAM 256	25
17	339000000	-4.4	39	QAM 256	26
18	347000000	-4.6	39	QAM 256	27
19	355000000	-4.9	39	QAM 256	28
20	363000000	-5.1	39	QAM 256	29
21	371000000	-5.7	39	QAM 256	30
22	379000000	-6.4	39	QAM 256	31
23	387000000	-7	39	QAM 256	32
24	395000000	-6.9	35	QAM 256	33
25	403000000	-6.9	39	QAM 256	34
26	411000000	-6.9	38	QAM 256	35
27	419000000	-7	38	QAM 256	36
28	427000000	-6.9	38	QAM 256	37
29	435000000	-7	38	QAM 256	38
30	443000000	-7.2	39	QAM 256	39
31	451000000	-7.4	38	QAM 256	40

Downstream bonded channels

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

1	Locked	39	1091	18309
2	Locked	40	893	13717
3	Locked	39	1704	15566
4	Locked	40	782	15326
5	Locked	39	542	4153
6	Locked	39	462	3366
7	Locked	39	524	5838
8	Locked	39	837	8984
9	Locked	39	131	2586
10	Locked	39	155	2448
11	Locked	39	193	5558
12	Locked	39	107	3108
13	Locked	39	112	2775
14	Locked	39	129	3068
15	Locked	39	111	3465
16	Locked	39	123	3039
17	Locked	39	197	2242
18	Locked	39	149	2406
19	Locked	39	131	2265
20	Locked	39	416	6337
21	Locked	39	140	3494
22	Locked	39	364	3461
23	Locked	39	1075	5395
24	Locked	35	190	4984
25	Locked	39	90	3370
26	Locked	38	65	2742
27	Locked	38	55	18460
28	Locked	38	42	5711
29	Locked	38	8025	18800
30	Locked	39	40	3524
31	Locked	38	37	4740

Upstream bonded channels

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

1	53700000	51.3	5120	QAM 64	2
2	46200000	50.3	5120	QAM 64	3
3	39400000	49.5	5120	QAM 64	4
4	32600000	48.8	5120	QAM 64	5
5	25800000	48.3	5120	QAM 64	6

Upstream bonded 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
5	ATDMA	0	0	0	0

Network Log

Time Priority Description

23-06-2022 12:20:37	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-06-2022 12:18:45	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-06-2022 12:12:33	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 12:10:44	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;
23-06-2022 12:05:37	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 12:01:49	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;
23-06-2022 11:56:46	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 11:52:05	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;
23-06-2022 11:50:42	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-06-2022 11:48:46	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 11:44:00	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-06-2022 11:43:58	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;
23-06-2022 11:11:02	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-06-2022 11:06:37	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-06-2022 10:18:05	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 10:15:24	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;
23-06-2022 09:55:36	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 09:52:25	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;
23-06-2022 09:51:32	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-06-2022 09:49:41	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 09:47:30	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;
23-06-2022 09:46:37	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 09:44:30	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;
23-06-2022 09:43:16	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 09:39:53	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-06-2022 09:39:52	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;
23-06-2022 09:31:02	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 09:25:30	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;
23-06-2022 08:54:10	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 08:52:06	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;
23-06-2022 08:50:25	notice	CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; 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;
23-06-2022 08:48:29	notice	CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; 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;

[Andrew-G · Accepted solution]

Power levels are too low downstream, probably too high upstream.  That's usually an easy fix and should improve speed and reliability.  I'll mark your post for staff to take a look and advise, they'll book a technician if it's unique to you rather than an area fault that's already being addressed.

[uscool]

Pretty sure sometimes it's fine for around week or maybe longer other times it can happen every few days 

I did notice month or so back the internet would stop working around 12am-1am it happened few times and around the same time each time no issues during the day 

It hasn't happened past few weeks 

[Adri_G]

Hey Uscool,

Thanks for posting here with your issue, I'm sorry to see you've been facing some issues with your broadband speeds. In order to provide further assistance with this I will send you a PM now.
Please check the top-right corner of our forum and you should see a purple envelope. Click this and you'll see my message.

[John_GS]

Hi @uscool

I can see you've already been in contact with my colleague via PM who's booked you a visit 🙂 let us know how the tech visit goes.

Best,