Showing results for 
Search instead for 
Did you mean: 

New Hub reboots at midnight every night

Joining in

Hi folks.

So i previously had the Superhub 2.0 (had it for about 7 years) and i encountered an issue where the wifi networks would randomly vanish  maybe once a day (even though connection via ethernet is fine) and i would have to restart the Hub to get the wifi networks to show again. I rang VM and explained the issue and the person i spoke to changed some settings apparently and asked me to see if the issue persists. 3-4 days went by and I had the same issue so I rang back and a new Superhub 3.0 was sent out. I connected this up and everything is ok with the wifi now.

However now the Hub reboots at nearly dead on midnight every night now and ive never had this issue before! I've rang up today and I have an engineer coming out in 2 weeks but to be honest i dont have any faith that this is a hardware or connection issue as my broadband is rock solid speed wise and doesnt drop out at all so im convinced this is a setting somewhere thats causing the midnight reboots.



Joining in


Downstream bonded channels

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

11870000004.338256 qam7
2195000000438256 qam8
32030000004.438256 qam9
4211000000438256 qam10
5235000000538256 qam13
6243000000438256 qam14
72510000005.538256 qam15
8259000000438256 qam16
92670000005.638256 qam17
102750000004.938256 qam18
112830000005.838256 qam19
122910000005.538256 qam20
132990000005.638256 qam21
143070000006.440256 qam22
153150000005.540256 qam23
163230000006.340256 qam24
17443000000538256 qam25
184510000004.638256 qam26
194590000004.938256 qam27
204670000004.838256 qam28
214750000004.538256 qam29
224830000004.538256 qam30

Downstream bonded channels

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



Upstream bonded channels

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

1462000004.45512064 qam1
2326000004.65512064 qam3
3258000004.4512064 qam4
4394000004.475512064 qam2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts


Network Log

Time Priority Description

23/05/2020 14:32:55Warning!RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:32:53Warning!Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:30:1Warning!RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:30:1noticeLAN login Success;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:28:4Warning!RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:28:3Warning!Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:19:59Warning!RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:19:58Warning!Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:19:49Warning!RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:19:48Warning!Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:05:53Warning!RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:05:52Warning!Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:02:57Warning!RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 14:02:56Warning!Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 12:46:10Warning!RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 12:46:10Warning!Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 11:55:15Warning!RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=00:01:***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 11:55:14Warning!Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 11:53:54Warning!RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;
23/05/2020 11:53:53Warning!Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0;


General Configuration

Network access
Maximum Number of CPEs
Baseline Privacy
Config file

Primary Downstream Service Flow

Max Traffic Rate230000061
Max Traffic Burst42600
Min Traffic Rate0

Primary Upstream Service Flow

Max Traffic Rate22000061
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort


Very Insightful Person
Very Insightful Person
VM "may" be doing some routine "updates/upgrades" at that time that is causing it.

However your down channels are showing more than usual PostRS errors that isnt healthy, they may just be "historic though. So, try rebooting the Hub to get them reset to 0 and then check back in to check that they have - and then monitor them over the next day or so. They shouldnt reappear - if the do it will need a VM tech to take a look.

Also, in the meantime to get a record of the midnight dances - set up a free “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts - it will thus allow you to differentiate between those and simple wifi dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections, useful data to have to match to the Network logs (in your Hub settings) and also in discussions with VM.
If you just see a wall of "red" then your Hub is not accepting the "pings" - make sure you uncheck the “ignore ping from WAN side” box in the settings - note it will take an hour or two to start seeing a sensible picture.


I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 1 WiFi, 1 on PA) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's. On 250Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

Very Insightful Person
Very Insightful Person

You hub is not rebooting every night. What it happening is it is losing connection with the VM CMTS at the other end of your cable. It then go into a loop trying to regain the connection and it eventually succeeds. So don’t think the Pre & Post RS error will reset every night, they will not. The only way to reset them is to power cycle your hub.

There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2

Thanks for your reply. Any idea what the resolution would be then?

Joining in

Went down again 12:20 - 12:45 No connection at all and couldnt even interact with the router via as it refused to even take me to the login page or acknowledge the router was there

Joining in

Again last night at 12:20 it went down.... It seems a bit too conistant

Very Insightful Person
Very Insightful Person

I presume you are testing the connection and logging on to the Hub3 from a cable connected devices. The only other explanation, other than VM maintenance, is perhaps someone on your street box is doing “something funny” on the internet at that time, although I think this is very remote. 

There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2

I am connecting via Ethernet and it seems this issue has only started since i changed the Hub from the 2.0 to 3.0 and it wouldnt expect that VM have been doing maintainance 4 days in a row just after midnight. I never had this issue with the 2.0 Hub, other than recently the wifi disappearing (but not the connection via ethernet) which is why i asked for a new Hub.

Call it rational or not im convinced that the first person who I spoke to, before i got the new Hub, "changed some settings" in their own words which I believe is causing the issues