Menu
Reply
akashmash
  • 11
  • 0
  • 1
On our wavelength
560 Views
Message 1 of 12
Flag for a moderator

1Gig Hub 4, ping spiking and boosters slow.

Hello! 

This is a bit of a double question, apologies. 

Firstly I've been having awful ping spikes making any gaming impossible at peak times (don't fancy playing between 12-7am) for the past 2 weeks. Before this I noticed less frequent ping issues but more than on my old hub 3.

Secondly my WiFi pod boosters can barely give me speeds of between 20-100mb, even when plugged in right next to the router to test.

I think I'm armed with a couple days worth of BQMs, but I'm assuming people will need more information to help meaningfully, happy to post whatever is required.

c43a8c29e0c4049ea6dbf78846375f60a8a0a517-17-12-2021.png

c43a8c29e0c4049ea6dbf78846375f60a8a0a517-16-12-2021.png

c43a8c29e0c4049ea6dbf78846375f60a8a0a517-15-12-2021.png

Thanks 

😊

0 Kudos
Reply
akashmash
  • 11
  • 0
  • 1
On our wavelength
548 Views
Message 2 of 12
Flag for a moderator

Re: 1Gig Hub 4, ping spiking and boosters slow.

Cable Modem StatusItemStatusCommentsCable Modem Status

Online
DOCSIS 3.1

Primary downstream channel

Locked
SC-QAM

Channel OverviewDownstreamUpstreamDOCSIS 3.0 channels

31
4

DOCSIS 3.1 channels

1
0
0 Kudos
Reply
akashmash
  • 11
  • 0
  • 1
On our wavelength
547 Views
Message 3 of 12
Flag for a moderator

Re: 1Gig Hub 4, ping spiking and boosters slow.

3.0 Downstream channels

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

253310000001.439QAM25625
11390000001.840.4QAM2561
21470000001.740.4QAM2562
31550000001.840.4QAM2563
41630000001.640.4QAM2564
51710000001.640.4QAM2565
61790000001.640.9QAM2566
71870000001.740.4QAM2567
81950000002.140.4QAM2568
92030000002.240.4QAM2569
102110000002.440.4QAM25610
112190000002.440.4QAM25611
122270000002.340.4QAM25612
132350000002.340.9QAM25613
142430000002.140.4QAM25614
152510000001.940.4QAM25615
162590000002.240.4QAM25616
172670000002.540.9QAM25617
18275000000340.4QAM25618
192830000002.640.4QAM25619
20291000000240.4QAM25620
212990000001.940.4QAM25621
22307000000240.4QAM25622
233150000002.240.9QAM25623
243230000002.240.4QAM25624
263390000001.640.4QAM25626
273470000001.340.4QAM25627
283550000001.240.4QAM25628
293630000001.139QAM25629
303710000001.540.4QAM25630
313790000001.540.4QAM25631
0 Kudos
Reply
akashmash
  • 11
  • 0
  • 1
On our wavelength
546 Views
Message 4 of 12
Flag for a moderator

Re: 1Gig Hub 4, ping spiking and boosters slow.

  • 3.0 Downstream channels

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

25Locked38.98326100
1Locked40.36628700
2Locked40.36628700
3Locked40.36628700
4Locked40.36628700
5Locked40.36628700
6Locked40.94620900
7Locked40.36628700
8Locked40.36628700
9Locked40.36628700
10Locked40.36628700
11Locked40.36628700
12Locked40.36628700
13Locked40.94620900
14Locked40.36628700
15Locked40.36628700
16Locked40.36628700
17Locked40.94620900
18Locked40.36628700
19Locked40.36628700
20Locked40.36628700
21Locked40.36628700
22Locked40.36628700
23Locked40.94620900
24Locked40.36628700
26Locked40.36628700
27Locked40.36628700
28Locked40.36628700
29Locked38.98326100
30Locked40.36628700
31Locked40.36628700



3.1 Downstream channels

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


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked433.42426517730
0 Kudos
Reply
akashmash
  • 11
  • 0
  • 1
On our wavelength
544 Views
Message 5 of 12
Flag for a moderator

Re: 1Gig Hub 4, ping spiking and boosters slow.

3.0 Upstream channels

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

146200000405120 KSym/sec64QAM1
225800000405120 KSym/sec64QAM4
332600000405120 KSym/sec64QAM3
439400000405120 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

 

General Configuration

Network access
true
Maximum Number of CPEs
1
Baseline Privacy
true
DOCSIS Mode
3.1
Config file
cxv9873254k;fg87dsfd;kfoA,.iy



Primary Downstream Service Flow

SFID
18540
Max Traffic Rate
1200000450
Max Traffic Burst
42600
Min Traffic Rate
0



Primary Upstream Service Flow

