Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Huge Ping Spikes and packet loss warnings in games and 1/20 webpages wont load on the first try

Noodlefox
Tuning in

on ‎26-04-2022 18:32

Hey folks! 

I'm getting massive ping spikes and disconnections in at least 5 different games i've tried (some more sensitive than others). Webpages either load instantly or hang forever. seemingly biased towards things I know to be hosted on AWS. If I bump through a VPN it clears up to some degree but adds to the latency.

I'm hoping someone can sanity check me. I seem to be having problems all over with my internet connection. I've got some hefty networking kit but i've cut it all out and get similar results. 

Would someone be able to sanity check me? it would be much appreciated. 

I get constant timeouts when i'm running traceroute which rings alarm bells for me. I seem to get better performance via a VPN I can't quite get my head around why that would be since the tunnel still runs through virgin equipment. (any thoughts? VG perhaps bouncing TR requests intentionally?)

traceroute to google.com (216.58.212.206), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.799 ms 0.800 ms 0.623 ms
2 10.53.39.129 (10.53.39.129) 10.160 ms 11.361 ms 10.262 ms
3 nott-core-2b-ae56-0.network.virginmedia.net (62.255.214.93) 11.486 ms 10.247 ms 14.135 ms
4 * * *
5 eislou2-ic-1-ae3-0.network.virginmedia.net (62.254.85.145) 15.703 ms 14.383 ms 14.948 ms
6 6-14-250-212.static.virginm.net (212.250.14.6) 16.961 ms 13.820 ms 14.981 ms
7 * * *
8 74.125.242.97 (74.125.242.97) 16.981 ms 22.434 ms
172.253.66.98 (172.253.66.98) 19.348 ms
9 ams16s21-in-f206.1e100.net (216.58.212.206) 26.403 ms
74.125.242.82 (74.125.242.82) 17.699 ms
74.125.242.115 (74.125.242.115) 19.874 ms

  
My Downstream:

3.0 Downstream channels
Channel	Frequency (Hz)	Power (dBmV)	SNR (dB)	Modulation	Channel ID
5	171000000	1.200001	38.983261	QAM256	5
1	139000000	1.599998	38.983261	QAM256	1
2	147000000	1.299999	38.983261	QAM256	2
3	155000000	1.299999	38.983261	QAM256	3
4	163000000	1.400002	38.983261	QAM256	4
6	179000000	1.200001	38.983261	QAM256	6
7	187000000	1.099998	38.983261	QAM256	7
8	195000000	1.099998	38.983261	QAM256	8
9	203000000	0.900002	38.983261	QAM256	9
10	211000000	0.799999	38.983261	QAM256	10
11	219000000	0.400002	38.983261	QAM256	11
12	227000000	-0.299999	38.983261	QAM256	12
13	235000000	-0.700001	38.605377	QAM256	13
14	243000000	0.099998	38.605377	QAM256	14
15	251000000	0.599998	38.983261	QAM256	15
16	259000000	0.299999	38.983261	QAM256	16
17	267000000	0.500000	38.605377	QAM256	17
18	275000000	1.200001	38.983261	QAM256	18
19	283000000	0.900002	38.983261	QAM256	19
20	291000000	0.900002	38.983261	QAM256	20
21	299000000	1.500000	38.605377	QAM256	21
22	307000000	2.200001	38.983261	QAM256	22
23	315000000	2.900002	38.983261	QAM256	23
24	323000000	2.700001	38.983261	QAM256	24
25	331000000	1.700001	38.983261	QAM256	25
26	339000000	0.700001	38.605377	QAM256	26
27	347000000	0.500000	38.605377	QAM256	27
28	355000000	0.299999	38.605377	QAM256	28
29	363000000	0.400002	38.605377	QAM256	29
30	371000000	0.900002	38.983261	QAM256	30
31	379000000	0.700001	38.983261	QAM256	31


3.0 Downstream channels
Channel	Lock Status	RxMER (dB)	Pre RS Errors	Post RS Errors
5	Locked	38.983261	0	0
1	Locked	38.983261	0	0
2	Locked	38.983261	0	0
3	Locked	38.983261	0	0
4	Locked	38.983261	0	0
6	Locked	38.983261	0	0
7	Locked	38.983261	0	0
8	Locked	38.983261	0	0
9	Locked	38.983261	0	0
10	Locked	38.983261	0	0
11	Locked	38.983261	0	0
12	Locked	38.983261	0	0
13	Locked	38.605377	0	0
14	Locked	38.605377	0	0
15	Locked	38.983261	0	0
16	Locked	38.983261	0	0
17	Locked	38.605377	0	0
18	Locked	38.983261	0	0
19	Locked	38.983261	0	0
20	Locked	38.983261	0	0
21	Locked	38.605377	0	0
22	Locked	38.983261	0	0
23	Locked	38.983261	0	0
24	Locked	38.983261	0	0
25	Locked	38.983261	0	0
26	Locked	38.605377	0	0
27	Locked	38.605377	0	0
28	Locked	38.605377	0	0
29	Locked	38.605377	0	0
30	Locked	38.983261	0	0
31	Locked	38.983261	0	0


