Random speed drops

[Galveo]

Hi Everyone,

I currently have a pretty simple setup with Virgin Media in the UK. I have a UDM (Unifi Dream Machine) and a super hub 4.0 in modem mode plugged into the UDM.

I have a 550/50 connection and most of the time it runs at this speed with no issue.

However at random intervals my speed will drop down to 40/27 and you won't be able to get any faster than this speed. The only thing that fixes this issue temporally is by restarting the modem and it will go back to the full speed.

I can't work out what's causing this issue and have tried numerous diagnostic steps:

• Factory Reset Modem

• Replaced Ethernet cable from modem to router.

• Replaced Superhub with a new model. Issue apparent on Superhub 3.0 and 4.0

• Tried a new router (Amplifi Gamer's Edition)

Any help would be really greatly appreciated.

[MOD EDIT: Subject title changed for clarity]

[Steven_L]

Hey @Galveo,

Welcome to the community and thanks for taking the time to post your issue on the forums.
I'm sorry to hear that you're facing issues with your connection at the moment.

Do you have any issues, if you run the hub in router mode rather than modem mode?

Would you be able to setup a BQM to help monitor your connection and this can also help us diagnose the issues with your connection. You can set this up here https://www.thinkbroadband.com/broadband/monitoring/quality and if you can post back in a few days, this will show us any issues that you're having with your connection.

Also, please could you post your hubs network logs on this thread, you can access this  In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) and hit return. On the first page up [there should be no need to login if you have done so before]

click on the “router status” icon/text at bottom-middle of first page up and then copy/paste 3 FULL sets of data onto here – from the Downstream, Upstream, & Network Logs pages.

Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses.

Regards,

Steven_L

[Galveo]

Thanks for your reply.

I have setup a BQM which can be found on the link below:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/49a067930be95595d60cd7f1dbff7972ce993a3b

Please also find the router status details as requested.

Downstream:

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

26	339000000	-7.099998	38.983261	QAM256	26
1	139000000	-5.799999	38.983261	QAM256	1
2	147000000	-5.599998	38.983261	QAM256	2
3	155000000	-5.799999	38.605377	QAM256	3

Upstream:

3.0 Upstream channels

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

1	25800000	52.520599	5120 KSym/sec	64QAM	6
2	32600000	52.770599	5120 KSym/sec	64QAM	5
3	39400000	52.770599	5120 KSym/sec	64QAM	4
4	46200000	53.270599	5120 KSym/sec	64QAM	3

Network Log:

Network Log

Time Priority Description

Wed Apr 13 14:49:12 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Wed Apr 13 14:49:13 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 14:49:15 2022	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;
Wed Apr 13 14:52:47 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 14:52:55 2022	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;
Wed Apr 13 14:55:07 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 14:55:32 2022	6	CM-STATUS message sent. Event Type Code: 1; Chan ID: 11; 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;
Wed Apr 13 14:55:45 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 14:55:47 2022	6	CM-STATUS message sent. Event Type Code: 1; Chan ID: 11; 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;
Wed Apr 13 14:56:21 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 14:56:21 2022	6	CM-STATUS message sent. Event Type Code: 1; Chan ID: 11; 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;
Wed Apr 13 14:57:31 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 14:57:32 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Wed Apr 13 14:57:41 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 14:57:50 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Wed Apr 13 14:57:53 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 14:57:54 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Wed Apr 13 15:04:19 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 15:04:40 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Wed Apr 13 15:07:05 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 15:07:13 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Wed Apr 13 15:23:09 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 15:23:28 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Wed Apr 13 15:29:47 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 15:29:53 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Wed Apr 13 15:30:25 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 15:30:54 2022	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;
Wed Apr 13 15:31:09 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 15:31:29 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Wed Apr 13 15:35:49 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 15:36:13 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Wed Apr 13 15:36:15 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 15:36:17 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Wed Apr 13 15:41:09 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 15:41:20 2022	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;
Wed Apr 13 15:41:25 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 13 15:41:26 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Thu Apr 14 08:20:11 2022	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 14 08:36:11 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; 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;
Thu Apr 14 11:52:21 2022	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 14 11:52:26 2022	5	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 14 11:52:30 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 14 11:52:51 2022	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 14 11:52:58 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 14 11:53:04 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 3; 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;
Thu Apr 14 11:53:10 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 14 11:53:13 2022	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 14 11:53:30 2022	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 14 11:53:43 2022	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 3; 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;
Thu Apr 14 11:56:27 2022	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Steven_L]

Thanks for coming back to us @Galveo.

I have looked into this and can see an issue with your downstream channels on our system that would need a technician visit to resolve.

I can arrange the appointment from here but would need to confirm a few details via a private message, that I will drop over in a moment.
Please look out for the private message and we can get started.
Regards,
Steven_L

[Galveo]

PM Has been sent, thank you.

[Steven_L]

Thanks for confirming your details via private message @Galveo.
I have arranged for the appointment and you can track your engineer appointments online. Simply sign in to My Virgin Media and you’ll see your appointments on your account dashboard.

Regards,

Steven_L