Menu
Reply
fitzy73london
  • 16
  • 0
  • 0
Tuning in
211 Views
Message 1 of 7
Flag for a moderator

Lagging / Latency issues

For both work and personal use, out service has been very poor for the last few days. We seem to be dropping multiple packets during Teams / Zoom / Online games etc. 

I've a VM 4 Hub, set up with a To Link Deco wireless system. I've run a few pings directly from the Hub4 and get various different timeout errors intermittently. 

Anyway, Monitor is here: 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/8afa414489c441906e933e002cb3566cc3...

 

 Will post other stats in next few posts. 

0 Kudos
Reply
fitzy73london
  • 16
  • 0
  • 0
Tuning in
210 Views
Message 2 of 7
Flag for a moderator

Re: Lagging / Latency issues

Downstream

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

30402750000-0.438.6QAM25630
11387500000.836.6QAM2561
21467500000.936.6QAM2562
31547500001.436.4QAM2563
4162750000136.6QAM2564
51707500000.536.6QAM2565
6178750000-0.237.4QAM2566
7186750000036.6QAM2567
81947500000.537.4QAM2568
92027500000.737.4QAM2569
102107500000.737.4QAM25610
112187500000.537.4QAM25611
12226750000037.4QAM25612
13234750000-0.637.4QAM25613
14242750000-0.937.4QAM25614
15250750000-0.437.4QAM25615
162587500000.237.6QAM25616
172667500000.837.4QAM25617
182747500000.837.6QAM25618
192827500000.637.4QAM25619
202907500000.337.4QAM25620
21298750000-0.237.6QAM25621
22306750000-0.337.6QAM25622
23314750000-0.137.6QAM25623
243227500000.137.6QAM25624
253307500000.237.6QAM25625
26370750000-1.237.6QAM25626
27378750000-1.437.4QAM25627
28386750000-137.4QAM25628
29394750000-0.537.6QAM25629
31410750000-0.639QAM25631



3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

30Locked38.60537700
1Locked36.60965300
2Locked36.60965300
3Locked36.38689000
4Locked36.60965310
5Locked36.60965320
6Locked37.35598800
7Locked36.60965300
8Locked37.35598800
9Locked37.35598800
10Locked37.35598800
11Locked37.35598800
12Locked37.35598800
13Locked37.35598800
14Locked37.35598800
15Locked37.35598800
16Locked37.63627600
17Locked37.35598800
18Locked37.63627600
19Locked37.35598800
20Locked37.35598800
21Locked37.63627600
22Locked37.63627600
23Locked37.63627600
24Locked37.63627600
25Locked37.63627600
26Locked37.63627600
27Locked37.35598800
28Locked37.35598800
29Locked37.63627600
31Locked38.98326100



3.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33864K1680QAM4096424


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
33Locked40-1.31992052380
0 Kudos
Reply
fitzy73london
  • 16
  • 0
  • 0
Tuning in
209 Views
Message 3 of 7
Flag for a moderator

Re: Lagging / Latency issues

Upstream

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

125800000485120 KSym/sec64QAM4
24620000049.35120 KSym/sec64QAM1
332600000485120 KSym/sec64QAM3
43940000048.35120 KSym/sec64QAM2



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000
0 Kudos
Reply
fitzy73london
  • 16
  • 0
  • 0
Tuning in
208 Views
Message 4 of 7
Flag for a moderator

Re: Lagging / Latency issues

Configuration

General Configuration

Network access
true
Maximum Number of CPEs
1
Baseline Privacy
true
DOCSIS Mode
3.1
Config file
cmreg-vmdg640-bbt060-b.cm



Primary Downstream Service Flow

SFID
42618
Max Traffic Rate
230000061
Max Traffic Burst
42600
Min Traffic Rate
0



Primary Upstream Service Flow

SFID
42617
Max Traffic Rate
22000061
Max Traffic Burst
42600
Min Traffic Rate
0
Max Concatenated Burst
42600
Scheduling Type
bestEffort
0 Kudos
Reply
fitzy73london
  • 16
  • 0
  • 0
Tuning in
207 Views
Message 5 of 7
Flag for a moderator

Re: Lagging / Latency issues

Network Log

 

Network Log

Time Priority Description

Thu 01/01/1970 00:01:173No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 16/12/2020 16:14:415MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 16/12/2020 16:17:496SW Download INIT - Via Config file cmreg-vmdg640-bbt060-b.cm
Wed 16/12/2020 16:19:036SW download Successful - Via Config file
Wed 16/12/2020 16:21:355MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 16/12/2020 16:51:004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 19/12/2020 18:01:083No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 20/12/2020 05:47:464DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 20/12/2020 18:31:213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 23/12/2020 17:47:464DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 29/12/2020 15:54:003No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 30/12/2020 17:47:464DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 06/01/2021 14:49:503No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 06/01/2021 17:47:464DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 07/01/2021 02:17:263No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 10/01/2021 05:47:474DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 11/01/2021 15:37:343No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 13/01/2021 17:47:474DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 15/01/2021 01:06:526SW Download INIT - Via NMS
Fri 15/01/2021 01:08:306SW download Successful - Via NMS
Thu 01/01/1970 00:01:193No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 15/01/2021 01:11:285MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 17/01/2021 21:29:394DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 21/01/2021 12:31:003No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/01/2021 14:08:534DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/01/2021 22:19:493No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 26/01/2021 19:08:045MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:203No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 26/01/2021 23:23:025MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 29/01/2021 06:45:534DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 01/02/2021 08:49:585MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 03/02/2021 05:30:043No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 04/02/2021 18:53:364DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 17/02/2021 10:01:015MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
jpeg1
  • 4.2K
  • 235
  • 668
Community elder
187 Views
Message 6 of 7
Flag for a moderator

Re: Lagging / Latency issues

I'm afraid you are suffering from the same problem as everyone else on here complaining of poor service. It's caused by millions of users all wanting to use the network for two-way video and other WFH uses. The network wasn't designed for that, and just can't cope.  OFCOM say that broadband use has increased by 100% over the lockdown, and Virgin have mentioned 95%.   

fitzy73london
  • 16
  • 0
  • 0
Tuning in
179 Views
Message 7 of 7
Flag for a moderator

Re: Lagging / Latency issues

Thanks, it's generally ok most of the time, but when it's bad it's utterly unusable. 

I suppose with this week being half term the kids are probably saturating the network as well. 

It's slightly frustrating as I've no FTTH / poor FTTC in my area, so no real alternative to VM over 100mb. 

0 Kudos
Reply