Menu
Reply
  • 70
  • 0
  • 7
flexipaul
On our wavelength
1,160 Views
Message 1 of 242
Flag for a moderator

packet loss

For over a week now i've been getting chronic packet loss on wired and wifi, not just related to gaming, twitch is also losing connection when watching live streams

I have vivid 350 and although speed is not constant at 350 its always been stable and i've rarely had a problem with gaming and never have I experienced such packet loss, this all started last Friday when i had to restart both the superhub 3 and my nighthawk r8000 after a sudden outage, this has slowly got worse over the last week to the point i'm having constant lag spike in games such as fortnite, i,ve put on debug mode in fortnite to watch the packet loss which has gone as high as 400% on the upstream, I then progressed and started investigating further, firstly by pinging google and amazon, ping is fine by the way very low, rarely above 20ms, but i noticed some timeouts when pinging them, i then progressed to tracing route and found lots of timeouts along the path, i have also pinged both my router and modem and found the router to be solid but when i pinged the modem i got a lot of timeouts again, I have tried connecting to the modem direct and also via wifi, can anyone with technical knowledge from virgin help as when i phoned i was told all departments closed until the 27th.

  • 403
  • 18
  • 80
tonycv51
Fibre optic
1,122 Views
Message 2 of 242
Flag for a moderator

Re: packet loss

Suggest post your power levels and also setup a BQM and see what shows. If you post the BQM back here remove your IP address

0 Kudos
Reply
  • 70
  • 0
  • 7
flexipaul
On our wavelength
1,104 Views
Message 3 of 242
Flag for a moderator

Re: packet loss

Downstream bonded channels

11710000004.137256 qam5
2179000000437256 qam6
3187000000437256 qam7
41950000003.937256 qam8
52030000003.537256 qam9
62110000003.237256 qam10
72190000003.437256 qam11
82270000003.437256 qam12
92350000003.237256 qam13
10243000000336256 qam14
112510000002.937256 qam15
122590000002.737256 qam16
132670000002.737256 qam17
142750000002.436256 qam18
152830000002.536256 qam19
162910000002.536256 qam20
173070000003.437256 qam22
183150000003.536256 qam23
193230000003.237256 qam24
203790000003.237256 qam25
21387000000337256 qam26
22395000000337256 qam27
234030000002.736256 qam28
242990000003.236256 qam21
0 Kudos
Reply
  • 70
  • 0
  • 7
flexipaul
On our wavelength
1,103 Views
Message 4 of 242
Flag for a moderator

Re: packet loss

Upstream bonded channels

13940000042512016 qam4
26030000042512016 qam1
34620000042.3512016 qam3
45370000042.5512016 qam2



Upstream bonded channels

1ATDMA0020
2ATDMA0000
3ATDMA0000
4ATDMA0020
0 Kudos
Reply
  • 70
  • 0
  • 7
flexipaul
On our wavelength
1,099 Views
Message 5 of 242
Flag for a moderator

Re: packet loss

Microsoft Windows [Version 10.0.17134.472]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\paulc_000>tracert google.co.uk

Tracing route to google.co.uk [216.58.210.35]
over a maximum of 30 hops:

1 2 ms 9 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 * 20 ms 12 ms hari-core-2a-xe-013-0.network.virginmedia.net [80.0.0.41]
4 * * * Request timed out.
5 18 ms 17 ms 13 ms tele-ic-7-ae2-0.network.virginmedia.net [62.253.175.34]
6 15 ms 16 ms 15 ms 74-14-250-212.static.virginm.net [212.250.14.74]
7 22 ms 24 ms 22 ms 108.170.246.129
8 24 ms 24 ms 22 ms 108.170.232.103
9 22 ms 23 ms 20 ms 108.170.232.105
10 19 ms 30 ms 16 ms lhr25s11-in-f35.1e100.net [216.58.210.35]

Trace complete.

C:\Users\paulc_000>

C:\Users\paulc_000>

0 Kudos
Reply
  • 70
  • 0
  • 7
flexipaul
On our wavelength
1,097 Views
Message 6 of 242
Flag for a moderator

Re: packet loss

Microsoft Windows [Version 10.0.17134.472]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\paulc_000>tracert virginmedia.com

Tracing route to virginmedia.com [213.105.9.24]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 14 ms 11 ms 15 ms hari-core-2b-xe-322-0.network.virginmedia.net [62.252.114.117]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 23 ms 23 ms 29 ms know-dclcore-1b-port-channel1.network.virginmedia.net [62.254.85.22]
8 24 ms 21 ms 21 ms www.virginmedia.com [213.105.9.24]

Trace complete.

C:\Users\paulc_000>

0 Kudos
Reply
  • 70
  • 0
  • 7
flexipaul
On our wavelength
1,095 Views
Message 7 of 242
Flag for a moderator

Re: packet loss

Microsoft Windows [Version 10.0.17134.472]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\paulc_000>tracert bbc.co.uk

Tracing route to bbc.co.uk [151.101.0.81]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 12 ms 10 ms hari-core-2b-xe-322-0.network.virginmedia.net [62.252.114.117]
4 * * * Request timed out.
5 * * * Request timed out.
6 19 ms 13 ms 14 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 * 14 ms 18 ms 213.46.174.118
8 45 ms 25 ms 24 ms fastly-ic-306174-ldn-b3.c.telia.net [62.115.42.194]
9 26 ms 22 ms 25 ms 151.101.0.81

