on 07-09-2021 00:04
hi,I have gig fiber broadband and I’m having problems in all online games with lag/ping causing spikes and delay.(quite severe at times almost unplayable) I have everything optimized on my pc with all the latest hardware and drivers it’s nothing to do with my system it’s all been tested throughly. I’ve been on live chat with virgin for nearly a year trying to solve it but they keep dismissing that there is a problem an they keep saying there’s nothing wrong on our side and follow the stupid reseting router method (which never fixes anything). I’ve also tested the network on modem mode with my own asus gaming router and I’ve adjusted the setting and tested it to achieve zero bufferbloat ( which I tested and achieved A+ rating) but still the same problem when online gaming. I have no problem with the speed it usually achieves around 800 Down an about 47 up on average which isn’t bad but it doesn’t matter what my speeds are it seems to something deeper causing the issues.
on 07-09-2021 05:31
The speed has nothing to do with latency or ping. Gaming needs less than 5 Mbps download, but needs low latency. Having a better router won't improve latency in the usual circumstance where the problem is the connection to VM, because the cable technology is prone to poor latency. A couple of diagnostic things you can try below:
1) Let's see how latency and packet loss are on your connection: Setup a BQM over at https://www.thinkbroadband.com/broadband/monitoring/quality that'll show what's going on with your VM connection. Post a LINK to a LIVE, SHARED graph here and we'll see what's happening. Usually needs to run for 24 hours before we can draw reasonable conclusions, but the live graph will continuously update so you can post the link immediately.
2) Connect to the hub by clicking on this link http://192.168.100.1/ That should pull up the log in page for the hub. But don't log in, just click on the link "Check router status" That'll bring up a window with five tabs. Open the Downstream tab. Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots. Post that, do the same for the Upstream and Network log. You'll get an error message when you post the Network log, just click on "post" a second time. Then we can check for any obvious problems with power, noise or error counts.
on 07-09-2021 16:21
on 07-09-2021 16:24
3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 331000000 | 4.199997 | 38.605377 | QAM256 | 25 |
6 | 179000000 | 5.599998 | 38.983261 | QAM256 | 6 |
7 | 187000000 | 5.599998 | 38.983261 | QAM256 | 7 |
8 | 195000000 | 5.599998 | 38.983261 | QAM256 | 8 |
9 | 203000000 | 5.599998 | 38.605377 | QAM256 | 9 |
10 | 211000000 | 5.400002 | 38.605377 | QAM256 | 10 |
11 | 219000000 | 5.400002 | 38.983261 | QAM256 | 11 |
12 | 227000000 | 5.400002 | 38.983261 | QAM256 | 12 |
13 | 235000000 | 5.199997 | 38.983261 | QAM256 | 13 |
14 | 243000000 | 5.199997 | 38.983261 | QAM256 | 14 |
15 | 251000000 | 5.199997 | 38.983261 | QAM256 | 15 |
16 | 259000000 | 5.099998 | 38.983261 | QAM256 | 16 |
17 | 267000000 | 4.800003 | 38.983261 | QAM256 | 17 |
18 | 275000000 | 4.099998 | 38.983261 | QAM256 | 18 |
19 | 283000000 | 4.800003 | 38.983261 | QAM256 | 19 |
20 | 291000000 | 4.599998 | 38.983261 | QAM256 | 20 |
21 | 299000000 | 4.599998 | 38.605377 | QAM256 | 21 |
22 | 307000000 | 4.599998 | 38.983261 | QAM256 | 22 |
23 | 315000000 | 3.599998 | 38.983261 | QAM256 | 23 |
24 | 323000000 | 3.700001 | 38.605377 | QAM256 | 24 |
26 | 339000000 | 4.000000 | 38.605377 | QAM256 | 26 |
27 | 347000000 | 4.500000 | 38.983261 | QAM256 | 27 |
28 | 355000000 | 4.199997 | 38.983261 | QAM256 | 28 |
29 | 363000000 | 3.900002 | 38.983261 | QAM256 | 29 |
30 | 371000000 | 4.400002 | 38.983261 | QAM256 | 30 |
31 | 379000000 | 3.799999 | 38.983261 | QAM256 | 31 |
32 | 387000000 | 4.000000 | 38.983261 | QAM256 | 32 |
34 | 395000000 | 4.000000 | 38.983261 | QAM256 | 34 |
35 | 403000000 | 3.299999 | 38.983261 | QAM256 | 35 |
36 | 411000000 | 3.799999 | 38.983261 | QAM256 | 36 |
37 | 419000000 | 3.599998 | 38.605377 | QAM256 | 37 |
3.0 Downstream channels
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | 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.605377 | 0 | 0 |
10 | Locked | 38.605377 | 0 | 0 |
11 | Locked | 38.983261 | 0 | 0 |
12 | Locked | 38.983261 | 0 | 0 |
13 | Locked | 38.983261 | 0 | 0 |
14 | Locked | 38.983261 | 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.983261 | 0 | 0 |
21 | Locked | 38.605377 | 0 | 0 |
22 | Locked | 38.983261 | 0 | 0 |
23 | Locked | 38.983261 | 0 | 0 |
24 | Locked | 38.605377 | 0 | 0 |
26 | Locked | 38.605377 | 0 | 0 |
27 | Locked | 38.983261 | 0 | 0 |
28 | Locked | 38.983261 | 0 | 0 |
29 | Locked | 38.983261 | 0 | 0 |
30 | Locked | 38.983261 | 0 | 0 |
31 | Locked | 38.983261 | 0 | 0 |
32 | Locked | 38.983261 | 0 | 0 |
34 | Locked | 38.983261 | 0 | 0 |
35 | Locked | 38.983261 | 0 | 0 |
36 | Locked | 38.983261 | 0 | 0 |
37 | Locked | 38.605377 | 0 | 0 |
33 | 96 | 4K | 1880 | QAM4096 | 424 |
33 | Locked | 42 | 3.2 | 239384916 | 2 |
on 07-09-2021 16:25
3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 47.770599 | 5120 KSym/sec | 64QAM | 8 |
2 | 39400000 | 47.770599 | 5120 KSym/sec | 64QAM | 9 |
3 | 53700000 | 48.020599 | 5120 KSym/sec | 64QAM | 7 |
4 | 60300000 | 48.270599 | 5120 KSym/sec | 64QAM | 6 |
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 |
on 07-09-2021 16:26
Network Log
Time Priority Description
Thu Jan 1 00:01:25 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Sep 3 18:10:19 2021 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 07-09-2021 17:22
The BQM looks good for the most part. Minimum latency is a touch higher than usual, but only by around 3-4ms, but the yellow "DOCSIS fringe" of peak latency is very well contained. The eight hourly latency spikes I suspect are VM's not-such-a-bright-idea automatic speed tests currently being rolled out to all Hub 4 users. That leaves a restart (?) at about 9am, and an event about 4:30pm that could be an out of sequence speed check, or a T3 timeout causing the connection to drop back. So based on this 24 hour period I'm not seeing anything that indicates a problem.
Looking at other hub stats: Power levels all look OK (error levels aren't zero, but show as such due to shoddy hub firmware), SNR and modulation seem fine. There's a lot more of the network log than you posted, but based on what I can see of the hub status data I don't expect there's much of interest in the remaining log data.
So.....you I'm not disputing that you may be seeing latency/ping issues, but there's nothing there that indicates a continuing problem with the VM connection. Which leaves other options like gaming over problematic wifi, or internet traffic routing for the games you play. If you're still having problems, and it isn't wifi then it could be poor traffic routing by VM, which happens for some games/locations/times, but sometimes the only fix is to change ISP.
Sorry I can't point the finger to an obvious and easily fixed fault.
on 07-09-2021 17:56
Thanks a lot for looking into that for me,yeah it was just a router restart on them times. I agree I think it is just a routing problem to the game severs I’ve asked them about that before but they couldn’t help me. Guessing there’s nothing than can be done about that? Only other thing I can think of is changing ips to BT as I’ve seen they have better latency on there lines but I’m not confident switching atm
on 07-09-2021 19:07
not sure if this is relevant but i just tried this on pingplotter and its saying i have packet loss on the first hop 9 which is my connection)?
on 07-09-2021 19:08
an also packet loss further down the line on like hop 10-13 etc (25-75% loss)