Menu
Reply
mushka1977
  • 9
  • 0
  • 0
Joining in
693 Views
Message 1 of 14
Flag for a moderator

high ping and packet loss

hi i had virgin installed on 3rd may 2021 M200, had it installed to spare room were i have a ps5 & ps4 both wired connection to hub 4, been fine tbh, up untill 1st nov were i started to have lag  high ping and packet loss, on ps5 i play cod cold war & cod vanguard, every game i play within 10 - 25 seconds i start laggin, i press options it shows ping & packet loss icon, my ping shows 30-40,  then it drops to 0 then shoots up to 400 or even higher, packet loss goes to over 100 or higher, on ps4 i play warzone and battlefield 1, warzone pre game lobbys start to lag, check ping says 30 -50, goes to 0 then sky rockets up  to 500 or higher, packet loss goes over 100 or higher,  ive tried restarting hub, pin hole reset, purchased new ethernet cables, still having same issue,  this morning logged into router ran diagnostic and it says  your home network has a few problems. but does state what problems. will add additional info soon. thanks

0 Kudos
Reply
Adduxi
  • 6.08K
  • 511
  • 1.57K
Very Insightful Person
Very Insightful Person
689 Views
Message 2 of 14
Flag for a moderator

Re: high ping and packet loss

Check with Area faults on 0800 561 0061 or if you have a VM landline 150 as small local faults are not listed on the VM status page.

Please post up your power levels, Pre and PostRS errors and Network log.  Also setup a BQM here www.thinkbroadband.com/ping

Once done we can comment on the state of your circuit.

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

0 Kudos
Reply
mushka1977
  • 9
  • 0
  • 0
Joining in
681 Views
Message 3 of 14
Flag for a moderator

Re: high ping and packet loss

thanks for quick reply, tried area faults, says no problems in my area,, i have a bqm running, on top of graph it shows name i created and it shows ip, beginning with 77,  will that show when i click share, as on settings it says ip/host name, but i cant change that, keeps saying invalid, 

0 Kudos
Reply
Adduxi
  • 6.08K
  • 511
  • 1.57K
Very Insightful Person
Very Insightful Person
674 Views
Message 4 of 14
Flag for a moderator

Re: high ping and packet loss

A shared BQM will not have your IP address,  so it's safe to post.   Just follow the instructions and you should be good to go.

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

0 Kudos
Reply
mushka1977
  • 9
  • 0
  • 0
Joining in
666 Views
Message 5 of 14
Flag for a moderator

Re: high ping and packet loss

https://www.thinkbroadband.com/broadband/monitoring/quality/share/7d1c864fd87245b16094738bf71103e4da3543c2
0 Kudos
Reply
mushka1977
  • 9
  • 0
  • 0
Joining in
658 Views
Message 6 of 14
Flag for a moderator

Re: high ping and packet loss

3.0 Downstream channels

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

2147000000-1.59999838.983261QAM2562
1139000000-1.70000138.605377QAM2561
3155000000-1.40000238.983261QAM2563
4163000000-1.59999838.983261QAM2564
5171000000-1.59999838.983261QAM2565
6179000000-1.59999838.983261QAM2566
7187000000-1.59999838.983261QAM2567
8195000000-1.59999838.605377QAM2568
9203000000-1.59999838.605377QAM2569
10211000000-1.40000238.605377QAM25610
11219000000-1.29999940.366287QAM25611
12227000000-1.50000040.366287QAM25612
13235000000-1.59999838.983261QAM25613
14243000000-1.59999840.946209QAM25614
15251000000-1.70000138.983261QAM25615
16259000000-1.70000138.983261QAM25616
17267000000-2.00000038.983261QAM25617
18275000000-2.09999838.983261QAM25618
19283000000-2.70000140.366287QAM25619
20291000000-3.00000040.366287QAM25620
21299000000-2.90000238.983261QAM25621
22307000000-2.79999938.983261QAM25622
23315000000-2.59999840.366287QAM25623
24323000000-2.50000038.605377QAM25624
25331000000-2.79999938.983261QAM25625
26339000000-2.79999938.983261QAM25626
27347000000-2.70000138.605377QAM25627
28355000000-2.79999938.605377QAM25628
29363000000-2.79999938.983261QAM25629
30371000000-2.90000238.983261QAM25630
31379000000-2.79999940.366287QAM25631



