on 13-06-2023 12:27
For a year now I have had constant dropouts throughout the day with my net. I can be watching a youtube video and it would freeze for a few seconds, Playing a game I either lag spike or get disconnected. I simply cannot play online games on my connection right now due to stability issues. I have called Virgin about this and get told its an area fault and will be fixed soon. But it's the same issue, over and over. If it was an area fault it would get better eventually. A year is not eventually. I simply need an engineer to come out and check stability, power levels etc as no idea how to do this myself.
I use a third-party router and hub in modem mode as the router mode was unuseable. Its definitely not my router as tried several routers (3 to be exact) and the same things happening. I am paying for a service which is just terrible right now and feel Virgin are simply trying to kick the ball down the street instead of helping me. I had this issue before a long time ago and it was a fault with the box at the end of my street as somebody stole cabling from it and it took you a year of me pestering before you came out to realise what had happened. Please can anybody help me here? I have been with virgin 20 years and feel customer support is just horrible right now and finally ready to leave and goto another supplier when contract ends, something I never wanted to do due to great service in the past but its just unbearable right now with 3 kids not being able to play games like roblox without it cutting out.
on 13-06-2023 23:10
Can you show us the connection data like this...
_______________________________________
In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) (DONT click these links) - and hit return. No need to log in - just click on the “Router Status” icon/text at bottom-middle (Hub3/4/5) or top/right (SH’s) - of the Login page.
Then… Navigate to these “data pages” and just copy/paste the normal “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs pages. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts
Also, If you haven’t already, set up a free, secure and “offlsite” - “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts , latency issues, packet drops, etc - 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 - note it will take a few hours to start seeing a sensible picture - post up the “link” to the “share live graph”. Click the lower link (Share Live Graph) then, click generate. Copy the text in the Direct Link box, beware, there may be more text than you can see. On here click the Link icon (2 links chain to the left of the camera icon) In the URL box paste the link you copied and then click OK
https://www.thinkbroadband.com/broadband/monitoring/quality
on 16-06-2023 23:34
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 330750000 | 0.500000 | 37.355988 | QAM256 | 25 |
18 | 274750000 | 1.400002 | 37.636276 | QAM256 | 18 |
19 | 282750000 | 1.400002 | 38.605377 | QAM256 | 19 |
20 | 290750000 | 1.500000 | 37.636276 | QAM256 | 20 |
21 | 298750000 | 1.599998 | 37.636276 | QAM256 | 21 |
22 | 306750000 | 1.299999 | 38.983261 | QAM256 | 22 |
23 | 314750000 | 0.799999 | 38.605377 | QAM256 | 23 |
24 | 322750000 | 0.400002 | 37.636276 | QAM256 | 24 |
26 | 338750000 | 0.099998 | 37.355988 | QAM256 | 26 |
27 | 346750000 | 0.200001 | 37.636276 | QAM256 | 27 |
28 | 354750000 | 0.299999 | 37.636276 | QAM256 | 28 |
29 | 362750000 | -0.099998 | 37.636276 | QAM256 | 29 |
30 | 370750000 | -0.099998 | 37.636276 | QAM256 | 30 |
31 | 378750000 | -0.200001 | 37.355988 | QAM256 | 31 |
32 | 386750000 | -0.799999 | 37.355988 | QAM256 | 32 |
33 | 394750000 | -1.099998 | 37.355988 | QAM256 | 33 |
34 | 402750000 | -1.400002 | 37.355988 | QAM256 | 34 |
35 | 410750000 | -1.799999 | 37.355988 | QAM256 | 35 |
36 | 418750000 | -1.799999 | 37.355988 | QAM256 | 36 |
37 | 426750000 | -1.700001 | 37.355988 | QAM256 | 37 |
38 | 434750000 | -1.799999 | 37.355988 | QAM256 | 38 |
39 | 442750000 | -1.400002 | 37.636276 | QAM256 | 39 |
40 | 450750000 | -1.900002 | 37.636276 | QAM256 | 40 |
41 | 458750000 | -2.000000 | 37.636276 | QAM256 | 41 |
42 | 466750000 | -2.000000 | 37.355988 | QAM256 | 42 |
43 | 474750000 | -2.400002 | 37.355988 | QAM256 | 43 |
44 | 482750000 | -2.500000 | 37.355988 | QAM256 | 44 |
45 | 490750000 | -2.900002 | 36.609653 | QAM256 | 45 |
46 | 498750000 | -3.000000 | 36.386890 | QAM256 | 46 |
47 | 506750000 | -2.799999 | 37.355988 | QAM256 | 47 |
48 | 514750000 | -2.599998 | 37.355988 | QAM256 | 48 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 37.355988 | 0 | 0 |
18 | Locked | 37.636276 | 0 | 0 |
19 | Locked | 38.605377 | 0 | 0 |
20 | Locked | 37.636276 | 0 | 0 |
21 | Locked | 37.636276 | 0 | 0 |
22 | Locked | 38.983261 | 0 | 0 |
23 | Locked | 38.605377 | 0 | 0 |
24 | Locked | 37.636276 | 0 | 0 |
26 | Locked | 37.355988 | 0 | 0 |
27 | Locked | 37.636276 | 0 | 0 |
28 | Locked | 37.636276 | 0 | 0 |
29 | Locked | 37.636276 | 0 | 0 |
30 | Locked | 37.636276 | 0 | 0 |
31 | Locked | 37.355988 | 0 | 0 |
32 | Locked | 37.355988 | 0 | 0 |
33 | Locked | 37.355988 | 0 | 0 |
34 | Locked | 37.355988 | 0 | 0 |
35 | Locked | 37.355988 | 0 | 0 |
36 | Locked | 37.355988 | 0 | 0 |
37 | Locked | 37.355988 | 0 | 0 |
38 | Locked | 37.355988 | 0 | 0 |
39 | Locked | 37.636276 | 0 | 0 |
40 | Locked | 37.636276 | 0 | 0 |
41 | Locked | 37.636276 | 0 | 0 |
42 | Locked | 37.355988 | 0 | 0 |
43 | Locked | 37.355988 | 0 | 0 |
44 | Locked | 37.355988 | 0 | 0 |
45 | Locked | 36.609653 | 0 | 0 |
46 | Locked | 36.386890 | 0 | 0 |
47 | Locked | 37.355988 | 0 | 0 |
48 | Locked | 37.355988 | 0 | 0 |
159 | 96 | 4K | 1840 | QAM4096 | 759 |
159 | Locked | 38 | -4.9 | 2158335943 | 0 |
on 16-06-2023 23:35
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 49600000 | 46.020599 | 5120 KSym/sec | 64QAM | 1 |
2 | 23600000 | 46.520599 | 5120 KSym/sec | 64QAM | 5 |
3 | 30100000 | 46.520599 | 5120 KSym/sec | 64QAM | 4 |
4 | 36600000 | 46.520599 | 5120 KSym/sec | 64QAM | 3 |
5 | 43100000 | 46.020599 | 5120 KSym/sec | 64QAM | 2 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | US_TYPE_ATDMA | 0 | 0 | 0 | 0 |
2 | US_TYPE_ATDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_ATDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_ATDMA | 0 | 0 | 0 | 0 |
5 | US_TYPE_ATDMA | 0 | 0 | 0 | 0 |
6 | 10.0 | 39.8 | 2K | QAM32 |
6 | OFDMA | 200 | 53.9 | 0 | 0 |
on 16-06-2023 23:35
Time Priority Description
Fri Jun 16 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Jun 16 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 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 Jun 15 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 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 Jun 15 | 4 | DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 5 | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 4 | DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 5 | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 4 | DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 5 | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 4 | DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 5 | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 4 | DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 5 | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 4 | DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 4 | DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jun 15 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt078+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Jun 14 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 13 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Jun 13 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Jun 12 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Jun 12 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Jun 12 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Jun 12 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Jun 11 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Jun 11 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Jun 11 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Jun 11 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt078+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Jun 11 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Jun 11 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 10 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 10 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 10 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 10 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 10 | 6 | US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 16-06-2023 23:36
As for a monitor I am using wired for everything except phones and its on the computers and consoles this is an issue.
on 18-06-2023 10:51
Can I get any real help with this one?
on 20-06-2023 12:44
Hey vhero,
Welcome back to the community and thanks for taking the time to post here on the forums.
I’m sorry to hear of the issues that you’re having with your connection, I have looked into this and can see issues with your upstream channel power levels 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.
Kind Regards,
Steven_L
on 20-06-2023 14:01
Thanks, Steven for assisting. I have messaged you with the details you have asked for.
on 20-06-2023 14:58
Thanks for confirming your details via private message vhero.
I have arranged a technician appointment for you and it can be tracked via your online account. Please sign into My Virgin Media and you will see your appointments on your account dashboard. However, this can take up to 24 hours to be updated. You can also check your appointments via the 'My Virgin Media' app.
There will be no charge for this visit unless:
• The technician diagnoses the faults as not being caused by our network/equipment
• The technician discovers that the fault or problem relates to your equipment
• The technician discovers that the fault or problem relates to any system that we are not responsible for.
The technician will confirm during their visit if any of these instances apply, and if so, a £25 charge will be applied to your account.
Kind Regards,
Steven_L