Menu
Reply
nhawan
  • 21
  • 0
  • 0
Joining in
591 Views
Message 1 of 9
Flag for a moderator

Severe packet loss and lag BD8

Hi,

I'm getting severe lag in online games and Youtube keeps buffering more frequently and web pages feel slow and pause intermittently. League of Legends shows a ping of 30ms constant but I get severe lag and even disconnection notices while playing.

This has been happening since yesterday but service status shows no issues. I checked the modem info and there appear to be lots of Post RS errors on the Downstream.

Downstream bonded channels
Channel	Frequency (Hz)	Power (dBmV)	SNR (dB)	Modulation	Channel ID
1	299000000	5.5	38	256 qam	21
2	139000000	5.3	38	256 qam	1
3	147000000	5.1	37	256 qam	2
4	155000000	5.1	37	256 qam	3
5	163000000	4.8	38	256 qam	4
6	171000000	5	38	256 qam	5
7	179000000	4.5	38	256 qam	6
8	187000000	4.5	37	256 qam	7
9	195000000	4	38	256 qam	8
10	203000000	3.7	38	256 qam	9
11	211000000	3.7	37	256 qam	10
12	219000000	3.5	38	256 qam	11
13	227000000	3.7	38	256 qam	12
14	235000000	3.7	38	256 qam	13
15	243000000	4	38	256 qam	14
16	251000000	4	38	256 qam	15
17	259000000	4.5	38	256 qam	16
18	267000000	5	38	256 qam	17
19	275000000	5.5	38	256 qam	18
20	283000000	5.4	38	256 qam	19
21	291000000	5.4	38	256 qam	20
22	307000000	5.3	38	256 qam	22
23	315000000	5	38	256 qam	23
24	323000000	4.8	38	256 qam	24


Downstream bonded channels
Channel	Locked Status	RxMER (dB)	Pre RS Errors	Post RS Errors
1	Locked		38.6	5304	9093
2	Locked		38.6	18103	13392
3	Locked		37.6	26588	12206
4	Locked		37.6	17001	23098
5	Locked		38.9	14179	13535
6	Locked		38.6	26102	50845
7	Locked		38.6	65730	18172
8	Locked		37.6	788775	19711
9	Locked		38.6	441179	16117
10	Locked		38.6	30463	15707
11	Locked		37.6	22560	14894
12	Locked		38.6	14772	13432
13	Locked		38.6	11390	13450
14	Locked		38.6	10324	13812
15	Locked		38.9	8342	12746
16	Locked		38.6	7310	11607
17	Locked		38.6	6861	11798
18	Locked		38.9	5857	10817
19	Locked		38.9	5178	11917
20	Locked		38.9	5282	10959
21	Locked		38.6	5900	10368
22	Locked		38.9	5825	8928
23	Locked		38.9	6465	9538
24	Locked		38.6	5433	8420
Upstream bonded channels
Channel	Frequency (Hz)	Power (dBmV)	Symbol Rate (ksps)	Modulation	Channel ID
1	25800000	4.75	5120	64 qam	8
2	32600000	4.75	5120	64 qam	7
3	39400000	4.75	5120	64 qam	6
4	46200000	4.75	5120	64 qam	5


Upstream bonded channels
Channel	Channel Type	T1 Timeouts	T2 Timeouts	T3 Timeouts	T4 Timeouts
1	ATDMA	0	0	0	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0

 

Please help.

0 Kudos
Reply
Anonymous
Not applicable
581 Views
Message 2 of 9
Flag for a moderator

Re: Severe packet loss and lag BD8

When was the last time the router/HUB was rebooted?

Just trying to understand if these 'Post RS Errors' have occured over a short period of time.

0 Kudos
Reply
nhawan
  • 21
  • 0
  • 0
Joining in
569 Views
Message 3 of 9
Flag for a moderator

Re: Severe packet loss and lag BD8

Rebooted router earlier today and another time just 20 mins ago. Lag is still present.

0 Kudos
Reply
Anonymous
Not applicable
566 Views
Message 4 of 9
Flag for a moderator

Re: Severe packet loss and lag BD8


@nhawan wrote:

Rebooted router earlier today and another time just 20 mins ago. Lag is still present.


Are the 'Post RS Errors' still building up?

0 Kudos
Reply
nhawan
  • 21
  • 0
  • 0
Joining in
563 Views
Message 5 of 9
Flag for a moderator

Re: Severe packet loss and lag BD8

The RS errors are still the same so perhaps these were from some previous time. The websites are loading very slowly now.

