on 10-03-2024 12:26
We pay for 200mbps download and we aren't getting it. Also the ping is unreasonably high for what it ought to be.
I ran a wired speed test directly to the Super Hub 3 and this was the outcome:
See below status from the SH3. Anything out of kilter here?
Downstream bonded channels
Channel | Frequency (Hz) | Power (dBmV) | SNR (dB) | Modulation | Channel ID |
1 | 203000000 | 2.7 | 40 | 256 qam | 9 |
2 | 139000000 | 5 | 40 | 256 qam | 1 |
3 | 147000000 | 5.5 | 40 | 256 qam | 2 |
4 | 155000000 | 5.5 | 40 | 256 qam | 3 |
5 | 163000000 | 4.6 | 40 | 256 qam | 4 |
6 | 171000000 | 4.8 | 40 | 256 qam | 5 |
7 | 179000000 | 3.9 | 40 | 256 qam | 6 |
8 | 187000000 | 3.9 | 40 | 256 qam | 7 |
9 | 195000000 | 3.2 | 40 | 256 qam | 8 |
10 | 211000000 | 2.7 | 40 | 256 qam | 10 |
11 | 219000000 | 2.5 | 40 | 256 qam | 11 |
12 | 227000000 | 2.5 | 40 | 256 qam | 12 |
13 | 235000000 | 2.7 | 40 | 256 qam | 13 |
14 | 243000000 | 2.5 | 40 | 256 qam | 14 |
15 | 251000000 | 3 | 40 | 256 qam | 15 |
16 | 259000000 | 3 | 40 | 256 qam | 16 |
17 | 267000000 | 3.7 | 40 | 256 qam | 17 |
18 | 275000000 | 3.7 | 40 | 256 qam | 18 |
19 | 283000000 | 4.4 | 40 | 256 qam | 19 |
20 | 291000000 | 4.5 | 40 | 256 qam | 20 |
21 | 299000000 | 5.5 | 40 | 256 qam | 21 |
22 | 307000000 | 5.8 | 40 | 256 qam | 22 |
23 | 315000000 | 5 | 40 | 256 qam | 23 |
24 | 323000000 | 4.5 | 40 | 256 qam | 24 |
Downstream bonded channels
Channel | Locked Status | RxMER (dB) | Pre RS Errors | Post RS Errors |
1 | Locked | 40.3 | 107 | 0 |
2 | Locked | 40.3 | 43 | 0 |
3 | Locked | 40.3 | 20 | 0 |
4 | Locked | 40.3 | 28 | 0 |
5 | Locked | 40.3 | 17 | 0 |
6 | Locked | 40.9 | 30 | 0 |
7 | Locked | 40.9 | 11 | 0 |
8 | Locked | 40.3 | 16 | 0 |
9 | Locked | 40.3 | 26 | 0 |
10 | Locked | 40.3 | 38 | 0 |
11 | Locked | 40.3 | 42 | 0 |
12 | Locked | 40.3 | 38 | 0 |
13 | Locked | 40.9 | 33 | 0 |
14 | Locked | 40.3 | 38 | 0 |
15 | Locked | 40.3 | 35 | 0 |
16 | Locked | 40.3 | 31 | 0 |
17 | Locked | 40.3 | 40 | 0 |
18 | Locked | 40.3 | 30 | 0 |
19 | Locked | 40.3 | 39 | 0 |
20 | Locked | 40.3 | 30 | 0 |
21 | Locked | 40.3 | 44 | 0 |
22 | Locked | 40.3 | 37 | 0 |
23 | Locked | 40.3 | 39 | 0 |
24 | Locked | 40.3 | 57 | 0 |
Upstream bonded channels
Channel | Frequency (Hz) | Power (dBmV) | Symbol Rate (ksps) | Modulation | Channel ID |
1 | 49599970 | 43 | 5120 | 64 qam | 1 |
2 | 36600049 | 43.3 | 5120 | 64 qam | 3 |
3 | 43100000 | 43.3 | 5120 | 64 qam | 2 |
4 | 30100000 | 43.3 | 5120 | 64 qam | 4 |
5 | 23600000 | 43 | 5120 | 64 qam | 5 |
Upstream bonded channels
Channel | Channel Type | T1 Timeouts | T2 Timeouts | T3 Timeouts | T4 Timeouts |
1 | ATDMA | 0 | 0 | 2 | 0 |
2 | ATDMA | 0 | 0 | 4 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 2 | 0 |
5 | ATDMA | 0 | 0 | 1 | 0 |
General Configuration
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | cmreg-vmdg505-bbt057-b.cm |
Primary Downstream Service Flow
SFID | 107910 |
Max Traffic Rate | 143750047 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Network Log
Time | Priority | Description |
10/03/2024 12:13:16 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/03/2024 11:45:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/03/2024 01:38:50 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/03/2024 23:45:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/03/2024 18:15:36 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/03/2024 11:45:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/02/2024 01:27:31 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
27/02/2024 23:45:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/02/2024 18:34:35 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/02/2024 11:45:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/02/2024 02:58:55 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/02/2024 17:35:54 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/02/2024 14:32:22 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/02/2024 21:04:25 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/02/2024 16:13:23 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/02/2024 23:46:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/02/2024 04:06:32 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/02/2024 11:46:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/02/2024 02:23:38 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/02/2024 23:46:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
Answered! Go to Answer
on 11-03-2024 15:13
143750047 is the down stream profile for the M125 service with advertised speeds of 132 / 20 Mb/s
on 10-03-2024 13:28
What does this site show?
https://samknows.com/realspeed/
HUB stats look ok, other than the occasional timeout.
Keep in mind, however, your HUB is configured for 143Mbps bandwidth, not 200:
Primary Downstream Service Flow
SFID | 107910 |
Max Traffic Rate | 143750047 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
on 11-03-2024 15:13
143750047 is the down stream profile for the M125 service with advertised speeds of 132 / 20 Mb/s
on 13-03-2024 16:17
Hi @andy1027 👋.
Thanks for reaching out to us. Apologies for the issues that you are having with your internet. Since your post have you been able to resolve this, if not could you please provide us with some more recent results with any third party Hubs you may have attached and our Hub in router mode.
Keep us updated.
Sabrina
on 28-09-2024 13:59
Issue resolved. We have since moved home and have a new issue. I will post this on a separate thread