Trace complete.

C:\Users\paulc_000>

0 Kudos
Reply
  • 70
  • 0
  • 7
flexipaul
On our wavelength
1,093 Views
Message 8 of 242
Flag for a moderator

Re: packet loss

Microsoft Windows [Version 10.0.17134.472]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\paulc_000>ping google.com -n 30
Ping request could not find host google.com. Please check the name and try again.

C:\Users\paulc_000>ping www.google.co.uk -n 30

Pinging www.google.co.uk [172.217.23.3] with 32 bytes of data:
Reply from 172.217.23.3: bytes=32 time=32ms TTL=52
Reply from 172.217.23.3: bytes=32 time=28ms TTL=52
Reply from 172.217.23.3: bytes=32 time=18ms TTL=52
Reply from 172.217.23.3: bytes=32 time=17ms TTL=52
Request timed out.
Request timed out.
Reply from 172.217.23.3: bytes=32 time=21ms TTL=52
Reply from 172.217.23.3: bytes=32 time=19ms TTL=52
Reply from 172.217.23.3: bytes=32 time=19ms TTL=52
Request timed out.
Reply from 172.217.23.3: bytes=32 time=35ms TTL=52
Reply from 172.217.23.3: bytes=32 time=26ms TTL=52
Reply from 172.217.23.3: bytes=32 time=15ms TTL=52
Request timed out.
Request timed out.
Reply from 172.217.23.3: bytes=32 time=18ms TTL=52
Reply from 172.217.23.3: bytes=32 time=21ms TTL=52
Reply from 172.217.23.3: bytes=32 time=17ms TTL=52
Reply from 172.217.23.3: bytes=32 time=17ms TTL=52
Reply from 172.217.23.3: bytes=32 time=16ms TTL=52
Reply from 172.217.23.3: bytes=32 time=17ms TTL=52
Reply from 172.217.23.3: bytes=32 time=16ms TTL=52
Reply from 172.217.23.3: bytes=32 time=19ms TTL=52
Reply from 172.217.23.3: bytes=32 time=16ms TTL=52
Request timed out.
Reply from 172.217.23.3: bytes=32 time=28ms TTL=52
Reply from 172.217.23.3: bytes=32 time=25ms TTL=52
Reply from 172.217.23.3: bytes=32 time=16ms TTL=52
Reply from 172.217.23.3: bytes=32 time=20ms TTL=52
Request timed out.

Ping statistics for 172.217.23.3:
Packets: Sent = 30, Received = 23, Lost = 7 (23% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 35ms, Average = 20ms

C:\Users\paulc_000>

0 Kudos
Reply
  • 403
  • 18
  • 80
tonycv51
Fibre optic
1,094 Views
Message 9 of 242
Flag for a moderator

Re: packet loss

Power levels look OK to me  If you can setup a BQM that might help

0 Kudos
Reply
  • 70
  • 0
  • 7
flexipaul
On our wavelength
1,093 Views
Message 10 of 242
Flag for a moderator

Re: packet loss

Massive ping time to the Virgin modem, could the superhub 3 be the problem?

Microsoft Windows [Version 10.0.17134.472]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\paulc_000>ping 192.168.100.1 -n 30

Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time=139ms TTL=63
Reply from 192.168.100.1: bytes=32 time=347ms TTL=63
Reply from 192.168.100.1: bytes=32 time=156ms TTL=63
Reply from 192.168.100.1: bytes=32 time=375ms TTL=63
Reply from 192.168.100.1: bytes=32 time=178ms TTL=63
Reply from 192.168.100.1: bytes=32 time=386ms TTL=63
Reply from 192.168.100.1: bytes=32 time=201ms TTL=63
Reply from 192.168.100.1: bytes=32 time=414ms TTL=63
Reply from 192.168.100.1: bytes=32 time=205ms TTL=63
Reply from 192.168.100.1: bytes=32 time=431ms TTL=63
Reply from 192.168.100.1: bytes=32 time=218ms TTL=63
Reply from 192.168.100.1: bytes=32 time=417ms TTL=63
Reply from 192.168.100.1: bytes=32 time=222ms TTL=63
Reply from 192.168.100.1: bytes=32 time=19ms TTL=63
Reply from 192.168.100.1: bytes=32 time=231ms TTL=63
Reply from 192.168.100.1: bytes=32 time=49ms TTL=63
Reply from 192.168.100.1: bytes=32 time=149ms TTL=63
Reply from 192.168.100.1: bytes=32 time=347ms TTL=63
Reply from 192.168.100.1: bytes=32 time=155ms TTL=63
Reply from 192.168.100.1: bytes=32 time=413ms TTL=63
Reply from 192.168.100.1: bytes=32 time=178ms TTL=63
Reply from 192.168.100.1: bytes=32 time=375ms TTL=63
Reply from 192.168.100.1: bytes=32 time=181ms TTL=63
Reply from 192.168.100.1: bytes=32 time=391ms TTL=63
Reply from 192.168.100.1: bytes=32 time=184ms TTL=63
Reply from 192.168.100.1: bytes=32 time=400ms TTL=63
Reply from 192.168.100.1: bytes=32 time=209ms TTL=63
Reply from 192.168.100.1: bytes=32 time=408ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=428ms TTL=63

Ping statistics for 192.168.100.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 431ms, Average = 260ms

C:\Users\paulc_000>

sive ping time to the Virgin modem

 

 

0 Kudos
Reply