on 15-05-2022 10:25
So for the last I don’t even know how many months, almost without fail our wifi has started to fail at 7/8/9pm every night as well as dropping out during the day.
The wifi will still show as connected but nothing on any devices will work and it’s almost like it starts jumping from having weak signal to high signal and then back again.
When testing the speed around these times when I can even manage to get it to load, the download speed is sitting around 5 and then I’ll test straight after and it’ll shoot back up to 200 and then drop to 5 in a test not even 30 seconds later.
We contacted Virgin about two months ago and it seemed like the issue had been solved but that lasted for maybe a week before this started again.
I’m at a loss with what to do at this point because I don’t know why we’re paying the amount we are for this wifi when it doesn’t even work when we need it to.
on 15-05-2022 10:52
Please post some stats and check if there is an area problem.
Check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level. You could also try the web page http://www.virginmedia.com/servicechecker
How to get stats from a VM hub (no need to logon to the hub)
Open a web browser and go to 192.168.0.1 router mode or 192.168.100.1 modem mode
on 15-05-2022 11:38
Hi, here are the stats you’ve asked for! There are no area issues for the area according to the webpage.
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 139000000 | 3.5 | 38 | 256 qam | 1 |
2 | 147000000 | 4.1 | 38 | 256 qam | 2 |
3 | 155000000 | 4 | 38 | 256 qam | 3 |
4 | 163000000 | 3.7 | 38 | 256 qam | 4 |
5 | 171000000 | 3.5 | 38 | 256 qam | 5 |
6 | 179000000 | 2.9 | 38 | 256 qam | 6 |
7 | 187000000 | 2.9 | 38 | 256 qam | 7 |
8 | 195000000 | 2.4 | 38 | 256 qam | 8 |
9 | 203000000 | 2 | 38 | 256 qam | 9 |
10 | 211000000 | 1.5 | 38 | 256 qam | 10 |
11 | 219000000 | 1.2 | 38 | 256 qam | 11 |
12 | 227000000 | 1.2 | 38 | 256 qam | 12 |
13 | 235000000 | 0.7 | 38 | 256 qam | 13 |
14 | 243000000 | 0.5 | 38 | 256 qam | 14 |
15 | 251000000 | 0 | 38 | 256 qam | 15 |
16 | 259000000 | -0.4 | 38 | 256 qam | 16 |
17 | 267000000 | -0.5 | 38 | 256 qam | 17 |
18 | 275000000 | -0.2 | 38 | 256 qam | 18 |
19 | 283000000 | 0.4 | 38 | 256 qam | 19 |
20 | 291000000 | 0.7 | 38 | 256 qam | 20 |
21 | 299000000 | 0.7 | 38 | 256 qam | 21 |
22 | 307000000 | 0.7 | 38 | 256 qam | 22 |
23 | 315000000 | 0.7 | 38 | 256 qam | 23 |
24 | 323000000 | 0.5 | 38 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 208 | 79 |
2 | Locked | 38.9 | 218 | 92 |
3 | Locked | 38.9 | 221 | 108 |
4 | Locked | 38.9 | 175 | 189 |
5 | Locked | 38.9 | 178 | 185 |
6 | Locked | 38.9 | 134 | 112 |
7 | Locked | 38.6 | 70 | 78 |
8 | Locked | 38.9 | 77 | 46 |
9 | Locked | 38.6 | 119 | 26 |
10 | Locked | 38.9 | 217 | 60 |
11 | Locked | 38.9 | 218 | 297 |
12 | Locked | 38.9 | 210 | 133 |
13 | Locked | 38.9 | 72 | 0 |
14 | Locked | 38.6 | 64 | 0 |
15 | Locked | 38.9 | 84 | 0 |
16 | Locked | 38.9 | 70 | 12 |
17 | Locked | 38.9 | 66 | 0 |
18 | Locked | 38.9 | 74 | 0 |
19 | Locked | 38.6 | 47 | 0 |
20 | Locked | 38.6 | 51 | 0 |
21 | Locked | 38.6 | 57 | 0 |
22 | Locked | 38.9 | 61 | 0 |
23 | Locked | 38.9 | 42 | 0 |
24 | Locked | 38.9 | 49 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 25799975 | 43.5 | 5120 | 64 qam | 11 |
2 | 39400000 | 44.3 | 5120 | 64 qam | 7 |
3 | 46200000 | 44.8 | 5120 | 64 qam | 3 |
4 | 32600064 | 44 | 5120 | 64 qam | 8 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 1 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
Will have to post network separately as it hit’s character limit
on 15-05-2022 11:39
Time Priority Description
15/05/2022 11:18:39 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/05/2022 01:01:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/05/2022 22:14:56 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/05/2022 19:52:12 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/05/2022 22:19:26 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/05/2022 22:19:24 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/05/2022 05:46:24 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/05/2022 06:16:55 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:58:31 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:57:18 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:55:8 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:16 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:12 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:12 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:12 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:12 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:11 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/05/2022 14:42:9 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/04/2022 01:34:28 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
27/04/2022 16:27:5 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 15-05-2022 12:38
There are a lot of errors showing, but they are accumulative since the hub was last power cycled. So please turn the hub off for two minutes and after two hours post a new full set of stats.
on 17-05-2022 12:51
Hi @Whiskeyprincxss.
Welcome to our community forums and thank you for your first posts.
Sorry to hear you have been having these issues with your WiFi service. We can understand this is not ideal and we want to best help.
I have been able to take a look at your service on our systems and it seems everything is in order after the reboot. Do you need any further help regarding this?
Please get in touch if so and we will do our best to help.
Thanks,
on 21-05-2022 22:52
Hi! Sorry it’s been a busy week so I’ve only been able to get around to doing this now.
turned router off around 8pm and these are the results
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 139000000 | 4 | 38 | 256 qam | 1 |
2 | 147000000 | 4.5 | 38 | 256 qam | 2 |
3 | 155000000 | 4.4 | 38 | 256 qam | 3 |
4 | 163000000 | 4 | 38 | 256 qam | 4 |
5 | 171000000 | 3.7 | 38 | 256 qam | 5 |
6 | 179000000 | 3.2 | 40 | 256 qam | 6 |
7 | 187000000 | 3.2 | 38 | 256 qam | 7 |
8 | 195000000 | 2.7 | 38 | 256 qam | 8 |
9 | 203000000 | 2.4 | 38 | 256 qam | 9 |
10 | 211000000 | 2 | 38 | 256 qam | 10 |
11 | 219000000 | 1.7 | 38 | 256 qam | 11 |
12 | 227000000 | 1.5 | 38 | 256 qam | 12 |
13 | 235000000 | 1.2 | 38 | 256 qam | 13 |
14 | 243000000 | 0.7 | 38 | 256 qam | 14 |
15 | 251000000 | 0.4 | 38 | 256 qam | 15 |
16 | 259000000 | 0 | 38 | 256 qam | 16 |
17 | 267000000 | 0.2 | 38 | 256 qam | 17 |
18 | 275000000 | 0.4 | 38 | 256 qam | 18 |
19 | 283000000 | 1 | 38 | 256 qam | 19 |
20 | 291000000 | 1 | 38 | 256 qam | 20 |
21 | 299000000 | 1 | 38 | 256 qam | 21 |
22 | 307000000 | 1 | 38 | 256 qam | 22 |
23 | 315000000 | 1 | 38 | 256 qam | 23 |
24 | 323000000 | 0.9 | 38 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 23 | 0 |
2 | Locked | 38.6 | 32 | 0 |
3 | Locked | 38.9 | 36 | 0 |
4 | Locked | 38.6 | 24 | 12 |
5 | Locked | 38.9 | 27 | 0 |
6 | Locked | 40.3 | 15 | 0 |
7 | Locked | 38.9 | 13 | 0 |
8 | Locked | 38.9 | 11 | 0 |
9 | Locked | 38.6 | 16 | 0 |
10 | Locked | 38.9 | 22 | 0 |
11 | Locked | 38.6 | 13 | 0 |
12 | Locked | 38.9 | 15 | 0 |
13 | Locked | 38.6 | 9 | 0 |
14 | Locked | 38.9 | 12 | 0 |
15 | Locked | 38.6 | 12 | 0 |
16 | Locked | 38.9 | 17 | 0 |
17 | Locked | 38.6 | 11 | 14 |
18 | Locked | 38.9 | 13 | 0 |
19 | Locked | 38.9 | 9 | 0 |
20 | Locked | 38.9 | 8 | 0 |
21 | Locked | 38.9 | 9 | 14 |
22 | Locked | 38.6 | 8 | 0 |
23 | Locked | 38.6 | 13 | 0 |
24 | Locked | 38.9 | 12 | 0 |
on 21-05-2022 22:53
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 25800000 | 43.5 | 5120 | 64 qam | 11 |
2 | 39400000 | 44.3 | 5120 | 64 qam | 7 |
3 | 46200000 | 44.8 | 5120 | 64 qam | 3 |
4 | 32600000 | 43.8 | 5120 | 64 qam | 8 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 21-05-2022 22:54
Time Priority Description
19/05/2022 08:42:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/05/2022 00:01:38 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/05/2022 20:32:35 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/05/2022 11:18:39 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/05/2022 01:01:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/05/2022 22:14:56 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/05/2022 19:52:12 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/05/2022 22:19:26 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/05/2022 22:19:24 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/05/2022 05:46:24 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/05/2022 06:16:55 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:58:31 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:57:18 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:55:8 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:16 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:12 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:12 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:12 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:12 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 09:52:11 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 21-05-2022 22:55
Hi, no it’s still doing exactly what is was before unfortunately