23-10-2021 10:58 - edited 23-10-2021 11:16
Background
I've had intermittent internet throughout the majority of 2020 with multiple engineer visits. During those visits they did the following:
The only thing that wasn't done was to replace the main cable that connects the house to the cabinet. I've had this internet service since 2003, which was before Virgin took over NTL as it was NTL I originally signed up with, so the cable is 18 years old.
However, since the last visit, the intermittent issues were shorter until summer 2021 where there were hardly any issues at all. All seemed normal but the problems returned in September and the periods have lasted as long as ever from 5+ hours to over a day.
I did a post about this last year which can be found here:
https://community.virginmedia.com/t5/Forum-Archive/Intermittent-Connection-via-Ethernet/td-p/4147978
Below is my internet diary which will be updated from time to time.
22/10/22
Internet was intermittent all day yesterday until after 10pm.
23/10/21
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 330750000 | -11.7 | 36 | 256 qam | 25 |
2 | 234750000 | -14.8 | 34 | 256 qam | 13 |
3 | 242750000 | -14.5 | 34 | 256 qam | 14 |
4 | 250750000 | -14.5 | 34 | 256 qam | 15 |
5 | 258750000 | -14.5 | 34 | 256 qam | 16 |
6 | 266750000 | -14.7 | 33 | 256 qam | 17 |
7 | 274750000 | -14.3 | 34 | 256 qam | 18 |
8 | 282750000 | -13.8 | 34 | 256 qam | 19 |
9 | 290750000 | -13.4 | 35 | 256 qam | 20 |
10 | 298750000 | -13 | 35 | 256 qam | 21 |
11 | 306750000 | -12.5 | 35 | 256 qam | 22 |
12 | 314750000 | -12 | 36 | 256 qam | 23 |
13 | 322750000 | -11.7 | 36 | 256 qam | 24 |
14 | 338750000 | -11.7 | 35 | 256 qam | 26 |
15 | 346750000 | -11.7 | 36 | 256 qam | 27 |
16 | 354750000 | -11.5 | 36 | 256 qam | 28 |
17 | 362750000 | -11.2 | 36 | 256 qam | 29 |
18 | 370750000 | -11.2 | 36 | 256 qam | 30 |
19 | 378750000 | -11 | 36 | 256 qam | 31 |
20 | 386750000 | -11 | 36 | 256 qam | 32 |
21 | 394750000 | -10.7 | 36 | 256 qam | 33 |
22 | 402750000 | -10.7 | 36 | 256 qam | 34 |
23 | 410750000 | -10.4 | 36 | 256 qam | 35 |
24 | 418750000 | -10.5 | 36 | 256 qam | 36 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39399930 | 47.5 | 5120 | 64 qam | 6 |
2 | 32599951 | 47.3 | 5120 | 64 qam | 7 |
3 | 46200000 | 47.8 | 5120 | 64 qam | 5 |
4 | 25800131 | 47 | 5120 | 64 qam | 8 |
Time Priority Description
23/10/2021 09:04:56 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 09:04:56 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 09:01:43 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 08:53:34 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 08:46:56 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 08:46:56 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 08:20:48 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 08:20:48 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 08:15:29 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 08:15:29 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 07:04:8 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 07:04:7 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 07:04:0 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 07:04:0 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 07:03:59 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 07:03:58 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2021 16:14:20 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2021 16:14:20 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2021 16:09:13 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2021 16:09:13 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
Before anyone starts giving me the usual troubleshooting tips, please acknowledge what I've said earlier in this post about what the engineers did and the tips I(and many others) have done below:
However, feel free to point out any helpful oversites or raise any issues I didn't mention here. Many thanks in advance.
on 23-10-2021 17:52
No, I've never used a BQM but here are the Upstream values:
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39399936 | 47.5 | 5120 | 64 qam | 6 |
2 | 32600042 | 47 | 5120 | 64 qam | 7 |
3 | 46200000 | 47.8 | 5120 | 64 qam | 5 |
4 | 25800269 | 46.8 | 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 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 23-10-2021 18:08
@what1x wrote:No, I've never used a BQM but here are the Upstream values:
Upstream is getting a bit high, but still within spec, 34 to 51.
You really need to setup a BQM for comment and to see the state of your circuit. www.thinkbroadband.com/ping
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 23-10-2021 19:21
23-10-2021 19:52 - edited 23-10-2021 20:01
23/10/21 @ 19:45
I rang VM technical support and the packet team(I think) will be running diagnostics over the next 72 hours since the tech rep I spoke to couldn't see any problems with my router on his end, despite the downstream levels still being out of spec at the time of the call. So I'll need to ring back on Tuesday evening or Wednesday morning for the results and go from there.
on 24-10-2021 08:32
24/10/21
My internet returned to normal(as can be) around 1 am but below is a snapshot of 08:21. I'm not an expert on the numbers so can anyone spot any issues here?
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 330750000 | 3 | 38 | 256 qam | 25 |
2 | 234750000 | 1.4 | 38 | 256 qam | 13 |
3 | 242750000 | 1.4 | 38 | 256 qam | 14 |
4 | 250750000 | 1.2 | 38 | 256 qam | 15 |
5 | 258750000 | 1.2 | 38 | 256 qam | 16 |
6 | 266750000 | 1 | 38 | 256 qam | 17 |
7 | 274750000 | 1.2 | 38 | 256 qam | 18 |
8 | 282750000 | 1.7 | 38 | 256 qam | 19 |
9 | 290750000 | 2 | 38 | 256 qam | 20 |
10 | 298750000 | 2.2 | 38 | 256 qam | 21 |
11 | 306750000 | 2.7 | 38 | 256 qam | 22 |
12 | 314750000 | 3 | 38 | 256 qam | 23 |
13 | 322750000 | 3.2 | 38 | 256 qam | 24 |
14 | 338750000 | 3.2 | 38 | 256 qam | 26 |
15 | 346750000 | 3 | 38 | 256 qam | 27 |
16 | 354750000 | 3.2 | 38 | 256 qam | 28 |
17 | 362750000 | 3.4 | 38 | 256 qam | 29 |
18 | 370750000 | 3.4 | 38 | 256 qam | 30 |
19 | 378750000 | 3.4 | 38 | 256 qam | 31 |
20 | 386750000 | 3.4 | 38 | 256 qam | 32 |
21 | 394750000 | 3.4 | 38 | 256 qam | 33 |
22 | 402750000 | 3.5 | 38 | 256 qam | 34 |
23 | 410750000 | 3.5 | 38 | 256 qam | 35 |
24 | 418750000 | 3.2 | 38 | 256 qam | 36 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 3523850 | 9114 |
2 | Locked | 38.9 | 12788478 | 9947 |
3 | Locked | 38.6 | 11794435 | 9966 |
4 | Locked | 38.6 | 11185807 | 11207 |
5 | Locked | 38.6 | 10646939 | 13392 |
6 | Locked | 38.9 | 10172081 | 13012 |
7 | Locked | 38.6 | 8834956 | 12020 |
8 | Locked | 38.9 | 7335715 | 13467 |
9 | Locked | 38.9 | 6232537 | 14422 |
10 | Locked | 38.6 | 5434591 | 11823 |
11 | Locked | 38.6 | 4588935 | 12106 |
12 | Locked | 38.6 | 4002436 | 10973 |
13 | Locked | 38.9 | 3675195 | 12333 |
14 | Locked | 38.9 | 3352009 | 11594 |
15 | Locked | 38.6 | 3111317 | 12134 |
16 | Locked | 38.6 | 2856118 | 12314 |
17 | Locked | 38.6 | 2581695 | 11501 |
18 | Locked | 38.9 | 2369937 | 12426 |
19 | Locked | 38.6 | 2212797 | 12381 |
20 | Locked | 38.6 | 2102494 | 13967 |
21 | Locked | 38.9 | 1998626 | 12230 |
22 | Locked | 38.9 | 1925449 | 11835 |
23 | Locked | 38.6 | 1747253 | 10871 |
24 | Locked | 38.9 | 1588117 | 10633 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39400092 | 47.5 | 5120 | 64 qam | 6 |
2 | 32600094 | 47 | 5120 | 64 qam | 7 |
3 | 46200000 | 47.8 | 5120 | 64 qam | 5 |
4 | 25799901 | 46.8 | 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 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 24-10-2021 08:33
Time Priority Description
24/10/2021 07:17:5 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 20:20:55 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 20:20:55 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 19:06:44 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 19:06:44 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 19:06:34 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 19:06:34 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 19:06:33 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 19:06:33 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 18:54:12 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 18:54:12 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 18:49:23 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 18:49:23 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 18:47:4 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 18:35:21 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 18:18:2 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 18:06:8 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 18:05:50 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 18:05:50 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/10/2021 17:08:45 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 24-10-2021 08:46
Your network log shows that you're repeatedly losing downstream channels, along with complete synchronisation failures. These are a bad thing, and any VM employee telling you that your connection looks OK has ignored the crime scene that is your network log.
In terms of the cause, I think your downstream power levels may be off. From downstream channel number 2 through to 24, the power level should be flattish, or falling, whereas yours are rising. This probably means that the "slope" on a signal amplifier is incorrectly set somewhere in a street cabinet. If my suspicion is correct that probably affects multiple customers, and VM need to send out somebody with the skills to properly setup the amp in question.
on 24-10-2021 11:15
@what1x wrote:
Excuse for asking, how would any of this help where a technician wouldn't?
A BQM is irrefutable evident to show VM how poor your circuit is. Most users on these Forums set them up as an easy way to keep an eye on the circuit.
It's free and very useful.
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
24-10-2021 12:10 - edited 24-10-2021 12:15
@Adduxi wrote:
@what1x wrote:
Excuse for asking, how would any of this help where a technician wouldn't?A BQM is irrefutable evident to show VM how poor your circuit is. Most users on these Forums set them up as an easy way to keep an eye on the circuit.
It's free and very useful.
Okay, thank you. Let's say it was a poor circuit, what would you recommend?
on 26-10-2021 12:51
Hey @what1x,
I have looked into this further and our system has identified an issue that we need to resolve with a technician visit.
I can book 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.
Regards,
Steven_L