I took the offer of a Hub 5 which arrived the other day and so far it's not been particularly brilliant on the stability side of things.
I was on a Hub 3 previously, as notorious as it is, it was stable (in modem mode) for years.
I opted to use the Hub 5 in router mode due to my existing RT-AC56U being far too old and long unsupported now. The Hub 5 has much improved wifi coverage and wifi speeds compared to the Hub 3 in my experience so far.
Unfortunately I am getting multiple disconnections every day, the internet goes away on wired and wireless devices for 30 - 60 seconds before coming back,  the Hub 3 had no such issues. I notice that there have been some others with this particular issue with the Hub 5.
Here are recent log entries, the MDD Timeout coincides with the disconnections.
	Quote:
	
	
		
			
				27-01-2022 11:14:09	notice	CM-STATUS message sent. Event Type Code: 4; 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; 
27-01-2022 11:13:04	notice	CM-STATUS message sent. Event Type Code: 1; 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; 
27-01-2022 11:13:00	warning	MDD message timeout;CM-MAC=*CMTS-MAC=*;CM-QOS=1.1;CM-VER=3.1; 
27-01-2022 08:42:56	notice	CM-STATUS message sent. Event Type Code: 4; 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; 
27-01-2022 08:42:02	notice	CM-STATUS message sent. Event Type Code: 1; 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; 
27-01-2022 08:41:32	warning	MDD message timeout;CM-MAC=*;CMTS-MAC=*;CM-QOS=1.1;CM-VER=3.1; 
27-01-2022 04:02:51	notice	CM-STATUS message sent. Event Type Code: 4; 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; 
27-01-2022 04:01:53	notice	CM-STATUS message sent. Event Type Code: 1; 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; 
27-01-2022 04:01:29	warning	MDD message timeout;CM-MAC=*;CMTS-MAC=*;CM-QOS=1.1;CM-VER=3.1; 
27-01-2022 00:33:07	notice	CM-STATUS message sent. Event Type Code: 4; 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; 
27-01-2022 00:32:10	notice	CM-STATUS message sent. Event Type Code: 1; 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; 
27-01-2022 00:32:06	warning	MDD message timeout;CM-MAC=*;CMTS-MAC=8;CM-QOS=1.1;CM-VER=3.1; 
26-01-2022 18:47:17	notice	CM-STATUS message sent. Event Type Code: 4; 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; 
26-01-2022 18:46:13	notice	CM-STATUS message sent. Event Type Code: 1; 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; 
26-01-2022 18:46:04	warning	MDD message timeout;CM-MAC=*;CMTS-MAC=*;CM-QOS=1.1;CM-VER=3.1;
			
		 |