06-09-2022 13:40 - edited 06-09-2022 14:25
Hi All.
Made the upgrade to 1GB from M350 17/18th August and had it installed on Sat 20th. The first couple days was absolutely brilliant. I was getting the speeds advertised and i'm still getting them. The problem i'm having is that it keeps dropping all day every day for the last 2 week on a wired ethernet connection. I'd use speedtest, samknows (sometimes the test fails when it's dropping connection) and all those websites/applications and i'll see drops of 0.15mpbs, then shooting back to around 200mbps to the advertise speeds of 900 to 945.54 as i know it won't go over 950 due to hub limitations. I noticed packet loss/huge latency spikes and it was getting worse so i checked speedtest to notice it dropping to around 0.57. Image below was my speed 2 days after installation after noticing latency online. It's still dropping between 0.15-0.50 this morning.
I thought it would be due to a new install/upgrade so i let it settle for 7 days and the issue seemed to go away, i checked the "Fix Broadband" option on the VM website and they say i still have issues so i've booked an engineer visit. Just wanted to know if there are any solutions on VM's side, checking to see why i'm getting my speeds but it's spiking crazily all day. I can web browse but can't play games any more due to it getting so bad. Can't watch videos on youtube on the tv either.
06-09-2022 13:42 - edited 06-09-2022 13:43
Been hitting these lows all morning out of nowhere.
on 06-09-2022 15:23
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 331000000 | -9.5 | 37.4 | QAM256 | 25 |
1 | 139000000 | -0.4 | 40.4 | QAM256 | 1 |
2 | 147000000 | -0.3 | 40.9 | QAM256 | 2 |
3 | 155000000 | -0.6 | 39 | QAM256 | 3 |
4 | 163000000 | -1.5 | 39 | QAM256 | 4 |
5 | 171000000 | -2.1 | 39 | QAM256 | 5 |
6 | 179000000 | -2.5 | 39 | QAM256 | 6 |
7 | 187000000 | -3 | 39 | QAM256 | 7 |
8 | 195000000 | -3.5 | 39 | QAM256 | 8 |
9 | 203000000 | -3.8 | 39 | QAM256 | 9 |
10 | 211000000 | -4.1 | 39 | QAM256 | 10 |
11 | 219000000 | -4.4 | 38.6 | QAM256 | 11 |
12 | 227000000 | -5 | 39 | QAM256 | 12 |
13 | 235000000 | -5.3 | 39 | QAM256 | 13 |
14 | 243000000 | -5.5 | 38.6 | QAM256 | 14 |
15 | 251000000 | -5.9 | 38.6 | QAM256 | 15 |
16 | 259000000 | -6 | 38.6 | QAM256 | 16 |
17 | 267000000 | -5.7 | 38.6 | QAM256 | 17 |
18 | 275000000 | -5.6 | 38.6 | QAM256 | 18 |
19 | 283000000 | -6.2 | 38.6 | QAM256 | 19 |
20 | 291000000 | -6.9 | 37.4 | QAM256 | 20 |
21 | 299000000 | -6.7 | 37.6 | QAM256 | 21 |
22 | 307000000 | -6.8 | 37.4 | QAM256 | 22 |
23 | 315000000 | -7.6 | 37.4 | QAM256 | 23 |
24 | 323000000 | -8.9 | 37.4 | QAM256 | 24 |
26 | 339000000 | -9.4 | 36.4 | QAM256 | 26 |
27 | 347000000 | -9.6 | 36.6 | QAM256 | 27 |
28 | 355000000 | -9.8 | 36.6 | QAM256 | 28 |
29 | 363000000 | -9.8 | 36.4 | QAM256 | 29 |
30 | 371000000 | -9.8 | 36.6 | QAM256 | 30 |
31 | 379000000 | -10.3 | 36.4 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 37.355988 | 0 | 0 |
1 | Locked | 40.366287 | 0 | 0 |
2 | Locked | 40.946209 | 0 | 0 |
3 | Locked | 38.983261 | 0 | 0 |
4 | Locked | 38.983261 | 0 | 0 |
5 | Locked | 38.983261 | 0 | 0 |
6 | Locked | 38.983261 | 0 | 0 |
7 | Locked | 38.983261 | 0 | 0 |
8 | Locked | 38.983261 | 0 | 0 |
9 | Locked | 38.983261 | 0 | 0 |
10 | Locked | 38.983261 | 0 | 0 |
11 | Locked | 38.605377 | 0 | 0 |
12 | Locked | 38.983261 | 0 | 0 |
13 | Locked | 38.983261 | 0 | 0 |
14 | Locked | 38.605377 | 0 | 0 |
15 | Locked | 38.605377 | 0 | 0 |
16 | Locked | 38.605377 | 0 | 0 |
17 | Locked | 38.605377 | 0 | 0 |
18 | Locked | 38.605377 | 0 | 0 |
19 | Locked | 38.605377 | 0 | 0 |
20 | Locked | 37.355988 | 0 | 0 |
21 | Locked | 37.636276 | 0 | 0 |
22 | Locked | 37.355988 | 0 | 0 |
23 | Locked | 37.355988 | 1 | 0 |
24 | Locked | 37.355988 | 0 | 0 |
26 | Locked | 36.386890 | 0 | 0 |
27 | Locked | 36.609653 | 0 | 0 |
28 | Locked | 36.609653 | 2 | 0 |
29 | Locked | 36.386890 | 0 | 0 |
30 | Locked | 36.609653 | 0 | 0 |
31 | Locked | 36.386890 | 0 | 0 |
on 06-09-2022 15:25
3.0 Upstream channels
Channel | Frequency (Hz) | Power (dBmV) | Symbol Rate (ksps) | Modulation | Channel ID |
1 | 25800000 | 50 | 5120 KSym/sec | 64QAM | 6 |
2 | 39400000 | 51.5 | 5120 KSym/sec | 64QAM | 4 |
3 | 46200000 | 52.3 | 5120 KSym/sec | 64QAM | 3 |
4 | 32600000 | 50.5 | 5120 KSym/sec | 64QAM | 5 |
3.0 Upstream channels
Channel | Channel Type | T1 Timeouts | T2 Timeouts | T3 Timeouts | T4 Timeouts |
1 | US_TYPE_STDMA | 0 | 0 | 3 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
on 06-09-2022 15:35
Network Log
Time | Priority | Description |
Tue 06/09/2022 10:28:17 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 10:28:19 | 6 | CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; 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; |
Tue 06/09/2022 10:36:55 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 10:37:13 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 10:52:05 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 10:52:27 | 6 | CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; 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; |
Tue 06/09/2022 11:19:31 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 11:19:39 | 6 | CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; 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; |
Tue 06/09/2022 13:07:25 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 13:07:37 | 6 | CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; 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; |
Tue 06/09/2022 13:48:01 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 13:48:04 | 6 | CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; 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; |
Tue 06/09/2022 13:55:45 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 13:55:49 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 13:59:07 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 13:59:08 | 6 | CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; 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; |
Tue 06/09/2022 14:02:39 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 14:02:46 | 6 | CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; 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; |
Tue 06/09/2022 14:07:01 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 14:07:28 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 14:10:07 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 14:10:11 | 6 | CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; 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; |
Tue 06/09/2022 14:12:37 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 14:12:44 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 14:20:09 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 06/09/2022 14:20:30 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 06-09-2022 22:07
on 09-09-2022 09:03
Hi @KMitchell91,
Thanks for your post, and a warm welcome back to our Community Forums!
I'm sorry to hear you're facing problems with your Broadband service. I've taken a look at things on our end and can see some packet loss, and disconnections on your service.
I'm going to drop you a private message to look into this further. Please look out for it in the top-right of the Forums, in the purple envelope.
Cheers,
08-10-2022 14:51 - edited 08-10-2022 14:54
Thanks Reece for the messages but i'm pretty fed up/had enough.
Having upgraded on August 20th, to an engineer that failed to send off my request for cabling repull outside my property and contecting VM Community here around the 13th September, to booking me in 3 weeks later on October 8th, to receiving a text message just now telling me that they've rebooked me in, for 2 weeks time on the 22nd. I've put a complaint in and i'll be looking to leave VM after years with you through family and then me. Nothing but problems from installation after moving a few years ago and waiting a couple months to get connected, to waiting what would be 2 months to enjoy waiting 2-3 minutes to load an image and 5 minutes to buffer a video to having to buffer again a few minutes later. Won't even think of playing an online game right now.
Wish things were so much simpler to get online, i'm in the city and shouldn't have been an issue, it's a highly populated VM area and i feel a bit entitled to be reacting in this way but it's just one problem after another, it's affected being able to work, gfs side business etc. Sending me barmy.
on 10-10-2022 15:09
I am sorry for that, as my colleague has explained, we would have booked in the first available slot. Though I do appreciate the frustration. Please do let us know how the tech visit goes and if you need further assistance.
Kind regards,
Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill
29-11-2022 18:24 - edited 29-11-2022 18:25
It was rebooked twice to October then 28 November. No one from, i'm assuming Comex2000 since they're partnered with VM bothered to turn up to the property yesterday, was supposed to have been escalated since it's the construction team for the pre pull and have a text message or email by 5 today and got nothing. I have a VM Assistant on Whatsapp asking me if i'm ok to rebook it to the 14th December. I'm refusing and fighting to get my contract canceled. I can't stream anything, play any videos or play a simple online game.
It will have been 4 months and counting to get this sorted, i'm done.
Thanks anyway.