Forum Discussion

Ninko's avatar
Ninko
Tuning in
2 years ago

Download speed slower then normal - GL52 area

Hi, 

Recently noticed download speeds slower then normal - no problems showing in my area: 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
12030000005.840256 qam9
2139000000638256 qam1
31470000005.840256 qam2
41550000005.940256 qam3
51630000005.940256 qam4
6171000000640256 qam5
7179000000640256 qam6
81870000005.940256 qam7
91950000005.840256 qam8
102110000005.840256 qam10
112190000005.840256 qam11
122270000005.640256 qam12
132350000005.540256 qam13
142430000005.540256 qam14
152510000005.540256 qam15
16259000000540256 qam16
172670000004.940256 qam17
18275000000540256 qam18
192830000005.840256 qam19
202910000006.140256 qam20
212990000006.640256 qam21
223070000006.540256 qam22
233150000006.540256 qam23
243230000006.540256 qam24


Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked40.3110
2Locked38.9720
3Locked40.9550
4Locked40.3360
5Locked40.9260
6Locked40.9170
7Locked40.390
8Locked40.960
9Locked40.9140
10Locked40.340
11Locked40.990
12Locked40.970
13Locked40.370
14Locked40.3110
15Locked40.9130
16Locked40.9120
17Locked40.360
18Locked40.380
19Locked40.390
20Locked40.370
21Locked40.3110
22Locked40.370
23Locked40.9190
24Locked40.3220

9 Replies

  • Upstream bonded channels

    Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
    12360000044.3512016 qam5
    23660000043.8512064 qam3
    33010000043.5512064 qam4
    44310000044.3512064 qam2
    54960000044.8512064 qam1


    Upstream bonded channels

    Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
    1ATDMA0010
    2ATDMA0000
    3ATDMA0000
    4ATDMA0000
    5ATDMA0060
    • Ninko's avatar
      Ninko
      Tuning in

      Network Log

      Time Priority Description
      13/04/2024 00:44:20criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      12/04/2024 22:57:21noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      01/01/1970 00:01:45criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      12/04/2024 22:51:35noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      12/04/2024 22:37:1Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      10/04/2024 01:54:48criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      10/04/2024 00:08:2ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      06/04/2024 13:01:5criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      06/04/2024 12:08:2ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      03/04/2024 02:18:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      03/04/2024 00:08:2ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      30/03/2024 13:43:7criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      30/03/2024 11:08:2ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      27/03/2024 23:40:19criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      26/03/2024 23:08:2ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      23/03/2024 20:46:27criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      23/03/2024 11:08:2ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      20/03/2024 18:41:16criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      19/03/2024 23:08:2ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      19/03/2024 20:32:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    • Cardiffman282's avatar
      Cardiffman282
      Wise owl

      Stats look good to me (save for channel 1 upstream qam which is too low) and BQM is okay if a little saw-shaped (do you have a Hub 5x?). Check again for local faults on 0800 561 0061 and try a full power down of the hub for a few minutes. 

      • Ninko's avatar
        Ninko
        Tuning in

        Hi @Cardiffman282 

        It's a hub 3, that 1 channel has gone back to 64 for the moment at least. I've tried powering it down for a few minutes.

        Is it normal to have lots of little packet loss episodes?

        Thanks