3.1 Downstream channels
Channel	Channel Width (MHz)	FFT Type	Number of Active Subcarriers	Modulation (Active Profile)	First Active Subcarrier (Hz)
159	96	4K	1880	QAM4096	759


3.1 Downstream channels
Channel ID	Lock Status	RxMER Data (dB)	PLC Power (dBmV)	Correcteds (Active Profile)	Uncorrectables (Active Profile)
159	Locked	40	-1.4	3340790327	835

 

My Upstream Channels:

3.0 Upstream channels
Channel	Frequency (Hz)	Power (dBmV)	Symbol Rate (ksps)	Modulation	Channel ID
1	25800000	44.270599	5120 KSym/sec	64QAM	4
2	32600000	44.770599	5120 KSym/sec	64QAM	3
3	39400000	44.270599	5120 KSym/sec	64QAM	2
4	46200000	44.270599	5120 KSym/sec	64QAM	1


3.0 Upstream channels
Channel	Channel Type	T1 Timeouts	T2 Timeouts	T3 Timeouts	T4 Timeouts
1	US_TYPE_STDMA	0	0	14	0
2	US_TYPE_STDMA	0	0	16	0
3	US_TYPE_STDMA	0	0	12	0
4	US_TYPE_STDMA	0	0	22	0


config

General Configuration
Network access	
true
Maximum Number of CPEs	
1
Baseline Privacy	
true
DOCSIS Mode	
3.1
Config file	
k;fg87dsfd;kfoA,.iyewrkld


Primary Downstream Service Flow
SFID	
396
Max Traffic Rate	
1200000450
Max Traffic Burst	
42600
Min Traffic Rate	
0


Primary Upstream Service Flow
SFID	
395
Max Traffic Rate	
55000270
Max Traffic Burst	
42600
Min Traffic Rate	
0
Max Concatenated Burst	
16320
Scheduling Type	
bestEffort


Networklog is empty


When I upgraded to 1Gig I was told that the connection on my street is old but the Traceroute makes me think there's something iffy in the Notts Exch ?

Any insight would be massively appreciated! 

 

0 Kudos
13 REPLIES 13

Noodlefox
Tuning in

on ‎26-04-2022 19:03

It's worth noting I also have a Noise Attenuator on the line from the original (few hubs ago) installation.

0 Kudos

Noodlefox
Tuning in
In response to Noodlefox

on ‎26-04-2022 21:09

Having read more i realise that the traceroute timeouts are just devices intentionally not responding to traceroute requests. 

0 Kudos

Noodlefox
Tuning in
In response to Noodlefox

on ‎26-04-2022 21:28

d3ee761ef8f0e3393f4f474dacada8192979fe7d-23-04-2022.pngd3ee761ef8f0e3393f4f474dacada8192979fe7d-20-04-2022.png

0 Kudos

SCA1972
Very Insightful Person
Very Insightful Person
In response to Noodlefox

‎26-04-2022 21:55 - edited ‎26-04-2022 21:55

@Noodlefox Your BQM images have been rejected as they contained your WAN IP address and this is against the forum rules, to protect your privacy.  If you use the share options on the BQM page you can add a link or embed an image of your graph without your IP address.

______________________
Scott

My setup: VM TV 360 box, M350 Fibre broadband with Hub 3 in modem mode connected to a Netgear R7000 router. Telewest/VM user since 2001.

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

Noodlefox
Tuning in
In response to SCA1972

on ‎26-04-2022 22:04

Thanks for the Save @SCA1972 !

looking back these have been the same for the weeks since I set the tracker up.

d3ee761ef8f0e3393f4f474dacada8192979fe7d-23-04-2022.jpgd3ee761ef8f0e3393f4f474dacada8192979fe7d-20-04-2022.jpg

0 Kudos

ReactUK
On our wavelength
In response to Noodlefox

on ‎27-04-2022 11:52

What attenuator is in there currently, should be written on it. VM engineer left me one and it was causing more issues than it was fixing.

Ignore the drops in trace routes, routers don't bother responding because ICMP is a waste of resource.

That BQM looks like oversubscription personally... but I haven't got a clue on the sync rates, I don't like the minus values.

Noodlefox
Tuning in
In response to ReactUK

on ‎27-04-2022 12:03

Thanks for the reply! it's a 6db it wouldn't do any harm to pull it since I can put it back later.
I'll pull it out later when the connection is less in use. Thanks for your insight I'll more digging on these forums for other graphs that look similar. I'm aware the ongoing problem is probably causing the red outs and some of the pattern. but I have a much higher max latency all the time so i'm guessing i might have two things going on. 

