Forum Discussion

NoDropouts's avatar
NoDropouts
Tuning in
2 years ago
Solved

Millisecond Internet Dropouts - 6 Months+

Over the last 6 months or so we've had an issue of micro dropouts, now this is not enough to cause disconnection from devices/wifi but it seems some programs are more sensitive than others, and several of those being programs used for work. VPNs, RDS, VDI's..

I've replaced several parts in the machines & cabling we use in the house. 

I am out of ideas here and this is becoming very frustrating to deal with. 

There is no rhyme or reason to these it seems and I cannot replicate them, some days there are not many others it's every 30 mins.

Last 7 days of monitor results are below. The small red packet loss pins would indicate my issue I believe. 

Monday 5th

Tuesday 6th

Wednesday 7th

Thursday 8th

Friday 9th

Saturday 10th

Sunday 11th

Monday 12th

Network Log

Time Priority Description

12-02-2024 01:11:26noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-02-2024 01:06:23noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-02-2024 13:11:37noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-02-2024 13:06:34noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-02-2024 01:11:29noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-02-2024 01:06:25noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-02-2024 22:44:47noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-02-2024 22:39:44noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-02-2024 13:11:36noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-02-2024 13:06:33noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-02-2024 07:03:42criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-02-2024 07:03:42critical16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-02-2024 07:02:34criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-02-2024 07:00:00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-02-2024 13:11:28noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-02-2024 13:06:25noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-02-2024 03:44:41errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 15:13:07noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 15:08:04noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 19:53:18noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 19:48:15noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-02-2024 15:44:40errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-02-2024 18:52:01noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-02-2024 18:46:58noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2024 19:37:23noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2024 19:32:20noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2024 19:06:24noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2024 19:01:21noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2024 16:53:15noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2024 16:48:12noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2024 03:44:38errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2024 02:08:50criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

  • Adduxi's avatar
    Adduxi
    2 years ago

    Terrible stats. Far too many T3 errors and PostRS errors.  Possible noise ingress and the Upstream is flapping between channels? 

6 Replies

  • NoDropouts's avatar
    NoDropouts
    Tuning in
    2 years ago

    3.0 Upstream channels

    Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
    04960000042.85120QAM 641
    14310000042.85120QAM 642
    23660000043.55120QAM 643
    330100000435120QAM 644
    423600000435120QAM 645

    3.0 Upstream channels

    Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
    0ATDMA0380
    1ATDMA03410
    2ATDMA03230
    3ATDMA03390
    4ATDMA03451

    3.1 Upstream channels

    Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
    1410.438.02KQAM 256

    3.1 Upstream channels

    Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
    14OFDMA2087400000070
  • NoDropouts's avatar
    NoDropouts
    Tuning in
    2 years ago

    3.0 Downstream channels

    Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
    13310000009.342QAM 25625
    21390000009.842QAM 2561
    31470000009.942QAM 2562
    41550000001042QAM 2563
    51630000001042QAM 2564
    61710000009.942QAM 2565
    71790000009.742QAM 2566
    81870000009.742QAM 2567
    91950000009.942QAM 2568
    102030000009.742QAM 2569
    112110000001042QAM 25610
    122190000009.742QAM 25611
    132270000009.642QAM 25612
    142350000009.642QAM 25613
    152430000009.542QAM 25614
    162510000009.142QAM 25615
    172590000008.542QAM 25616
    182670000008.742QAM 25617
    19275000000942QAM 25618
    202830000009.142QAM 25619
    212910000009.442QAM 25620
    222990000009.342QAM 25621
    233070000009.542QAM 25622
    243150000009.542QAM 25623
    253230000009.442QAM 25624
    263390000009.342QAM 25626
    273470000009.442QAM 25627
    283550000009.642QAM 25628
    293630000009.642QAM 25629
    303710000009.442QAM 25630
    313790000009.142QAM 25631

    3.0 Downstream channels

    Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
    1Locked421696
    2Locked424771528
    3Locked4224689839
    4Locked423162511
    5Locked423461268
    6Locked4212734654
    7Locked4211515535
    8Locked423117247
    9Locked42737112
    10Locked42834204
    11Locked42824347
    12Locked42778364
    13Locked42637148
    14Locked4212441
    15Locked4211446
    16Locked4221434
    17Locked4233338
    18Locked4270856
    19Locked4255326
    20Locked4217526
    21Locked4214719
    22Locked4212610
    23Locked4223013
    24Locked4213511
    25Locked421090
    26Locked423861
    27Locked4262437
    28Locked42691100
    29Locked4262654
    30Locked424547
    31Locked422671

    3.1 Downstream channels

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

    3.1 Downstream channels

    Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
    37Locked439.034419094652
  • Adduxi's avatar
    Adduxi
    Very Insightful Person
    2 years ago

    Terrible stats. Far too many T3 errors and PostRS errors.  Possible noise ingress and the Upstream is flapping between channels? 

    • NoDropouts's avatar
      NoDropouts
      Tuning in
      2 years ago

      Interesting, I forget what it is called but about 4-5 years ago an engineer had come and fit something to the coax cable from the wall to the router as we were causing noise for our neighbours apparently. 

      Is there anything I can do from here or will this all be on Virgin to look at?

      • Adduxi's avatar
        Adduxi
        Very Insightful Person
        2 years ago

        VM will need to sort this out.  All you can do is make sure the connections are at least "finger tight" as loose connections can cause noise ingress.