Menu
Reply
Highlighted
  • 6
  • 0
  • 0
Tuning in
373 Views
Message 1 of 8
Flag for a moderator

Packet loss issue

Hi,

been having packet loss issue for the last 3 or 4 days and noticed lower than normal upload speed as low as 2 mb. packet loss is small but definitely affecting gaming. I have 350 fibre broadband and V M super hub 3 if anyone could help? 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/c2bb86e85f43e1487bc92f78afe47be4876ba413

  

0 Kudos
Reply
Highlighted
  • 2.39K
  • 378
  • 927
Problem sorter
324 Views
Message 2 of 8
Flag for a moderator

Re: Packet loss issue

Any packet loss at all kills gaming and streaming, and there shouldn't be any, but it looks as though that BQM cleared up at midnight - is the connection still causing problems?

If it is, usual drill, connect to the hub, don't log in, click on "check router status", then post here as text the contents of the three tabs Downstream, Upstream, Network log.  Do a few speed tests on a device connected to the hub by a network cable, see what they show.  

Highlighted
  • 6
  • 0
  • 0
Tuning in
285 Views
Message 3 of 8
Flag for a moderator

Re: Packet loss issue

Hi, Thanks for reply.

Yes still getting a little packet loss not as much as before but it is still there.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/c2bb86e85f43e1487bc92f78afe47be4876ba413

Downstream bonded channels

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

12990000000.237256 qam21
2235000000138256 qam13
32430000000.738256 qam14
42510000000.538256 qam15
52590000000.238256 qam16
62670000000.438256 qam17
72750000000.438256 qam18
82830000000.238256 qam19
9291000000037256 qam20
10307000000038256 qam22
11315000000037256 qam23
123230000000.237256 qam24
133470000000.438256 qam25
143550000000.438256 qam26
153630000000.438256 qam27
163710000000.538256 qam28
173790000000.538256 qam29
183870000000.538256 qam30
193950000000.538256 qam31
204030000000.738256 qam32
214110000000.738256 qam33
224190000000.538256 qam34
234270000000.538256 qam35
24435000000038256 qam36


Downstream bonded channels

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

1Locked37.3650
2Locked38.6350
3Locked38.6240
4Locked38.6310
5Locked38.6270
6Locked38.6300
7Locked38.6290
8Locked38.6350
9Locked37.6280
10Locked38.6300
11Locked37.6200
12Locked37.6290
13Locked38.9340
14Locked38.6330
15Locked38.9240
16Locked38.6280
17Locked38.9400
18Locked38.6310
19Locked38.6280
20Locked38.6540
21Locked38.6650
22Locked38.6330
23Locked38.9300
24Locked38.6280

 

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

1537000294.45512064 qam2
2462001034.425512064 qam3
3394000594.4512064 qam7
4603000504.475512064 qam1


Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000



0 Kudos
Reply
Highlighted
  • 6
  • 0
  • 0
Tuning in
295 Views
Message 4 of 8
Flag for a moderator

Re: Packet loss issue

Hi thanks for reply.

Yes still having packet loss issue but not as much as before but still there.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/c2bb86e85f43e1487bc92f78afe47be4876ba413

 

Downstream bonded channels

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

12990000000.237256 qam21
2235000000138256 qam13
32430000000.738256 qam14
42510000000.538256 qam15
52590000000.238256 qam16
62670000000.438256 qam17
72750000000.438256 qam18
82830000000.238256 qam19
9291000000037256 qam20
10307000000038256 qam22
11315000000037256 qam23
123230000000.237256 qam24
133470000000.438256 qam25
143550000000.438256 qam26
153630000000.438256 qam27
163710000000.538256 qam28
173790000000.538256 qam29
183870000000.538256 qam30
193950000000.538256 qam31
204030000000.738256 qam32
214110000000.738256 qam33
224190000000.538256 qam34
234270000000.538256 qam35
24435000000038256 qam36



Downstream bonded channels

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

1Locked37.3650
2Locked38.6350
3Locked38.6240
4Locked38.6310
5Locked38.6270
6Locked38.6300
7Locked38.6290
8Locked38.6350
9Locked37.6280
10Locked38.6300
11Locked37.6200
12Locked37.6290
13Locked38.9340
14Locked38.6330
15Locked38.9240
16Locked38.6280
17Locked38.9400
18Locked38.6310
19Locked38.6280
20Locked38.6540
21Locked38.6650
22Locked38.6330
23Locked38.9300
24Locked38.6280
0 Kudos
Reply
Highlighted
  • 6
  • 0
  • 0
Tuning in
294 Views
Message 5 of 8
Flag for a moderator

Re: Packet loss issue

Upstream bonded channels

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

1537000294.45512064 qam2
2462001034.425512064 qam3
3394000594.4512064 qam7
4603000504.475512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
Highlighted
  • 6
  • 0
  • 0
Tuning in
293 Views
Message 6 of 8
Flag for a moderator

Re: Packet loss issue

Network Log

Time Priority Description

19/02/2020 21:33:5criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/02/2020 14:20:29noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:31criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/02/2020 13:57:5noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/02/2020 09:24:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/02/2020 21:39:3Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/02/2020 02:25:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2020 14:38:44ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2020 06:35:27ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2020 04:11:9criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/02/2020 22:32:13ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/02/2020 01:20:7noticeSW download Successful - Via NMS
04/02/2020 01:16:54noticeSW Download INIT - Via NMS
02/02/2020 14:35:40ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2020 00:36:7ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/02/2020 21:12:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/02/2020 10:36:37ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2020 06:18:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2020 04:00:18ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Highlighted
  • 2.39K
  • 378
  • 927
Problem sorter
267 Views
Message 7 of 8
Flag for a moderator

Re: Packet loss issue

From all sets of stats I can't spot anything obviously wrong - all looks within spec, and whilst the network log isn't completely clean, it too is still not providing much evidence.  However, the BQM shows ongoing low level packet loss, and whilst there's always the chance of the odd packet being lost on the complex technology involved, it shouldn't be grumbling along persistently* like your BQM shows.

All I can suggest is waiting for the forum staff to advise. 

Sometimes these things appear to go away of their own accord after a day or two, sometimes field technicians can visit, pinpoint and fix this sort of thing, occasionally they (and VM) seem to be unable or unwilling to fix it.  If it falls into the last category, then you may be looking at finding a new ISP, but before worrying about that, wait and see what the forum staff have to say.

 

* I'd like to point out that "grumbling along persistently" is a highly technical term, widely understood by networking experts. Probably.

Highlighted
  • 6
  • 0
  • 0
Tuning in
261 Views
Message 8 of 8
Flag for a moderator

Re: Packet loss issue

Thanks for your help Andruser appreciate it.

yes the packet loss is only showing on game as 1% to 3% today compared to last couple days was 5% and high as 10%.

Been with VM for 8 years now and first i have had this problem, connection has always been great.

 

 

0 Kudos
Reply