on 02-09-2021 16:14
I have a PC with Gigabit connection connected directly to the Hub4 via a Cat 5e Gigabit cable - Distance about 4 to 5 metres.Connected to my hub presently and for all testing are my pc and my iphone 8. I previously had an M600 package with almost identical issues then whilst transiting to the 1Gb package, moved to M200 for about a week and that work flawlessly from start to finish!!!
I had 1Gb installed last week and haven't got anything greater than 943Mbps but overall average is around 4-500Mbps?
I have used countless speedtests and are generally in unison that my connection is slow - Realspeed Samknows shows anything from 350 to 980 but usually is in the 400's.My upload speeds are averaging around 50, latency around 15 and packet loss always less than 1.0 (last check was -0.121.
Regards wifi, my phone on last check using Samknows was 397 to hub and 319 to phone - Ookla test was 479 up and 49.5 down. Overall any test on my phone will show anything from 69Mbps to 500Mbps sitting right next to the router?
I'm confused as to why a) I'm not getting a decent speed e.g. always over say 850 and b. Why my readings are so widely variable?
Last speed test run/ethernet:
nperf.com: down 246 up 51.63
Fast.com: down 290 up 50
Samknows: down 390 down 293
Thinkbroadband: down 215 up 39.7
Ookla Website: down 351 up 52.84
Ookla Windows app: down 676 up 52.80
iPhone 8 Wifi: Ookla app: down 358 up 43.5 Realspeed Samknows: down 397 down 319
Answered! Go to Answer
on 11-09-2021 07:10
If the Hub 4 is in modem mode the forum staff won't be able to do a remote check on status, so it may need reverting back to router mode. If you get an "all looks good from our side" response you may need to be very persistent to get such an intermittent fault fixed.
The problem may be the range of power levels as already suggested, could also be an RF noise ingress issue, which would show up as post-RS errors on selected downstream channels. A post-RS error is an error that cannot be corrected by the hub's built in Reed Solomon error correction routines, and uncorrectable errors, even at low numbers are damaging for speeds because the data has to be re-requested. Pre-RS errors are those that have been corrected, these have negligible impact unless the numbers are very high. Unfortunately the dreadful firmware of the Hub 4 has a bug and doesn't reliably show pre or post RS error counts, so I can't comment other than to observe that the current showing of two columns of zero errors is not feasible - DOCSIS is an error prone technology, even when working properly there will be at least some pre-RS errors. I also note that there's "uncorrectables" (post-RS errors) on the D3.1 channel - that's an indication of a probable noise problem as well.
on 02-09-2021 16:15
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 331000000 | 2.700001 | 38.983261 | QAM256 | 25 |
1 | 139000000 | 6.400002 | 38.605377 | QAM256 | 1 |
2 | 147000000 | 6.500000 | 38.983261 | QAM256 | 2 |
3 | 155000000 | 6.500000 | 40.366287 | QAM256 | 3 |
4 | 163000000 | 5.800003 | 38.983261 | QAM256 | 4 |
5 | 171000000 | 5.400002 | 40.366287 | QAM256 | 5 |
6 | 179000000 | 5.000000 | 38.983261 | QAM256 | 6 |
7 | 187000000 | 4.900002 | 40.366287 | QAM256 | 7 |
8 | 195000000 | 4.699997 | 40.366287 | QAM256 | 8 |
9 | 203000000 | 4.300003 | 38.983261 | QAM256 | 9 |
10 | 211000000 | 4.300003 | 38.983261 | QAM256 | 10 |
11 | 219000000 | 4.199997 | 40.366287 | QAM256 | 11 |
12 | 227000000 | 4.099998 | 40.366287 | QAM256 | 12 |
13 | 235000000 | 4.199997 | 38.983261 | QAM256 | 13 |
14 | 243000000 | 4.500000 | 40.366287 | QAM256 | 14 |
15 | 251000000 | 4.400002 | 40.366287 | QAM256 | 15 |
16 | 259000000 | 4.699997 | 40.946209 | QAM256 | 16 |
17 | 267000000 | 4.599998 | 38.983261 | QAM256 | 17 |
18 | 275000000 | 4.300003 | 40.366287 | QAM256 | 18 |
19 | 283000000 | 3.900002 | 38.983261 | QAM256 | 19 |
20 | 291000000 | 3.700001 | 40.366287 | QAM256 | 20 |
21 | 299000000 | 3.799999 | 40.366287 | QAM256 | 21 |
22 | 307000000 | 3.500000 | 40.366287 | QAM256 | 22 |
23 | 315000000 | 3.200001 | 38.983261 | QAM256 | 23 |
24 | 323000000 | 2.799999 | 38.983261 | QAM256 | 24 |
26 | 371000000 | 2.200001 | 40.366287 | QAM256 | 26 |
27 | 379000000 | 2.299999 | 40.366287 | QAM256 | 27 |
28 | 387000000 | 2.400002 | 40.366287 | QAM256 | 28 |
29 | 395000000 | 2.599998 | 38.983261 | QAM256 | 29 |
30 | 403000000 | 2.700001 | 40.366287 | QAM256 | 30 |
31 | 411000000 | 2.700001 | 40.366287 | QAM256 | 31 |
3.0 Downstream channels
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 38.983261 | 0 | 0 |
1 | Locked | 38.605377 | 0 | 0 |
2 | Locked | 38.983261 | 0 | 0 |
3 | Locked | 40.366287 | 0 | 0 |
4 | Locked | 38.983261 | 0 | 0 |
5 | Locked | 40.366287 | 0 | 0 |
6 | Locked | 38.983261 | 0 | 0 |
7 | Locked | 40.366287 | 0 | 0 |
8 | Locked | 40.366287 | 0 | 0 |
9 | Locked | 38.983261 | 0 | 0 |
10 | Locked | 38.983261 | 0 | 0 |
11 | Locked | 40.366287 | 0 | 0 |
12 | Locked | 40.366287 | 0 | 0 |
13 | Locked | 38.983261 | 0 | 0 |
14 | Locked | 40.366287 | 0 | 0 |
15 | Locked | 40.366287 | 0 | 0 |
16 | Locked | 40.946209 | 0 | 0 |
17 | Locked | 38.983261 | 0 | 0 |
18 | Locked | 40.366287 | 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 | 38.983261 | 0 | 0 |
24 | Locked | 38.983261 | 0 | 0 |
26 | Locked | 40.366287 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 40.366287 | 0 | 0 |
29 | Locked | 38.983261 | 0 | 0 |
30 | Locked | 40.366287 | 0 | 0 |
31 | Locked | 40.366287 | 0 | 0 |
33 | 80 | 4K | 1560 | QAM4096 | 424 |
33 | Locked | 42 | 3.1 | 58135192 | 18 |
on 02-09-2021 16:16
3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 32600000 | 44.270599 | 5120 KSym/sec | 64QAM | 5 |
2 | 39400000 | 44.020599 | 5120 KSym/sec | 64QAM | 4 |
3 | 46200000 | 43.770599 | 5120 KSym/sec | 64QAM | 3 |
4 | 25800000 | 44.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 | 3 | 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 02-09-2021 16:17
on 02-09-2021 16:17
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; |
Wed Sep 1 19:13:02 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; |
Wed Sep 1 21:27:05 2021 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Sep 1 23:05:43 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-09-2021 16:33 - edited 02-09-2021 16:36
Sometimes it is just the speed test sites that are unreliable, for example when I did SamKnows I got 230Mb to hub but 660 Mb to computer 😄 Often the length of the test is often too short, particularly for wifi where beamforming can come into play.
You have to know which server on a speedtest can provide reliable data.
Approx 940Mb is the speed you should see wired to a PC, assuming it is not some under powered netbook
The max you will see on an Iphone 8 is a theoretical 867Mbps, there will no doubt be some overhead in that which would drop the speed you receive down on wifi 5, I know on my own Wifi 5 laptop I don't often see more than 400Mb from an internet speed test unless I have 160Mhz channels enabled. (Non VM wifi) at which point I can max it.
You could try a wifi site survey and set the router up on a non congested channel and perhaps if you have no old wifi devices just put it in AC mode on Ghz.
on 02-09-2021 16:41
Is that fixable because currently VM call taker said there's no issues and i can go on the 30 day check?!!!!
on 02-09-2021 19:31
@lotharmat wrote:
I'm wondering if the spread of power (d/s) of 2.2 - 6.6 dBmV is causing a problem!
Could be!
A power attenuator could be a easy fix.
ewhitey have you set up a BQM yet?
It may help to illuminate the problem.
You could also try this as a temporary measure...
1. Turn off Smart WIFI
2. Turn off 2.4g WIFI
3. Make sure 5G WIFI channel width is set to 20/40/80.
Retest at close range and pray.
03-09-2021 01:05 - edited 03-09-2021 01:17
Hi there
I'll give that a go later and thanks for your help (and others above).
This evening we disconnected everything and connected the Hub 4 to the cable coming into the house. Then connected my lads laptop, my pc and eventually our two mobiles to test wifi. We tested many times over ethernet and wifi using RealSpeed Samknows then later a few times for luck with Ookla. The results that came back helped us ruled out any "forward" line issues as most of the time, from cable to Hub 4, we had around 7-800 average (never higher than 985 or lower than 387) with fluctuations but i'm assuming these are to be expected? At any one time only one device was connected whether via ethernet or wifi. The download speeds from Hub4 to device were as before pretty low averaging maybe 3-350 Mbps (occasionally lower!). The wifi speeds on the phones were showing low in the 40-70 range for download speed using Ookla and that's sitting beside the router.
Next we put the Hub4 into modem mode and linked up my Asus RT-AC86U router. Same tests again and almost immediately there were huge differences. The SamKnows download speeds were (strangely) more consistent - averaging maybe 850Mbps and the Hub to device speed increased by around 200Mbps - The phone wifi speeds went from double to triple figures averaging out around 450Mbps.
I'll continue recording my readings but it appears that the Hub4 just isn't up to the job. VM can send the signal to the Hub4 (but not without fluctuation and and certainly not the 1 Gb advertised - I have only seen 4 figures three times since installation. From Hub4 to device whether ethernet or wifi is just woeful and it's terrible that I have to use another router to carry the can for the Hub4. What annoys me is that all VM will say when you call them is we'll put you on a 30 day Ofcom monitor yada yada - No mention of actually trying to fix the issue and certainly no mention of retaining you as a customer. I've been with VM for over 25 or so years - our line's been there since the NTL days - and I've never been so messed about as I have been over the past month or so. Calltakers blatantly lying, departments not returning calls, people hanging up during calls by "getting cut off", giving faulty email addresses and even cutting our services by mistake leaving us with nothing for three days - It's ridiculous and unacceptable and VM need to get a grip! I will add however that I have the greatest respect and give thanks again to those on these forums who give their time to provide support - I wonder however, how many people are sitting just putting up with what they have and stressing out as they can't come on here and don't have some kind of technical understanding.
Going back a month or so, we had an almost identical issue with our M600 signal and I thought the Hub3 was faulty. Despite crying out for a hub change they basically did nothing except bang on about the 30 day Ofcom monitor then as mentioned, cut our connection by mistake. Our package was reinstalled, more "mistakes" were made and we ended up with a shiny new Hub3 but on M200. Everything then worked fine - stable acceptable speeds until of course it all changed after the 1GB/Hub4 install - Why was that? The caveat VM has is their "minimum guarantee to the hub" meaning they don't need to concern themselves about what happens beyond it. Of course in my case, I'm not even getting that guaranteed speed most of the time, just some of it. It's seems so wrong that I am forced to use another router to get some (not all) of what I'm already paying for but worse still that VM are allowed to get away with it in the first place. At the end of the day, I spent most this afternoon waiting on the phone with VM to yet again be told all we can do is start a 30 day monitor and you can leave if you want. The rest of the day was spent troubleshooting with you guys and with ONLY single devices connected to a Hub by ethernet or wifi, the Hub with its superfast 1Gb connection STILL couldn't put out a stable, acceptable speed - How is this right and how can they say that everything is working fine - Is the Hub faulty or simply not fit for purpose? 😞
on 04-09-2021 16:25
Just to let you know, as we had similar problems with speed.
Engineer been out and cable needs replacing between our house and VM cabinet 1000m away!
Planned in for 13th this month, will keep you posted.
Simon