SFID
18539
Max Traffic Rate
55000270
Max Traffic Burst
42600
Min Traffic Rate
0
Max Concatenated Burst
16320
Scheduling Type
bestEffort
0 Kudos
Reply
akashmash
  • 11
  • 0
  • 1
On our wavelength
424 Views
Message 6 of 12
Flag for a moderator

Re: At what point does virgin media fix their problems?

I'm having the same issues, as are apparently a good chunk of the customer base judging from the amount of posts I'm seeing on the forums.

I really do hope they can sort the issues out for me, gaming has been so useful to connect with people since I'm more compromised health wise and avoid leaving the house unnecessarily due to current events.

Think I'll be taking this to the press with how widespread the issues are, I've already been talking with a few editors about it. 

0 Kudos
Reply
akashmash
  • 11
  • 0
  • 1
On our wavelength
538 Views
Message 7 of 12
Flag for a moderator

Re: 1Gig Hub 4, ping spiking and boosters slow.

Network Log

Time Priority Description

Tue 19/10/2021 16:03:326DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 20/10/2021 09:48:093No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 23/10/2021 04:03:324DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 23/10/2021 04:03:326DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 25/10/2021 14:34:315MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 26/10/2021 01:24:363No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 27/10/2021 21:18:544DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 27/10/2021 21:18:556DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 29/10/2021 20:56:093No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 30/10/2021 10:49:575MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 01/11/2021 12:09:153No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 03/11/2021 21:32:014DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 03/11/2021 21:32:016DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 03/11/2021 23:25:543No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 08/11/2021 17:01:594DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 08/11/2021 17:02:014DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 08/11/2021 17:02:016DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 10/11/2021 11:25:163No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 11/11/2021 13:16:594DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 11/11/2021 13:16:596DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 13/11/2021 14:39:233No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 14/11/2021 17:54:274DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 14/11/2021 17:54:286DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 15/11/2021 15:48:205MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/11/2021 03:28:393No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/11/2021 16:51:224DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/11/2021 16:51:236DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 20/11/2021 01:45:563No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 21/11/2021 23:53:014DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 21/11/2021 23:53:016DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/11/2021 07:08:293No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/11/2021 11:53:014DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/11/2021 11:53:016DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 26/11/2021 12:01:283No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 28/11/2021 23:53:014DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 28/11/2021 23:53:016DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 29/11/2021 16:59:053No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/12/2021 11:53:014DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/12/2021 11:53:016DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 04/12/2021 23:31:363No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 05/12/2021 23:53:014DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 05/12/2021 23:53:026DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 06/12/2021 21:59:093No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 07/12/2021 20:14:125MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 10/12/2021 10:03:394DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 10/12/2021 10:03:406DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 11/12/2021 05:12:333No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 13/12/2021 11:28:294DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

0 Kudos
Reply
Andrew-G
  • 9.53K
  • 1.54K
  • 4.55K
Very Insightful Person
Very Insightful Person
487 Views
Message 8 of 12
Flag for a moderator
Helpful Answer

Re: 1Gig Hub 4, ping spiking and boosters slow.

I'll leave pod or booster issues to others, as they're not something I know about, and my preferred wifi solution is to take all of it out of VM's hands and do the job properly, but that costs money.

On the connection quality, there's a couple of things - first the possible impact of the latest work from home guidance which means that whilst this lasts there's a lot more problems (for some areas) on the upstream side of VM's network, creating latency problems that affect gamers, any Teams/Zoom/Skype types of use, and live streaming.  There's not much VM can do about that, as its a result of the network not being designed for this pattern of usage, and changing that would take far longer than the current issues will last.  VM are improving capacity all the time, but it's a long, slow technically complicated task, and not something they can suddenly accelerate or deliver to every affected area.   

The second thing is that it looks to me like the power levels may be out, as the DOCSIS 3.1 power level looks to me far too high relative to the D 3.0 channels, and those are a bit variable to boot.  This can be addressed, but I'm not sure whether the Fisher Price diagnostics that VM use will recognise that pattern of power level problems, and if they don't you'll need a staff member who can interpret the numbers  - wait and see what the forum staff have to say.

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

Hayley_S
  • 3.4K
  • 109
  • 225
Forum Team
Forum Team
393 Views
Message 9 of 12
Flag for a moderator

Re: 1Gig Hub 4, ping spiking and boosters slow.

Hello @akashmash

Welcome to the community, thanks for posting.

I am sorry for the issues with your broadband.

Are you using any 3rd party devices? 

Many thanks,

Hayley
Forum Team



New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
akashmash
  • 11
  • 0
  • 1
On our wavelength
389 Views
Message 10 of 12
Flag for a moderator

Re: 1Gig Hub 4, ping spiking and boosters slow.

Hi Hayley,

Nope, Hub 4 + 2 wifi pods. Seeing people post very similar issues to mine on the forums and elsewhere daily now, getting worried that it's not something that you can fix quickly. 

0 Kudos
Reply