3.0 Downstream channels

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

2Locked38.98326100
1Locked38.605377110
3Locked38.98326100
4Locked38.98326100
5Locked38.98326100
6Locked38.98326100
7Locked38.98326100
8Locked38.60537700
9Locked38.60537700
10Locked38.60537700
11Locked40.36628700
12Locked40.36628700
13Locked38.98326100
14Locked40.94620900
15Locked38.983261130
16Locked38.98326100
17Locked38.98326100
18Locked38.98326100
19Locked40.36628700
20Locked40.36628700
21Locked38.98326100
22Locked38.98326100
23Locked40.36628700
24Locked38.60537700
25Locked38.98326100
26Locked38.98326100
27Locked38.60537700
28Locked38.60537700
29Locked38.98326100
30Locked38.98326100
31Locked40.36628700
0 Kudos
Reply
mushka1977
  • 9
  • 0
  • 0
Joining in
657 Views
Message 7 of 14
Flag for a moderator

Re: high ping and packet loss

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

159964K1880QAM1024392



3.1 Downstream channels

Channel ID Lock Status  (dB) PLC Power  (Active Profile)  (Active Profile)

159Locked42-2.1101052700
0 Kudos
Reply
mushka1977
  • 9
  • 0
  • 0
Joining in
656 Views
Message 8 of 14
Flag for a moderator

Re: high ping and packet loss

3.0 Upstream channels

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

15370000035.7705995120 KSym/sec64QAM10
23940000035.7705995120 KSym/sec64QAM12
34620000035.2705995120 KSym/sec64QAM11
46030000035.7705995120 KSym/sec64QAM9



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
mushka1977
  • 9
  • 0
  • 0
Joining in
655 Views
Message 9 of 14
Flag for a moderator

Re: high ping and packet loss

 
 
 
 

Network Log

Time Priority Description
Sun Sep 12 06:27:36 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 13 18:30:39 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 15 18:27:36 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 15 18:27:36 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 17 17:29:53 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 19 06:27:36 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 19 06:27:36 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Sep 20 00:15:58 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 18:27:37 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 18:27:37 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Sep 25 14:25:47 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 26 06:27:37 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 26 06:27:37 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Sep 26 07:51:07 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 29 18:27:37 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 29 18:27:37 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 1 10:08:04 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 3 06:27:37 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 3 06:27:37 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Oct 5 22:59:18 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 6 18:27:37 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 6 18:27:37 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 10 06:27:38 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 10 06:27:38 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 13 18:27:38 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 13 18:27:38 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 17 06:27:38 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 17 06:27:38 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Oct 18 16:03:45 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 20 18:27:38 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 20 18:27:38 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 24 06:27:38 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 24 06:27:38 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 27 18:27:38 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct 27 18:27:39 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 30 18:54:33 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 31 06:27:39 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct 31 06:27:39 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Nov 1 18:42:26 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Nov 1 18:54:41 20215DBC-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;
Thu Nov 4 12:35:10 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Nov 4 12:35:11 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 5 22:01:13 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 7 16:01:39 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 7 16:01:39 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 7 18:03:20 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
mushka1977
  • 9
  • 0
  • 0
Joining in
641 Views
Message 10 of 14
Flag for a moderator

Re: high ping and packet loss

hope that is all correct info needed.  just to add as well, i live a lone so there is only my self using the service,, which is all connected and set up upstairs in spare room were hub 4 is set up is and ps5 & ps4,, i also have plusnet fttc 40/10 downstairs in living room, ive tried both ps5 & ps4 connected to router down stairs, same cables etc and no lag at all, its got to be a issue with virgin media connection. 

0 Kudos
Reply