0 Kudos
Reply
Anonymous
Not applicable
562 Views
Message 6 of 9
Flag for a moderator

Re: Severe packet loss and lag BD8


@nhawan wrote:

The RS errors are still the same so perhaps these were from some previous time. The websites are loading very slowly now.


When you reboot the hub the stats reset, other than network log, so that's a bit odd?

0 Kudos
Reply
nhawan
  • 21
  • 0
  • 0
Joining in
533 Views
Message 7 of 9
Flag for a moderator

Re: Severe packet loss and lag BD8

I rang VM and they told me to factory reset the router by holding the reset button in for 40 secs. The problem still exists after this reset but no Post RS errors are showing even though there are some pre RS errors.

 

I did a ping test on Google.com and this is what I get:

 

C:\WINDOWS\system32>ping www.google.com -t

Pinging www.google.com [216.58.206.100] with 32 bytes of data:
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Reply from 216.58.206.100: bytes=32 time=19ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Reply from 216.58.206.100: bytes=32 time=13ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=16ms TTL=115
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=16ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Reply from 216.58.206.100: bytes=32 time=22ms TTL=115
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.206.100: bytes=32 time=18ms TTL=115
Reply from 216.58.206.100: bytes=32 time=18ms TTL=115
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.206.100: bytes=32 time=26ms TTL=115
Reply from 216.58.206.100: bytes=32 time=16ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=18ms TTL=115
Reply from 216.58.206.100: bytes=32 time=22ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=18ms TTL=115
Reply from 216.58.206.100: bytes=32 time=24ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Reply from 216.58.206.100: bytes=32 time=13ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=19ms TTL=115
Reply from 216.58.206.100: bytes=32 time=22ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=18ms TTL=115
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=23ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Reply from 216.58.206.100: bytes=32 time=18ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=18ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=16ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=16ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Reply from 216.58.206.100: bytes=32 time=13ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Reply from 216.58.206.100: bytes=32 time=20ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=13ms TTL=115
Reply from 216.58.206.100: bytes=32 time=13ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=29ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=16ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Request timed out.
Reply from 216.58.206.100: bytes=32 time=17ms TTL=115
Reply from 216.58.206.100: bytes=32 time=16ms TTL=115
Reply from 216.58.206.100: bytes=32 time=13ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=13ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Reply from 216.58.206.100: bytes=32 time=13ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Reply from 216.58.206.100: bytes=32 time=13ms TTL=115
Reply from 216.58.206.100: bytes=32 time=14ms TTL=115
Reply from 216.58.206.100: bytes=32 time=15ms TTL=115
Reply from 216.58.206.100: bytes=32 time=19ms TTL=115

Ping statistics for 216.58.206.100:
    Packets: Sent = 101, Received = 77, Lost = 24 (23% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 29ms, Average = 16ms

 

A traceroute shows this :

C:\WINDOWS\system32>tracert www.google.com

Tracing route to www.google.com [216.58.206.100]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2    13 ms    10 ms     7 ms  10.76.48.1
  3    11 ms    10 ms     7 ms  brad-core-2a-xe-10117-0.network.virginmedia.net [81.97.81.49]
  4     *        *        *     Request timed out.
  5    17 ms    17 ms    24 ms  tcl5-ic-4-ae5-0.network.virginmedia.net [62.252.192.246]
  6    15 ms    14 ms    15 ms  cpc69435-hink4-2-0-cust116.8-2.cable.virginm.net [62.252.5.117]
  7    16 ms    14 ms    22 ms  216.239.41.16
  8    18 ms    15 ms    16 ms  216.239.58.221
  9    18 ms    17 ms    13 ms  lhr25s14-in-f4.1e100.net [216.58.206.100]

Trace complete.

 

The traceroute showing a time out on hop 4 seems to be something on the VM network. There is definite packet loss but VM can't detect a problem from their side. 

0 Kudos
Reply
nhawan
  • 21
  • 0
  • 0
Joining in
516 Views
Message 8 of 9
Flag for a moderator

Re: Severe packet loss and lag BD8

Update: After some investigation I found that the fault was caused by a media player connected to the router. For some reason the media player was probably sending too much data or pings to the router thus overloading it. The problem went away when I rebooted the media player. Now there is no packet loss after a 10 minute ping test.

Problem is fixed.

0 Kudos
Reply
Lee_R
  • 2.56K
  • 136
  • 238
Forum Team
Forum Team
459 Views
Message 9 of 9
Flag for a moderator

Re: Severe packet loss and lag BD8

That's great.  I'm happy you've found a resolution nhawan.

Call on our assistance any time you need us though.

Regards

 

Lee_R

0 Kudos
Reply