Forum Discussion

alphaomega16's avatar
alphaomega16
Up to speed
2 years ago

Constant small packet loss dips in SS2

For the past week ive been getting persistent little spikes in packet loss and I am noticing it ingame.

Is there currently an issue in my area, no point in calling up as I never get anywhere and now the tech support has business hours so if my internet went completely off after 5pm there is nobody to call.

64 Replies

  • You're very welcome alphaomega16 and glad that we could get this resolved for you. If you get the chance, please let us know how the visit goes. 

    Kind Regards,

    Steven_L

  • LOL 4/5 are now out of whack

    Network status

     

    Router status

    Mon 13/01/2025
    21:05:45
    6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    20:28:22
    6CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    16:59:25
    6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    16:54:54
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    16:32:19
    6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    16:18:48
    6CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    14:42:00
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    14:39:15
    6CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    08:25:05
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    08:00:25
    6CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    07:11:32
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    07:10:24
    6CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    06:25:44
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    06:21:03
    6CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    03:26:31
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    03:10:50
    5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu 01/01/1970
    00:01:21
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 13/01/2025
    02:25:58
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
  • Engineer not long left, signal seemed fine outside so replaced the inside box thing on the wall (old one still had telewest logo on it) but upon booting up the QAM issue remains as does the original issue.

    Live graph to view

    https://www.thinkbroadband.com/broadband/monitoring/quality/share/49e55d6cab21bc6dd4177463ad074fde33e2843c

    But it didn't take long for the issue to be visible again

    He is going to speak with some other people to see if anything else may be going on and as last resort try changing the hub if all else fails as it could be the hub that is the issue.

  • 3.0 Downstream channels

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

    142430000006.19999740.366287QAM25614
    11390000007.00000040.366287QAM2561
    31550000007.30000340.366287QAM2563
    41630000007.00000040.366287QAM2564
    51710000006.30000340.366287QAM2565
    61790000006.09999840.366287QAM2566
    71870000006.09999840.946209QAM2567
    81950000006.00000040.946209QAM2568
    92030000005.69999740.366287QAM2569
    102110000005.59999840.366287QAM25610
    112190000005.50000040.946209QAM25611
    122270000005.90000240.366287QAM25612
    132350000006.09999840.366287QAM25613
    152510000006.30000340.366287QAM25615
    162590000006.40000240.366287QAM25616
    172670000005.90000240.366287QAM25617
    182750000004.90000240.366287QAM25618
    192830000005.19999740.366287QAM25619
    202910000005.50000040.946209QAM25620
    212990000005.69999740.366287QAM25621
    223070000005.50000040.366287QAM25622
    233150000005.00000040.366287QAM25623
    243230000004.50000040.366287QAM25624
    253310000004.90000240.946209QAM25625
    263390000004.90000240.366287QAM25626
    273470000004.69999740.366287QAM25627
    283550000004.80000340.366287QAM25628
    293630000004.50000040.366287QAM25629
    303710000004.69999740.946209QAM25630
    313790000004.59999840.366287QAM25631
    323870000004.50000040.366287QAM25632



    3.0 Downstream channels

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

    14Locked40.36628700
    1Locked40.36628700
    3Locked40.36628700
    4Locked40.36628700
    5Locked40.36628700
    6Locked40.36628700
    7Locked40.94620900
    8Locked40.94620900
    9Locked40.36628700
    10Locked40.36628700
    11Locked40.94620900
    12Locked40.36628700
    13Locked40.36628700
    15Locked40.36628700
    16Locked40.36628700
    17Locked40.36628700
    18Locked40.36628700
    19Locked40.36628700
    20Locked40.94620900
    21Locked40.36628700
    22Locked40.36628700
    23Locked40.36628700
    24Locked40.36628700
    25Locked40.94620900
    26Locked40.36628700
    27Locked40.36628700
    28Locked40.36628700
    29Locked40.36628700
    30Locked40.94620900
    31Locked40.36628700
    32Locked40.36628700



    3.1 Downstream channels

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


    3.1 Downstream channels

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

     

    Now ALL upstream channels are not on QAM64

     

  • Just wanted to update, looking a LOT better now in regards to the constant red dips at top and upstream channels for the moment are all on QAM64 which I have not seen in quite a while.

    All it took was someone to make someone look at something other than my end.

    EDIT

    Not sure why but these new forums can't click for bigger image any more and can't drag image to open in new window.

    • Matthew_ML's avatar
      Matthew_ML
      Icon for Forum Team rankForum Team

      Glad to hear this is looking better for you.

      Please do keep us update is anything changes.