Is this typical Virgin Media jitter ?

[webBeAsTspider]

Hi,

As a previous BT user I did spend quite some time looking at their network, their jitter was low +/- 1ms, now via Virgin Media I'm seeing some not very good jitter, typically +10ms or more, is this typical with perhaps a over loaded network ? I'm using a wired network, there's nothing happening on my network, 1 user - myself and wireshark shows nothing happening apart from ping.

ping to first hop

Reply from 86.28.83.173: bytes=32 time=10ms TTL=62
Reply from 86.28.83.173: bytes=32 time=8ms TTL=62
Reply from 86.28.83.173: bytes=32 time=17ms TTL=62 <<<<<<<<
Reply from 86.28.83.173: bytes=32 time=8ms TTL=62
Reply from 86.28.83.173: bytes=32 time=8ms TTL=62
Reply from 86.28.83.173: bytes=32 time=8ms TTL=62
Reply from 86.28.83.173: bytes=32 time=8ms TTL=62
Reply from 86.28.83.173: bytes=32 time=7ms TTL=62
Reply from 86.28.83.173: bytes=32 time=9ms TTL=62

ping to bbc.co.uk

Reply from 151.101.128.81: bytes=32 time=12ms TTL=58
Reply from 151.101.128.81: bytes=32 time=14ms TTL=58
Reply from 151.101.128.81: bytes=32 time=12ms TTL=58
Reply from 151.101.128.81: bytes=32 time=16ms TTL=58
Reply from 151.101.128.81: bytes=32 time=13ms TTL=58
Reply from 151.101.128.81: bytes=32 time=20ms TTL=58 <<<<<<<<<<<<<<
Reply from 151.101.128.81: bytes=32 time=14ms TTL=58
Reply from 151.101.128.81: bytes=32 time=13ms TTL=58
Reply from 151.101.128.81: bytes=32 time=13ms TTL=58

tracert to bbc.co.uk

1 1 ms 1 ms 2 ms 192.168.0.1
2 11 ms 16 ms 8 ms 10.53.37.117
3 9 ms 12 ms 9 ms nott-core-2b-xe-305-0.network.virginmedia.net [86.28.83.173]
4 * * * Request timed out.
5 16 ms 16 ms 13 ms tcl5-ic-5-ae0-0.network.virginmedia.net [62.254.84.66]
6 14 ms 13 ms 14 ms 157.52.127.10
7 13 ms 13 ms 12 ms 151.101.192.81

[Tom_W1]

Hi @webBeAsTspider thanks for your thanks via PM - I'm just bringing this back publicly to close off this thread.

I'm glad that we can look to get this sorted for you, please let us know if you have any other problems once we've aimed to get this resolved.

Many thanks

[webBeAsTspider]

Here's my BQM result, I have rebooted the hub a few times where there's a red line / packet loss, seems peak time does push up latency, I'll report back to see if there's any improvement after my power levels are sorted. Obviously pings into 100's of ms aren't a good result.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/9226f432ebfbf29e306b03d0a4252ab8d6...

[Gareth_L]

HI webBeAsTspider

How are things looking now 

Any improvement at all 

Gareth_L

[webBeAsTspider]

I'm still seeing a fair bit of jitter with occasional larger ping increases for no apparent reason, it may be ever so marginally better. I think the engineer tried more or less everything so I'm not sure what else if anything can be done.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/2ce8b4e43f0d35a25a6ab818f621007232...

As below after the visit I'm still seeing a swing from 10ms up to 21ms, I wonder if having a land line attached might have something to do with it, perhaps clutching at straws ? I may try modem mode tomorrow to see if that changes anything but I suspect this jitter is coming from something beyond the wall socket. There's plenty of speed, 940 ish Mb/s and 50Mb/s up

Reply from 151.101.64.81: bytes=32 time=16ms TTL=58
Reply from 151.101.64.81: bytes=32 time=10ms TTL=58 <<<<<<<<<<<
Reply from 151.101.64.81: bytes=32 time=12ms TTL=58
Reply from 151.101.64.81: bytes=32 time=21ms TTL=58 <<<<<<<<<<<
Reply from 151.101.64.81: bytes=32 time=11ms TTL=58
Reply from 151.101.64.81: bytes=32 time=12ms TTL=58

