on 25-11-2021 17:20
The ping has got LOTS better since upgrading to gig1, but it still is high compared to many, many others on here, some on Hub3's... my connection has intermittent low packet loss and the average ping is all over the place.
Can someone advise if this is acceptable and I am just being picky on it? My upload is also pathetic
Answered! Go to Answer
on 25-11-2021 21:29
@josh94 wrote:Well your saying my levels are good and someone else says they wont be helping, what's your thoughts? I always have high and erratic ping, and my upload fluctuates heavily when no usage is going on, down is not that effected but may just be my areas congested?
The levels are crap, trust me. For starters, the accepted range of DOCSIS power levels on VM's network is up to +10 dBmV, you have multiple channels at or above that. High power levels are of themselves an indication that the connection is noisy, although within permitted limits that would not matter if they were less than 10, and there were no other symptoms. Next up, the range of power levels is about 7.3 dBmV from lowest to highest, that's going to cause problems on its own - we frequently see problems when the range exceeds 4.5 dBmV. Then we have to consider that ideally power levels should be flat or slightly declining as frequency rises - but yours are going up steeply with frequency. That's an incorrectly set or faulty street cabinet amplifier resulting in incorrect "slope". There's also uncorrectable errors showing on the DOCSIS 3.1 channel, that's always a bad sign. Normally I'd expect to also see significant post-RS (uncorrectable) errors on the DOCSIS 3.0 channels. You'll see values of zero there, but that's not because there aren't any, it's because the Hub 4 firmware is a pile of steaming **** and shows zeroes rather than actual error counts. I can tell the two columns of zeroes are nonsense because a DOCSIS connection ALWAYS racks up pre-RS errors even if working well. The pre-RS errors are corrected, they don't matter, but their absence confirms that your hub is running the faulty firmware (like most other Hub 4s).
So all things considered, you've got a shonky connection, that either an area fault or it's your unique connection, either needs a technician.
In honesty, VM is not the network for gamers. When it's working well it's still marginally inferior to the latency of an Openreach connection. When things go wrong then cable technology is erratic and difficult to troubleshoot. And then you have VM's world famous technical support. In return for that, you can download games faster than Openreach, you just can't play them very well. When you're gaming, it uses less than 10 Mbps up and down.
on 25-11-2021 17:29
The upload has got a lot worse throughout the day, is there anyone that can check how congested my area is? I got a text earlier saying that they are doing maintenance in my area so I am hoping that is going to sort these issues out...
on 25-11-2021 17:30
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 331000000 | 10.300003 | 40.946209 | QAM256 | 25 |
1 | 139000000 | 5.099998 | 38.605377 | QAM256 | 1 |
2 | 147000000 | 5.300003 | 38.605377 | QAM256 | 2 |
3 | 155000000 | 5.199997 | 38.605377 | QAM256 | 3 |
4 | 163000000 | 5.300003 | 38.983261 | QAM256 | 4 |
5 | 171000000 | 5.500000 | 38.983261 | QAM256 | 5 |
6 | 179000000 | 5.900002 | 38.605377 | QAM256 | 6 |
7 | 187000000 | 6.199997 | 38.983261 | QAM256 | 7 |
8 | 195000000 | 6.400002 | 38.983261 | QAM256 | 8 |
9 | 203000000 | 6.500000 | 38.605377 | QAM256 | 9 |
10 | 211000000 | 6.699997 | 38.983261 | QAM256 | 10 |
11 | 219000000 | 7.000000 | 38.983261 | QAM256 | 11 |
12 | 227000000 | 7.099998 | 40.366287 | QAM256 | 12 |
13 | 235000000 | 7.199997 | 38.983261 | QAM256 | 13 |
14 | 243000000 | 7.300003 | 40.366287 | QAM256 | 14 |
15 | 251000000 | 7.099998 | 38.983261 | QAM256 | 15 |
16 | 259000000 | 6.800003 | 38.983261 | QAM256 | 16 |
17 | 267000000 | 6.699997 | 40.366287 | QAM256 | 17 |
18 | 275000000 | 7.599998 | 38.983261 | QAM256 | 18 |
19 | 283000000 | 8.699997 | 38.983261 | QAM256 | 19 |
20 | 291000000 | 9.900002 | 40.366287 | QAM256 | 20 |
21 | 299000000 | 10.699997 | 40.366287 | QAM256 | 21 |
22 | 307000000 | 10.300003 | 40.366287 | QAM256 | 22 |
23 | 315000000 | 9.800003 | 40.946209 | QAM256 | 23 |
24 | 323000000 | 9.699997 | 40.366287 | QAM256 | 24 |
26 | 339000000 | 11.000000 | 40.946209 | QAM256 | 26 |
27 | 347000000 | 12.000000 | 40.946209 | QAM256 | 27 |
28 | 355000000 | 12.400002 | 40.366287 | QAM256 | 28 |
29 | 363000000 | 12.199997 | 40.946209 | QAM256 | 29 |
30 | 371000000 | 11.400002 | 40.366287 | QAM256 | 30 |
31 | 379000000 | 10.900002 | 40.366287 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 40.946209 | 0 | 0 |
1 | Locked | 38.605377 | 0 | 0 |
2 | Locked | 38.605377 | 0 | 0 |
3 | Locked | 38.605377 | 0 | 0 |
4 | Locked | 38.983261 | 0 | 0 |
5 | Locked | 38.983261 | 0 | 0 |
6 | Locked | 38.605377 | 0 | 0 |
7 | Locked | 38.983261 | 0 | 0 |
8 | Locked | 38.983261 | 0 | 0 |
9 | Locked | 38.605377 | 0 | 0 |
10 | Locked | 38.983261 | 0 | 0 |
11 | Locked | 38.983261 | 0 | 0 |
12 | Locked | 40.366287 | 0 | 0 |
13 | Locked | 38.983261 | 0 | 0 |
14 | Locked | 40.366287 | 0 | 0 |
15 | Locked | 38.983261 | 0 | 0 |
16 | Locked | 38.983261 | 0 | 0 |
17 | Locked | 40.366287 | 0 | 0 |
18 | Locked | 38.983261 | 0 | 0 |
19 | Locked | 38.983261 | 0 | 0 |
20 | Locked | 40.366287 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.366287 | 0 | 0 |
23 | Locked | 40.946209 | 0 | 0 |
24 | Locked | 40.366287 | 0 | 0 |
26 | Locked | 40.946209 | 0 | 0 |
27 | Locked | 40.946209 | 0 | 0 |
28 | Locked | 40.366287 | 0 | 0 |
29 | Locked | 40.946209 | 0 | 0 |
30 | Locked | 40.366287 | 0 | 0 |
31 | Locked | 40.366287 | 0 | 0 |
39 | 96 | 4K | 1880 | QAM4096 | 424 |
39 | Locked | 43 | 11.2 | 291553137 | 268 |
on 25-11-2021 17:31
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39400000 | 46.520599 | 5120 KSym/sec | 64QAM | 2 |
2 | 32600000 | 46.520599 | 5120 KSym/sec | 64QAM | 3 |
3 | 25800000 | 47.020599 | 5120 KSym/sec | 64QAM | 4 |
4 | 46200000 | 46.270599 | 5120 KSym/sec | 64QAM | 1 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | US_TYPE_STDMA | 0 | 0 | 1 | 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 25-11-2021 17:31
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | cmreg-vmdg640-bbt076+voc-b.cm |
SFID | 106578 |
Max Traffic Rate | 1200000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 106577 |
Max Traffic Rate | 55000270 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | bestEffort |
on 25-11-2021 17:40
There's other factors that can drive poor latency, but you certainly won't be helped by your downstream power levels, which have too wide a range, some are too high, and overall they slope the wrong way. I'll mark this for the forum staff to take a look and advise. As and when that's been sorted, see how latency is, and we can see if there's other factors involved, and take it from there.
on 25-11-2021 18:27
Hi @josh94,
Thank you for your posts. I'm really sorry to hear you're having a little bit of trouble with your connection.
Using the details you provided when joining the forums, I've taken a look at your line and I can't see any problems there to explain what you seem to be experiencing.
Would you mind clarifying any diagnostics and troubleshooting you've done thus far in an effort to remedy this?
Thanks,
on 25-11-2021 19:36
Well your saying my levels are good and someone else says they wont be helping, what's your thoughts? I always have high and erratic ping, and my upload fluctuates heavily when no usage is going on, down is not that effected but may just be my areas congested?
on 25-11-2021 20:52
If you do a:
ping -t 194.168.4.100
and a speed test when it hits upload does your ping spike?
on 25-11-2021 20:59
What am I pinging? I am in modem mode, I presume you are pinging the DNS server when its in router mode so 192.168.100.1 should suffice that test?
Every line was like this:
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63