It doesn't help that i work in Cloud on AWS all day and it runs like a dog as soon as I'm not on a VPN.

0 Kudos

Adduxi
Very Insightful Person
Very Insightful Person
In response to Noodlefox

on ‎27-04-2022 14:44

@Noodlefox wrote:

Thanks for the reply! it's a 6db it wouldn't do any harm to pull it since I can put it back later.
<snip>

Apart from the large numbers of T3 errors, your power levels are all okay.  The 6dba FPA if removed, will increase the power levels towards the upper limit of +10.  The range being -6 to +10.  The US power range is 34 to 51, so make sure they stay within these bounds if you remove it.

I would be asking VM to check why you are getting so many T3 errors, it could be a faulty cable or something amiss in the street cabinet.?

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

Noodlefox
Tuning in
In response to Adduxi

on ‎28-04-2022 13:58

So I tried without the 6dba FPA and the results are looking very similar. Also some of my levels are right on the money with the maximum safe DB ( i think?)

3.0 Downstream channels
Channel	Frequency (Hz)	Power (dBmV)	SNR (dB)	Modulation	Channel ID
5	171000000	7.900002	38.605377	QAM256	5
1	139000000	8.099998	38.983261	QAM256	1
2	147000000	7.900002	38.605377	QAM256	2
3	155000000	7.900002	38.605377	QAM256	3
4	163000000	8.000000	38.605377	QAM256	4
6	179000000	7.699997	38.983261	QAM256	6
7	187000000	7.800003	38.983261	QAM256	7
8	195000000	7.800003	38.983261	QAM256	8
9	203000000	7.699997	38.983261	QAM256	9
10	211000000	7.300003	38.983261	QAM256	10
11	219000000	7.199997	38.983261	QAM256	11
12	227000000	6.400002	38.983261	QAM256	12
13	235000000	6.000000	38.605377	QAM256	13
14	243000000	6.699997	38.605377	QAM256	14
15	251000000	7.199997	38.605377	QAM256	15
16	259000000	7.000000	38.983261	QAM256	16
17	267000000	7.500000	38.983261	QAM256	17
18	275000000	7.900002	38.605377	QAM256	18
19	283000000	7.900002	38.983261	QAM256	19
20	291000000	7.699997	38.983261	QAM256	20
21	299000000	8.500000	38.605377	QAM256	21
22	307000000	9.000000	38.605377	QAM256	22
23	315000000	9.900002	38.983261	QAM256	23
24	323000000	9.599998	38.983261	QAM256	24
25	331000000	9.000000	38.983261	QAM256	25
26	339000000	7.699997	38.983261	QAM256	26
27	347000000	7.500000	38.983261	QAM256	27
28	355000000	7.599998	38.983261	QAM256	28
29	363000000	7.400002	38.605377	QAM256	29
30	371000000	7.900002	38.983261	QAM256	30
31	379000000	7.199997	38.605377	QAM256	31


3.0 Downstream channels
Channel	Lock Status	RxMER (dB)	Pre RS Errors	Post RS Errors
5	Locked	38.605377	0	0
1	Locked	38.983261	0	0
2	Locked	38.605377	0	0
3	Locked	38.605377	0	0
4	Locked	38.605377	0	0
6	Locked	38.983261	0	0
7	Locked	38.983261	0	0
8	Locked	38.983261	0	0
9	Locked	38.983261	0	0
10	Locked	38.983261	0	0
11	Locked	38.983261	0	0
12	Locked	38.983261	0	0
13	Locked	38.605377	0	0
14	Locked	38.605377	0	0
15	Locked	38.605377	0	0
16	Locked	38.983261	0	0
17	Locked	38.983261	0	0
18	Locked	38.605377	0	0
19	Locked	38.983261	0	0
20	Locked	38.983261	0	0
21	Locked	38.605377	0	0
22	Locked	38.605377	0	0
23	Locked	38.983261	0	0
24	Locked	38.983261	0	0
25	Locked	38.983261	0	0
26	Locked	38.983261	0	0
27	Locked	38.983261	0	0
28	Locked	38.983261	0	0
29	Locked	38.605377	0	0
30	Locked	38.983261	0	0
31	Locked	38.605377	0	0


3.1 Downstream channels
Channel	Channel Width (MHz)	FFT Type 	Number of Active Subcarriers	Modulation (Active Profile)	First Active Subcarrier (Hz)
159	96	4K	1880	QAM4096	759


3.1 Downstream channels
Channel ID	Lock Status	RxMER Data (dB)	PLC Power (dBmV)	Correcteds (Active Profile)	Uncorrectables (Active Profile)
159	Locked	41	5.8	107530953	0
0 Kudos
Top