on 23-11-2023 23:53
I was on 250Mbps via a SuperHub 3, but yesterday switched to 1Gbps via Superhub 5.
I initially had a bit of a flakey connection, but reconnected the copper cable to the white wall socket that hadn't been tightened by the engineer properly. Rebooted router. BMQ now looks mostly okay, Router stats not too bad.
But various speed/latency/bufferbloat tests give quite a wide range of results. I was expecting better quality than with the Hub 3, but it felt like I had a more consistent quality connection with my hub 3 250Mbps connection, lower average ping for example playing some games, such as Rocket League.
My Upstream seems rock solid, with all tests showing consistent 100Mbps with low active load latency (grade A on the buffer bloat test, +2ms latency).
It's the download that seems a bit flakey still (buffer bloat test often reports a grade E downstream, with my downstream active load latency at +54ms).
Download speed tests seem to report varying figures, averaging around 780Mbps, running on a PC connected with gigabit ethernet.
Downstream power levels for channels range between 3.8 to 7.5, SNR 41-42. Over a 24 hour period, I seem to have accululated in the range of 4 to 13 Pre RS errors on each channel. No Post RS errors though.
3.1 Downstream channels, Active Profile corrected errors is now over 875M (no uncorrectable errors though).
23-11-2023 23:57 - edited 23-11-2023 23:59
I have noticed a small amount of packet loss on BMQ graph.
2am - 9am had a more consistent latency. I see more variance in the average latency and maximum latency this afternoon/evening.
on 24-11-2023 00:16
on 24-11-2023 00:25
This seems to suggest that perhaps the connection from the hub to desktop PC (via ethernet cable) is introducing additional latency and jitter. Are all ports equal on the Hub 5? Perhaps the ethernet cable should be replaced (it's not marked what grade it is - blue colour, I think it came with the Hub 3). Would Cat 5E be fine, or should I get Cat 6 or higher?
on 24-11-2023 14:44
Your connection looks fine Buffer Bloat happens on load as to how limiting handles traffic which you may be buffer at the hub normally on lower speed package or at VM gateway to buffer as HFQ should their be load by others in your area meaning you can't hit your full speed.
on 25-11-2023 00:13
I am less worried about full speed, more worried about latency. It seems that when I run Rocket League now, I am seeing slightly higher pings (maybe 5-10ms higher than I used to see). On the BMQ graph during prime times, I am seeing more blue colour than previously, meaning my average ping has more variance (jitter?). I do wonder if the connection from router to PC is actually adding a bit more latency, and will try to get a new CAT 5E or 6 cable, if that could be the problem?
25-11-2023 11:31 - edited 25-11-2023 11:37
All looks normal for a VM connection using DOCSIS.
In fact it looks like a very good connection in your area.
My area for comparison (Rebooted at 8pm!):
Technically there could be a fault in the area, however unsure if VM would acknowledge.
Assuming your HUB 5 is on the latest firmware what do the upstream stats look like?
on 25-11-2023 22:45
Here are my downstream stats:
3.0 Downstream channels
1 | 331000000 | 5.3 | 40 | QAM 256 | 25 |
2 | 179000000 | 7.5 | 42 | QAM 256 | 6 |
3 | 187000000 | 7.6 | 42 | QAM 256 | 7 |
4 | 195000000 | 7.7 | 42 | QAM 256 | 8 |
5 | 203000000 | 7.5 | 42 | QAM 256 | 9 |
6 | 211000000 | 7.4 | 42 | QAM 256 | 10 |
7 | 219000000 | 7.3 | 42 | QAM 256 | 11 |
8 | 227000000 | 7.2 | 42 | QAM 256 | 12 |
9 | 235000000 | 7.1 | 42 | QAM 256 | 13 |
10 | 243000000 | 7 | 42 | QAM 256 | 14 |
11 | 251000000 | 6.7 | 42 | QAM 256 | 15 |
12 | 259000000 | 6.4 | 41 | QAM 256 | 16 |
13 | 267000000 | 6.3 | 41 | QAM 256 | 17 |
14 | 275000000 | 6.1 | 41 | QAM 256 | 18 |
15 | 283000000 | 5.9 | 41 | QAM 256 | 19 |
16 | 291000000 | 5.8 | 41 | QAM 256 | 20 |
17 | 299000000 | 5.7 | 41 | QAM 256 | 21 |
18 | 307000000 | 5.8 | 41 | QAM 256 | 22 |
19 | 315000000 | 5.7 | 41 | QAM 256 | 23 |
20 | 323000000 | 5.6 | 40 | QAM 256 | 24 |
21 | 339000000 | 5.3 | 41 | QAM 256 | 26 |
22 | 347000000 | 5.1 | 41 | QAM 256 | 27 |
23 | 355000000 | 5.1 | 41 | QAM 256 | 28 |
24 | 363000000 | 4.9 | 41 | QAM 256 | 29 |
25 | 371000000 | 4.8 | 41 | QAM 256 | 30 |
26 | 379000000 | 5 | 41 | QAM 256 | 31 |
27 | 387000000 | 4.8 | 41 | QAM 256 | 32 |
28 | 395000000 | 4.6 | 41 | QAM 256 | 34 |
29 | 403000000 | 4.5 | 41 | QAM 256 | 35 |
30 | 411000000 | 4.3 | 41 | QAM 256 | 36 |
31 | 419000000 | 4.2 | 41 | QAM 256 | 37 |
3.0 Downstream channels
1 | Locked | 40 | 26 | 0 |
2 | Locked | 42 | 24 | 0 |
3 | Locked | 42 | 16 | 0 |
4 | Locked | 42 | 26 | 0 |
5 | Locked | 42 | 18 | 0 |
6 | Locked | 42 | 21 | 0 |
7 | Locked | 42 | 17 | 0 |
8 | Locked | 42 | 13 | 0 |
9 | Locked | 42 | 17 | 0 |
10 | Locked | 42 | 13 | 0 |
11 | Locked | 42 | 29 | 0 |
12 | Locked | 41 | 20 | 0 |
13 | Locked | 41 | 12 | 0 |
14 | Locked | 41 | 29 | 0 |
15 | Locked | 41 | 20 | 0 |
16 | Locked | 41 | 26 | 0 |
17 | Locked | 41 | 26 | 0 |
18 | Locked | 41 | 30 | 0 |
19 | Locked | 41 | 32 | 0 |
20 | Locked | 40 | 25 | 0 |
21 | Locked | 41 | 39 | 0 |
22 | Locked | 41 | 35 | 0 |
23 | Locked | 41 | 44 | 0 |
24 | Locked | 41 | 44 | 0 |
25 | Locked | 41 | 47 | 0 |
26 | Locked | 41 | 56 | 0 |
27 | Locked | 41 | 38 | 0 |
28 | Locked | 41 | 49 | 0 |
29 | Locked | 41 | 42 | 0 |
30 | Locked | 41 | 27 | 0 |
31 | Locked | 41 | 42 | 0 |
3.1 Downstream channels
33 | 94 | 4K | 1840 | QAM 4096 | 1108 |
3.1 Downstream channels
33 | Locked | 41 | 3.2 | 3016234918 | 5 |
on 25-11-2023 22:45
Here's the upstream stats:
3.0 Upstream channels
0 | 49600000 | 41.3 | 5120 | QAM 64 | 1 |
1 | 43100000 | 40.5 | 5120 | QAM 64 | 2 |
2 | 36600000 | 40.3 | 5120 | QAM 64 | 3 |
3 | 30100000 | 39.8 | 5120 | QAM 64 | 4 |
4 | 23600000 | 39.3 | 5120 | QAM 64 | 5 |
3.0 Upstream channels
0 | ATDMA | 0 | 0 | 0 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
3.1 Upstream channels
12 | 10.4 | 37.2 | 2K | QAM 256 |
3.1 Upstream channels
12 | OFDMA | 208 | 74000000 | 0 | 0 |
25-11-2023 22:50 - edited 25-11-2023 22:54
I have noticed that I get a lag spike, often associated with packet loss, repeatedly exactly every 8 hours, just before 6am, 2pm, 10pm. Seems to happen every day at exactly the same time.