Power levels ok? BQM all over the place lately...

[robbiekhan]

Hi, recently my BQM has been showing massive spikes for the maximum latency. I've noticed that my speeds are affected if I start a download on Steam, for example, even though I'm manually locking download speeds at 100MB/s which in the past has been no problem and allowed me to stream anything online and not buffer. Without locking the DL speed in apps like Steam I was able to download at circa 118MB/s, or as mentioned, browse/stream etc with no issues.

I'm on a HUB4, when I was on a HUB3 before upgrading to Gig1, an attenuator was attached by the technician who dropped the HUB3 off at the time. I was told the attenuator would not be needed for Gig1 when arranging the self install kit with the HUB4, and it has been fine since install over a year ago. Until now.

For ref, I am on modem only mode and use my own router (Asus RT AC-68U).

ANy advice apprecaited, maybe need a technician out to investigate?

BQM:

Stats from hub in the reply post below.

[robbiekhan]

3.0 Downstream channels

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

8	194750000	5.500000	37.636276	QAM256	8
1	138750000	4.900002	37.355988	QAM256	1
2	146750000	4.900002	37.636276	QAM256	2
3	154750000	4.800003	37.636276	QAM256	3
4	162750000	4.800003	37.636276	QAM256	4
5	170750000	5.000000	37.636276	QAM256	5
6	178750000	5.199997	37.636276	QAM256	6
7	186750000	5.300003	37.636276	QAM256	7
9	202750000	6.099998	37.355988	QAM256	9
10	210750000	5.800003	37.636276	QAM256	10
11	218750000	5.900002	37.636276	QAM256	11
12	226750000	6.000000	37.636276	QAM256	12
13	234750000	5.099998	37.636276	QAM256	13
14	242750000	6.000000	37.636276	QAM256	14
15	250750000	6.199997	37.636276	QAM256	15
16	258750000	5.800003	37.636276	QAM256	16
17	266750000	6.000000	37.636276	QAM256	17
18	274750000	6.300003	37.636276	QAM256	18
19	282750000	6.000000	37.636276	QAM256	19
20	290750000	6.400002	37.355988	QAM256	20
21	298750000	7.300003	37.636276	QAM256	21
22	306750000	6.199997	37.636276	QAM256	22
23	314750000	6.000000	38.605377	QAM256	23
24	322750000	6.599998	37.636276	QAM256	24
25	330750000	5.699997	37.636276	QAM256	25
26	338750000	5.900002	38.605377	QAM256	26
27	346750000	6.400002	38.605377	QAM256	27
28	354750000	5.699997	37.636276	QAM256	28
29	362750000	6.500000	38.605377	QAM256	29
30	370750000	7.000000	38.605377	QAM256	30
31	378750000	6.199997	37.636276	QAM256	31

3.0 Downstream channels

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

8	Locked	37.636276	0	0
1	Locked	37.355988	0	0
2	Locked	37.636276	0	0
3	Locked	37.636276	0	0
4	Locked	37.636276	0	0
5	Locked	37.636276	0	0
6	Locked	37.636276	0	0
7	Locked	37.636276	0	0
9	Locked	37.355988	0	0
10	Locked	37.636276	0	0
11	Locked	37.636276	0	0
12	Locked	37.636276	0	0
13	Locked	37.636276	0	0
14	Locked	37.636276	0	0
15	Locked	37.636276	0	0
16	Locked	37.636276	0	0
17	Locked	37.636276	0	0
18	Locked	37.636276	0	0
19	Locked	37.636276	0	0
20	Locked	37.355988	0	0
21	Locked	37.636276	0	0
22	Locked	37.636276	0	0
23	Locked	38.605377	0	0
24	Locked	37.636276	0	0
25	Locked	37.636276	0	0
26	Locked	38.605377	0	0
27	Locked	38.605377	0	0
28	Locked	37.636276	0	0
29	Locked	38.605377	0	0
30	Locked	38.605377	0	0
31	Locked	37.636276	0	0

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

37

94

4K

1800

QAM4096

424

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

37

Locked

40

7.6

1943461422

13

[robbiekhan]

3.0 Upstream channels

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

1	30100000	40.020599	5120 KSym/sec	32QAM	4
2	43100000	39.270599	5120 KSym/sec	32QAM	2
3	36600000	39.520599	5120 KSym/sec	32QAM	3
4	49600000	39.020599	5120 KSym/sec	32QAM	1
5	23600000	40.020599	5120 KSym/sec	16QAM	5

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	US_TYPE_ATDMA	0	0	0	0
2	US_TYPE_ATDMA	0	0	0	0
3	US_TYPE_ATDMA	0	0	0	0
4	US_TYPE_ATDMA	0	0	0	0
5	US_TYPE_ATDMA	0	0	0	0

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation

6

10.8

33.5

2K

QAM8

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts

6

OFDMA

220

53.4

2

0

[Jonny-M]

Looks like an SnR fault with the low modulation rates on the upstream, unfortunately it could take months for VM to fix.

[robbiekhan]

Damn 😕

Well Toob have recently installed FTTP on my road and come the summer should be going live, so looks like I will be jumping away as soon as that happens if VM don't fix this.

[Tom_W1]

Hi @robbiekhan thanks for your post here in the Community, although we're sorry to hear of the concerns you've raised here regarding your connections.

I've ran some checks here and I can see that there is currently an outage affecting your services, sincere apologies for this.

The latest info we have on this is that it is due to be fixed by May 8th at approximately 15:00.

If this is still happening after this time, please let us know and we can review this again for you.

Many thanks

[robbiekhan]

@Tom_W1 thanks, the service status page that VM on twitter reference says no issues hence the confusion. Will there be any credit to the bill for the affected service for all this time?

[legacy1]

The outage likely has nothing to do with what your seeing in your BQM

[robbiekhan]

I posted my BQM on another forum's networking section and this is the consensus:

Upstream congestion, usually that means they sold to too many customers locally on your node. Fix can often be several months or even years away.

"However you have noise on your upstream channels which reduces the effective capacity (they should be QAM64). So if they fix that then it might ease off a bit, but with that graph."

[robbiekhan]

Oops that was meant to be:

"Upstream congestion, usually that means they sold to too many customers locally on your node. Fix can often be several months or even years away.

However you have noise on your upstream channels which reduces the effective capacity (they should be QAM64). So if they fix that then it might ease off a bit, but with that graph, I would be moaning, and looking at competitors."