power levels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
26 339000000 5.599998 40.366287 QAM256 26
1 139000000 -1.299999 37.355988 QAM256 1
2 147000000 -0.799999 37.355988 QAM256 2
3 155000000 -0.299999 37.355988 QAM256 3
4 163000000 0.099998 37.636276 QAM256 4
5 171000000 0.500000 37.636276 QAM256 5
6 179000000 0.799999 38.605377 QAM256 6
7 187000000 1.200001 38.983261 QAM256 7
8 195000000 1.400002 38.605377 QAM256 8
9 203000000 1.700001 38.605377 QAM256 9
10 211000000 1.799999 38.605377 QAM256 10
11 219000000 2.000000 38.605377 QAM256 11
12 227000000 2.099998 38.983261 QAM256 12
13 235000000 2.200001 38.605377 QAM256 13
14 243000000 2.099998 38.605377 QAM256 14
15 251000000 2.200001 38.983261 QAM256 15
16 259000000 2.000000 38.983261 QAM256 16
17 267000000 2.099998 38.983261 QAM256 17
18 275000000 2.700001 38.983261 QAM256 18
19 283000000 3.400002 38.983261 QAM256 19
20 291000000 3.900002 38.605377 QAM256 20
21 299000000 4.099998 38.605377 QAM256 21
22 307000000 4.199997 38.983261 QAM256 22
23 315000000 4.400002 38.983261 QAM256 23
24 323000000 5.000000 38.983261 QAM256 24
25 331000000 5.099998 38.983261 QAM256 25
27 347000000 5.500000 40.946209 QAM256 27
28 355000000 5.900002 40.366287 QAM256 28
29 363000000 5.800003 38.983261 QAM256 29
30 371000000 5.800003 40.366287 QAM256 30
31 379000000 5.900002 40.366287 QAM256 31

3.0 Downstream channels
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
26 Locked 40.366287 0 0
1 Locked 37.355988 1 0
2 Locked 37.355988 0 0
3 Locked 37.355988 0 0
4 Locked 37.636276 0 0
5 Locked 37.636276 0 0
6 Locked 38.605377 0 0
7 Locked 38.983261 0 0
8 Locked 38.605377 0 0
9 Locked 38.605377 0 0
10 Locked 38.605377 0 0
11 Locked 38.605377 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.983261 0 0
18 Locked 38.983261 0 0
19 Locked 38.983261 0 0
20 Locked 38.605377 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
27 Locked 40.946209 0 0
28 Locked 40.366287 0 0
29 Locked 38.983261 0 0
30 Locked 40.366287 0 0
31 Locked 40.366287 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 6.8 152809068 50

----------------

upstream

3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 60300000 41.770599 5120 KSym/sec 64QAM 1
2 39400000 39.770599 5120 KSym/sec 64QAM 4
3 46200000 40.270599 5120 KSym/sec 64QAM 3
4 53700000 41.270599 5120 KSym/sec 64QAM 2

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

[legacy1]

---

@webBeAsTspider wrote:

I'm still seeing a fair bit of jitter with occasional larger ping increases for no apparent reason, it may be ever so marginally better. I think the engineer tried more or less everything so I'm not sure what else if anything can be done.

---

Everyone with a BQM on Docsis with good latency has jitter some spikes can be caused by a burst in speed to your upto limit due to not QoS/BWM on the hub or a network load by others in your area.      

[webBeAsTspider]

The jitter I see isn't from my local network, I've tried the hub4 in modem mode and I'm seeing the exact same jitter, I have to assume this is "a network load by others in your area.". It would be interesting if someone else could verify this by doing 'ping bbc.co.uk -t' and see what sort of jitter they have.

So at the moment it seems this jitter can't be fixed and is unavoidable i.e.it's just what you get with Virgin broadband.

[legacy1]

---

@webBeAsTspider wrote:

So at the moment it seems this jitter can't be fixed and is unavoidable i.e.it's just what you get with Virgin broadband.

---

yes

My BQM like others has jitter some worse some better 

L