on 15-02-2023 22:01
I've been having erratic issues with ping for a few weeks now. Thought it might be a recurrence of an earlier issue with my coax cable, but no longer sure this is the case. Router stats:
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
26 | 338750000 | 7.900002 | 40.946209 | QAM256 | 26 |
1 | 138750000 | 7.599998 | 38.983261 | QAM256 | 1 |
2 | 146750000 | 7.599998 | 38.983261 | QAM256 | 2 |
3 | 154750000 | 7.199997 | 38.983261 | QAM256 | 3 |
4 | 162750000 | 7.099998 | 38.983261 | QAM256 | 4 |
5 | 170750000 | 7.199997 | 38.983261 | QAM256 | 5 |
6 | 178750000 | 7.199997 | 40.366287 | QAM256 | 6 |
7 | 186750000 | 7.199997 | 38.983261 | QAM256 | 7 |
8 | 194750000 | 7.099998 | 38.983261 | QAM256 | 8 |
9 | 202750000 | 7.099998 | 38.983261 | QAM256 | 9 |
10 | 210750000 | 7.099998 | 38.983261 | QAM256 | 10 |
11 | 218750000 | 7.000000 | 38.983261 | QAM256 | 11 |
12 | 226750000 | 6.800003 | 38.983261 | QAM256 | 12 |
13 | 234750000 | 6.599998 | 38.605377 | QAM256 | 13 |
14 | 242750000 | 6.800003 | 38.983261 | QAM256 | 14 |
15 | 250750000 | 6.800003 | 38.983261 | QAM256 | 15 |
16 | 258750000 | 6.900002 | 40.366287 | QAM256 | 16 |
17 | 266750000 | 6.900002 | 40.366287 | QAM256 | 17 |
18 | 274750000 | 7.400002 | 40.366287 | QAM256 | 18 |
19 | 282750000 | 7.599998 | 38.983261 | QAM256 | 19 |
20 | 290750000 | 7.900002 | 38.983261 | QAM256 | 20 |
21 | 298750000 | 7.400002 | 40.366287 | QAM256 | 21 |
22 | 306750000 | 7.300003 | 40.366287 | QAM256 | 22 |
23 | 314750000 | 7.500000 | 40.366287 | QAM256 | 23 |
24 | 322750000 | 8.000000 | 40.946209 | QAM256 | 24 |
25 | 330750000 | 8.300003 | 40.366287 | QAM256 | 25 |
27 | 346750000 | 7.500000 | 40.366287 | QAM256 | 27 |
28 | 354750000 | 7.199997 | 38.983261 | QAM256 | 28 |
29 | 362750000 | 7.000000 | 38.983261 | QAM256 | 29 |
30 | 370750000 | 6.800003 | 38.983261 | QAM256 | 30 |
31 | 378750000 | 6.199997 | 38.605377 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
26 | Locked | 40.946209 | 6 | 0 |
1 | Locked | 38.983261 | 0 | 0 |
2 | Locked | 38.983261 | 5 | 0 |
3 | Locked | 38.983261 | 0 | 0 |
4 | Locked | 38.983261 | 0 | 0 |
5 | Locked | 38.983261 | 6 | 0 |
6 | Locked | 40.366287 | 0 | 0 |
7 | Locked | 38.983261 | 0 | 0 |
8 | Locked | 38.983261 | 0 | 0 |
9 | Locked | 38.983261 | 0 | 0 |
10 | Locked | 38.983261 | 8 | 0 |
11 | Locked | 38.983261 | 1 | 0 |
12 | Locked | 38.983261 | 0 | 0 |
13 | Locked | 38.605377 | 6 | 0 |
14 | Locked | 38.983261 | 0 | 0 |
15 | Locked | 38.983261 | 7 | 0 |
16 | Locked | 40.366287 | 5 | 0 |
17 | Locked | 40.366287 | 0 | 0 |
18 | Locked | 40.366287 | 6 | 0 |
19 | Locked | 38.983261 | 0 | 0 |
20 | Locked | 38.983261 | 7 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.366287 | 0 | 0 |
23 | Locked | 40.366287 | 0 | 0 |
24 | Locked | 40.946209 | 8 | 0 |
25 | Locked | 40.366287 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 38.983261 | 0 | 0 |
29 | Locked | 38.983261 | 0 | 0 |
30 | Locked | 38.983261 | 0 | 0 |
31 | Locked | 38.605377 | 0 | 0 |
159 | 94 | 4K | 1840 | QAM1024 | 424 |
159 | Locked | 43 | 7.3 | 51395686 | 0 |
on 26-03-2023 18:21
I've posted most of this on previous pages, but will do so again. Ping is terrible this evening - and I note my upstream speed is down from its usual level in speedtest. Implies there's an upstream congestion issue?
Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream
Cable Modem Status | Online | DOCSIS 3.1 |
Primary downstream channel | Locked | SC-QAM |
DOCSIS 3.0 channels | 31 | 4 |
DOCSIS 3.1 channels | 1 | 0 |
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 138750000 | 7.000000 | 38.983261 | QAM256 | 1 |
2 | 146750000 | 6.800003 | 38.605377 | QAM256 | 2 |
3 | 154750000 | 6.199997 | 38.983261 | QAM256 | 3 |
4 | 162750000 | 6.099998 | 38.983261 | QAM256 | 4 |
5 | 170750000 | 6.099998 | 38.983261 | QAM256 | 5 |
6 | 178750000 | 6.199997 | 40.366287 | QAM256 | 6 |
7 | 186750000 | 6.099998 | 40.946209 | QAM256 | 7 |
8 | 194750000 | 5.900002 | 38.605377 | QAM256 | 8 |
9 | 202750000 | 5.699997 | 38.983261 | QAM256 | 9 |
10 | 210750000 | 5.500000 | 38.983261 | QAM256 | 10 |
11 | 218750000 | 5.500000 | 38.605377 | QAM256 | 11 |
12 | 226750000 | 5.300003 | 38.983261 | QAM256 | 12 |
13 | 234750000 | 5.099998 | 38.983261 | QAM256 | 13 |
14 | 242750000 | 5.000000 | 38.983261 | QAM256 | 14 |
15 | 250750000 | 4.800003 | 38.605377 | QAM256 | 15 |
16 | 258750000 | 4.699997 | 38.983261 | QAM256 | 16 |
17 | 266750000 | 4.699997 | 38.983261 | QAM256 | 17 |
18 | 274750000 | 5.199997 | 38.983261 | QAM256 | 18 |
19 | 282750000 | 5.599998 | 38.983261 | QAM256 | 19 |
20 | 290750000 | 6.400002 | 38.983261 | QAM256 | 20 |
21 | 298750000 | 6.300003 | 40.366287 | QAM256 | 21 |
22 | 306750000 | 5.900002 | 40.366287 | QAM256 | 22 |
23 | 314750000 | 6.000000 | 40.366287 | QAM256 | 23 |
24 | 322750000 | 6.300003 | 40.366287 | QAM256 | 24 |
25 | 330750000 | 6.400002 | 40.366287 | QAM256 | 25 |
26 | 338750000 | 5.800003 | 38.983261 | QAM256 | 26 |
27 | 346750000 | 5.400002 | 40.366287 | QAM256 | 27 |
28 | 354750000 | 5.199997 | 38.983261 | QAM256 | 28 |
29 | 362750000 | 5.099998 | 38.605377 | QAM256 | 29 |
30 | 370750000 | 5.000000 | 38.605377 | QAM256 | 30 |
31 | 378750000 | 4.300003 | 38.983261 | QAM256 | 31 |
on 26-03-2023 18:22
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.983261 | 0 | 0 |
2 | Locked | 38.605377 | 0 | 0 |
3 | Locked | 38.983261 | 0 | 0 |
4 | Locked | 38.983261 | 0 | 0 |
5 | Locked | 38.983261 | 0 | 0 |
6 | Locked | 40.366287 | 0 | 0 |
7 | Locked | 40.946209 | 0 | 0 |
8 | Locked | 38.605377 | 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.983261 | 0 | 0 |
15 | Locked | 38.605377 | 0 | 0 |
16 | Locked | 38.983261 | 0 | 0 |
17 | Locked | 38.983261 | 0 | 0 |
18 | Locked | 38.983261 | 0 | 0 |
19 | Locked | 38.983261 | 0 | 0 |
20 | Locked | 38.983261 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.366287 | 0 | 0 |
23 | Locked | 40.366287 | 0 | 0 |
24 | Locked | 40.366287 | 0 | 0 |
25 | Locked | 40.366287 | 0 | 0 |
26 | Locked | 38.983261 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 38.983261 | 0 | 0 |
29 | Locked | 38.605377 | 0 | 0 |
30 | Locked | 38.605377 | 0 | 0 |
31 | Locked | 38.983261 | 0 | 0 |
159 | 94 | 4K | 1800 | QAM4096 | 424 |
159 | Locked | 42 | 4.3 | 2623480 | 0 |
1 | 32600000 | 42.020599 | 5120 KSym/sec | 64QAM | 4 |
2 | 25800000 | 41.520599 | 5120 KSym/sec | 64QAM | 5 |
3 | 39400000 | 42.520599 | 5120 KSym/sec | 64QAM | 3 |
4 | 46200000 | 42.020599 | 5120 KSym/sec | 64QAM | 2 |
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 |
on 26-03-2023 18:23
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | kfoA,.iyewrkldJKDHSUBsgvc |
SFID | 21554 |
Max Traffic Rate | 1200000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 21557 |
Max Traffic Rate | 55000270 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | bestEffort |
Time Priority Description
Sun Mar 26 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Mar 26 | 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; |
Sun Mar 26 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Mar 26 | 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; |
Sun Mar 26 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Mar 26 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Mar 25 | 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; |
Sat Mar 25 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 24 | 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; |
Fri Mar 24 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Mar 24 | 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; |
Fri Mar 24 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 23 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 23 | 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; |
26-03-2023 18:24 - edited 26-03-2023 18:25
https://www.thinkbroadband.com/broadband/monitoring/quality/share/514d6fbb54a0b2e7ef89c203f4c80b8ad480bada
on 26-03-2023 20:38
There's nothing wrong with your connection data. You have the common problem of sharing your local network with too many users that Virginmedia have signed up to use it.
You can complain of course, but...
on 29-03-2023 09:29
Hi @Rogueywon thanks for getting back to us.
Sorry to hear of your ping issues and for any inconvenience this may be causing your household. I would like to have a look on your behalf. I am going to send you a private message. Please look out for the purple envelope in the top right of your screen.
Regards
Lee_R
on 09-04-2023 22:42
After a week of being pretty much fine (other than the national outages on Tuesday, of course), the ping's gone to hell again this evening.
on 12-04-2023 09:55
Hey Rogueywon, thanks for keeping the thread updated with this.
I am sorry to read the connection issue has re-occurred, I can see you've previously spoken to our forum team privately a couple of times and we've offered support with this.
Could you please confirm if this was a fix by tech visit we did last time and has your hub been replaced recently?
Upon our latest checks there are no known issues in your area network to explain this issue at this time.
Please, can you confirm whether you have any 3rd party equipment currently in use and if you have access to broadband and Wi Fi currently?
Let us know where you are with this and we're here to assist.
on 12-04-2023 10:35
Your shared BQM is still showing over utilisation in peak hours, as pointed out by @jpeg1 last week. The time scale for fixing such issues can be quite long.
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 12-04-2023 10:50
But @Adri_G is following this, so hopefully they will be able to get something done to resolve it.