on 20-02-2022 18:56
Hi all,
VM did some work in the area last week, since then we've had patchy internet. Upload speeds range from 2 to 6Mpbs instead of the 33Mbps it used to be, download is around 130MBps instead of 350.
I rebooted everything this morning, for a short time the speeds improved, now they're back to being poor and I'm experiencing packet loss in games, etc.
Is this going to require an engineer to resolve do you think?
Here's the modem info:
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 171000000 | 5.5 | 38 | 256 qam | 5 |
2 | 139000000 | 4.9 | 38 | 256 qam | 1 |
3 | 147000000 | 5 | 38 | 256 qam | 2 |
4 | 155000000 | 5.3 | 38 | 256 qam | 3 |
5 | 163000000 | 5.4 | 38 | 256 qam | 4 |
6 | 179000000 | 5.6 | 38 | 256 qam | 6 |
7 | 187000000 | 5.9 | 38 | 256 qam | 7 |
8 | 195000000 | 5.9 | 38 | 256 qam | 8 |
9 | 203000000 | 6 | 38 | 256 qam | 9 |
10 | 211000000 | 5.5 | 38 | 256 qam | 10 |
11 | 219000000 | 5.8 | 38 | 256 qam | 11 |
12 | 227000000 | 5.8 | 38 | 256 qam | 12 |
13 | 235000000 | 6 | 38 | 256 qam | 13 |
14 | 243000000 | 5.8 | 38 | 256 qam | 14 |
15 | 251000000 | 6.1 | 38 | 256 qam | 15 |
16 | 259000000 | 6.1 | 38 | 256 qam | 16 |
17 | 267000000 | 6.4 | 38 | 256 qam | 17 |
18 | 275000000 | 6.3 | 38 | 256 qam | 18 |
19 | 283000000 | 6.6 | 38 | 256 qam | 19 |
20 | 291000000 | 6.6 | 38 | 256 qam | 20 |
21 | 299000000 | 7 | 38 | 256 qam | 21 |
22 | 307000000 | 7 | 38 | 256 qam | 22 |
23 | 315000000 | 7.4 | 38 | 256 qam | 23 |
24 | 323000000 | 7.5 | 38 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 24243 | 130804 |
2 | Locked | 38.6 | 7025118 | 2643051 |
3 | Locked | 38.6 | 294437 | 178747 |
4 | Locked | 38.6 | 4953374 | 175427 |
5 | Locked | 38.6 | 7960201 | 1627044 |
6 | Locked | 38.6 | 7907139 | 953080 |
7 | Locked | 38.6 | 3231886 | 0 |
8 | Locked | 38.6 | 9371 | 0 |
9 | Locked | 38.6 | 7825 | 0 |
10 | Locked | 38.9 | 10534 | 0 |
11 | Locked | 38.6 | 10470 | 0 |
12 | Locked | 38.6 | 10694 | 0 |
13 | Locked | 38.9 | 7575 | 0 |
14 | Locked | 38.6 | 7225 | 0 |
15 | Locked | 38.6 | 5109 | 0 |
16 | Locked | 38.9 | 4234 | 0 |
17 | Locked | 38.9 | 2309 | 0 |
18 | Locked | 38.6 | 1677 | 0 |
19 | Locked | 38.9 | 818 | 0 |
20 | Locked | 38.6 | 684 | 0 |
21 | Locked | 38.9 | 423 | 0 |
22 | Locked | 38.6 | 335 | 0 |
23 | Locked | 38.9 | 211 | 0 |
24 | Locked | 38.9 | 128 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 48 | 5120 | 64 qam | 3 |
2 | 39400021 | 48 | 5120 | 64 qam | 4 |
3 | 53700031 | 48 | 5120 | 64 qam | 2 |
4 | 60299981 | 48 | 5120 | 64 qam | 1 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 1 | 0 |
Time Priority Description
20/02/2022 18:38:43 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 18:31:47 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 18:31:34 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 17:53:34 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 17:49:49 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 16:05:11 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 16:00:6 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 11:56:51 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 11:55:42 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 09:08:29 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 08:46:57 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 08:28:54 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 08:16:6 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/02/2022 23:35:35 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/02/2022 23:28:37 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/02/2022 20:13:54 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/02/2022 20:12:51 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/02/2022 20:06:24 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/02/2022 20:03:3 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/02/2022 19:08:17 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 21-02-2022 15:57
PostRS errors are showing a bad connection on those channels, possibly noise on the circuit. Ideally PostRS errors should be zero. You will always get PreRS errors, but these are acceptable.
You will need an VM technician to fix this. Either phone in or wait here a day or two for a VM Mod to pick this up.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
on 21-02-2022 16:12
@Adduxi
Thanks for that, I'll get in touch with VM in that case.
on 23-02-2022 17:23
Just updating. VM engineer came out today, he found an issue at the box where VM enters the house. He put in some new connections which sorted the packet issues, fixing that meant it needed an attenuator to get it to the right levels.
Happy to say 5 hours later and still no Post RS errors.
on 24-02-2022 15:43
Hi Robinio,
Thank you for your post and keeping us updated on this. We're glad to hear this has all been resolved for you.
^Martin
on 26-02-2022 15:51
Hi @Robinio
Thank you very much for coming back to us, I'm glad to hear our engineer found the issue and that you are no longer experiencing Post RS errors. If there's anything else you need, please do get back in touch.
Kind regards,
Serena