on 21-04-2022 20:43
Recently upgraded from 650Mbps to Gig1 and experiencing a lot of issues still.
I have conducted speedtests everyday to check consistency and I never manage to end up with consistent results during Peak times and Offpeak times. Max speed i have reached is 1.2Gbps, but that was for a split second, immidately after the connection drops to 300Mbps as does every other test I perform on any device.
I have reset my router settings, both Hub4 and ASUS AC86u, I have tried removing Modem mode and trying only via the Hub4 and still get the same results. I then decided to replace my CAT 5E Ethernet with a brand new CAT 8.1 with the same results.
I have even gone as far as disabling QoS, DNS changes and changing buffer sizes on windows, with still the same results.
I have put everything back to how it is on default settings, is there anything I am not doing that I should be?
I have noticed that dBmV levels seem extremely abnormal compared to other results and notice that uncorrectables is 600~ tho I believe this may not be an issue as ive only seen people say its only an issue in the thousands. As for the noise margin, im not too sure what the expected is.
Posted all below! Let me know if you require anything else! Thanks!
Answered! Go to Answer
on 25-04-2022 06:40
I've marked that for staff to pick up again. If you're still seeing really poor power levels (downstream lower than -5 dBmV, including the 3.1 channel) then the problem still exists and you'll need a technician. If @jb66 is correct in their well reasoned diagnosis, then a fix could be moving you onto a new tap, which is a quick and easy fix, if the problem is across the whole frame due to a physically faulty cabinet then it might take repeated attempts to get put right, and a degree of persistence on your part. Potentially the area SNR fault was due to water ingress, somebody's used a tea towel on the cabinet, but it wouldn't be the first time to see a CBU fault that recurs due to inadequate diagnosis and a consequent lack of joined up rectification by the disjointed teams that VM might need to fix a moderately complex problem. Give thought to asking for a complaint to be raised under the minimum speed guarantee, and I'd recommend you try to stick to communicating with VM through this forum - whilst it isn't real time and that can be frustrating, you're dealing with well intentioned UK based staff, as opposed to the very, very poor offshore call centres who respond to telephone calls.
In terms of operational policy, VM will always defer attending to individual faults whilst an area fault is reported, because that makes good sense, as customers can't distinguish whether their problem is caused by the area fault or something else, and most of the time neither can VM staff.
On your BQM, the mid level humps are down to problems with peering, and affect all VM customers. It's been going on for weeks now, with no signs of explanation or the matter being addressed. This is completely separate to the speed problem.
on 21-04-2022 20:44
Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream
Cable Modem Status | Online | DOCSIS 3.1 |
Primary downstream channel | Locked | SC-QAM |
DOCSIS 3.0 channels | 31 | 4 |
DOCSIS 3.1 channels | 1 | 0 |
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 330750000 | -6.9 | 38.6 | QAM256 | 25 |
1 | 138750000 | 1.7 | 40.9 | QAM256 | 1 |
2 | 146750000 | 1.3 | 40.9 | QAM256 | 2 |
3 | 154750000 | 1.2 | 40.9 | QAM256 | 3 |
4 | 162750000 | 0.7 | 40.4 | QAM256 | 4 |
5 | 170750000 | 0.3 | 40.9 | QAM256 | 5 |
6 | 178750000 | -0.2 | 40.4 | QAM256 | 6 |
7 | 186750000 | -0.6 | 40.4 | QAM256 | 7 |
8 | 194750000 | -1 | 40.9 | QAM256 | 8 |
9 | 202750000 | -1.4 | 40.9 | QAM256 | 9 |
10 | 210750000 | -1.6 | 40.9 | QAM256 | 10 |
11 | 218750000 | -2 | 40.9 | QAM256 | 11 |
12 | 226750000 | -2.1 | 40.4 | QAM256 | 12 |
13 | 234750000 | -2.4 | 40.4 | QAM256 | 13 |
14 | 242750000 | -2.7 | 40.9 | QAM256 | 14 |
15 | 250750000 | -2.9 | 40.4 | QAM256 | 15 |
16 | 258750000 | -2.9 | 40.4 | QAM256 | 16 |
17 | 266750000 | -3.6 | 40.9 | QAM256 | 17 |
18 | 274750000 | -4.1 | 40.4 | QAM256 | 18 |
19 | 282750000 | -4.2 | 40.4 | QAM256 | 19 |
20 | 290750000 | -4.2 | 40.4 | QAM256 | 20 |
21 | 298750000 | -4.3 | 40.4 | QAM256 | 21 |
22 | 306750000 | -5.1 | 40.4 | QAM256 | 22 |
23 | 314750000 | -5.9 | 38.6 | QAM256 | 23 |
24 | 322750000 | -6.7 | 38.6 | QAM256 | 24 |
26 | 338750000 | -7.4 | 38.6 | QAM256 | 26 |
27 | 346750000 | -7.6 | 38.6 | QAM256 | 27 |
28 | 354750000 | -8 | 37.6 | QAM256 | 28 |
29 | 362750000 | -8.3 | 37.6 | QAM256 | 29 |
30 | 370750000 | -8.6 | 37.6 | QAM256 | 30 |
31 | 378750000 | -9 | 37.6 | QAM256 | 31 |
on 21-04-2022 20:44
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 38.605377 | 0 | 0 |
1 | Locked | 40.946209 | 0 | 0 |
2 | Locked | 40.946209 | 0 | 0 |
3 | Locked | 40.946209 | 0 | 0 |
4 | Locked | 40.366287 | 0 | 0 |
5 | Locked | 40.946209 | 0 | 0 |
6 | Locked | 40.366287 | 0 | 0 |
7 | Locked | 40.366287 | 0 | 0 |
8 | Locked | 40.946209 | 0 | 0 |
9 | Locked | 40.946209 | 0 | 0 |
10 | Locked | 40.946209 | 0 | 0 |
11 | Locked | 40.946209 | 0 | 0 |
12 | Locked | 40.366287 | 0 | 0 |
13 | Locked | 40.366287 | 0 | 0 |
14 | Locked | 40.946209 | 0 | 0 |
15 | Locked | 40.366287 | 0 | 0 |
16 | Locked | 40.366287 | 0 | 0 |
17 | Locked | 40.946209 | 0 | 0 |
18 | Locked | 40.366287 | 0 | 0 |
19 | Locked | 40.366287 | 0 | 0 |
20 | Locked | 40.366287 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.366287 | 0 | 0 |
23 | Locked | 38.605377 | 0 | 0 |
24 | Locked | 38.605377 | 0 | 0 |
26 | Locked | 38.605377 | 1 | 0 |
27 | Locked | 38.605377 | 0 | 0 |
28 | Locked | 37.636276 | 0 | 0 |
29 | Locked | 37.636276 | 0 | 0 |
30 | Locked | 37.636276 | 0 | 0 |
31 | Locked | 37.636276 | 0 | 0 |
on 21-04-2022 20:45
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159 | 96 | 4K | 1880 | QAM256 | 759 |
Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159 | Locked | 29 | -21 | 1318106527 | 619 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39400000 | 42 | 5120 KSym/sec | 64QAM | 12 |
2 | 46200000 | 43 | 5120 KSym/sec | 64QAM | 11 |
3 | 53700000 | 44 | 5120 KSym/sec | 64QAM | 10 |
4 | 60300000 | 45 | 5120 KSym/sec | 64QAM | 9 |
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 |
SFID | 973 |
Max Traffic Rate | 1200000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
on 21-04-2022 20:46
Looks like water in the taps outside, high end is away, what signal level is your 3.1 channel?
on 21-04-2022 20:47
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159 | 96 | 4K | 1880 | QAM256 | 759 |
Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159 | Locked | 29 | -21 | 1318106527 | 619 |
21-04-2022 20:47 - edited 21-04-2022 20:47
Posted Above
on 21-04-2022 20:47
on 21-04-2022 20:50
Lol, sounds good. I guess I shall wait for them to check this post. Do you think this may be the root cause of the extreme instability with the inability to reach anywhere near minimum predicted speeds?
on 21-04-2022 21:12
@Declan_1242 wrote:Lol, sounds good. I guess I shall wait for them to check this post. Do you think this may be the root cause of the extreme instability with the inability to reach anywhere near minimum predicted speeds?
Almost definitely the root cause.