cancel
Showing results for 
Search instead for 
Did you mean: 

Connection keeps dropping after major outage

nathanlfc1996
Joining in

18th - 21st i was without internet as there was a major outage in the area.

Since it has come back i keep getting loss of internet every 30mins/hour and when i check the router info there are alot of errors. I will post the pages of info for reference.

Cable Modem StatusItem Status Comments
Acquired Downstream Channel(Hz)187000000Locked
Ranged Upstream Channel(Hz)49600000Ranged
Provisioning StateOnlineOperational

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
11870000005.833QAM 2567
21390000005.629QAM 2561
31470000005.60QAM 2562
41550000005.529QAM 2563
51630000005.435QAM 2564
61710000005.534QAM 2565
71790000005.732QAM 2566
81950000006.132QAM 2568
92030000005.933QAM 2569
102110000006.10QAM 25610
112190000006.60Unknown11
122270000006.20Unknown12
13235000000632QAM 25613
142430000005.935QAM 25614
152510000005.932QAM 25615
162590000005.834QAM 25616
172670000005.935QAM 25617
182750000005.935QAM 25618
192830000006.135QAM 25619
202910000006.234QAM 25620
212990000006.135QAM 25621
223070000006.138QAM 25622
233150000006.338QAM 25623
243230000006.337QAM 25624
253310000006.438QAM 25625
263390000006.539QAM 25626
273470000006.437QAM 25627
283550000006.640QAM 25628
293630000006.741QAM 25629
303710000006.841QAM 25630
313790000006.841QAM 25631

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked3396826124236694
2Locked2958987782705354
3Locked010322549816827492
4Locked29971658392226353
5Locked3576549775801180
6Locked341393552882056242
7Locked321516595621243654
8Locked324110502418469
9Locked331487408732706
10Locked04083012440
11Unlocked000
12Unlocked012999164860944
13Locked32848800417759
14Locked35442834171
15Locked3243811271616
16Locked341481797193
17Locked351363944218
18Locked354460529
19Locked35536376871831
20Locked3423110643475109
21Locked3557838987175
22Locked3867221
23Locked3870390
24Locked37201550
25Locked381620520
26Locked39184620
27Locked37590
28Locked40240
29Locked41150
30Locked41230
31Locked41620

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000050.85120QAM 641
14310000050.85120QAM 642
23660000049.85120QAM 643
330100000495120QAM 644
42360000048.35120QAM 645

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0001
3ATDMA0000
4ATDMA0000

Network Log

Time Priority Description
24-06-2023 01:14:21noticeCM-STATUS message sent. Event Type Code: 2; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:14:21noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 2 10 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:14:15noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 3 4 5 6 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:13:58noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 10 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:13:57warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:13:51noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 10 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:13:45warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:13:37noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:13:35warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:13:28noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:13:26noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 10 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:13:19noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 3 4 5 6 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:13:03warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:12:59noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 10 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:12:57noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:12:45warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:12:42noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 10 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:12:13warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:11:37noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 10 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:11:23noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:11:21warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:10:51noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 10 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:10:49noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:10:27warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:10:24noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:10:03noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 2 10 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:10:03warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:09:08noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 10 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:09:08noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:08:55warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:08:20noticeCM-STATUS message sent. Event Type Code: 2; Chan ID: 10 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 01:08:16noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13 REPLIES 13

nathanlfc1996
Joining in

When i get a dropout the router cant even load its own information pages, it glitches out and only gives half the screen.

Could my router be dying?

Kain_W
Forum Team (Retired)
Forum Team (Retired)

Hi nathanlfc1996,

Thanks for your post and welcome to the community.

Many apologies for the issues faced, just from checking our system there doesn't seem to be an area fault currently raised. 

Are you able to post a BQM, to monitor the dropouts?

Regards,

Kain

https://www.thinkbroadband.com/broadband/monitoring/quality/share/eb84c92d1038cf92de79f799c482606c2f8433ab

It is only for like a minute each time, but that is causing major issues with online gaming.

I never had these issues before...

nathanlfc1996
Joining in

This one is a snapshot of today so the data isnt lost, it shows how many disconnects are happening. More in the evenings 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/4753900c7304dd2c6e28813893dc792003315363-24-06-2023

jbrennand
Very Insightful Person
Very Insightful Person

there is a problem on the Hub's downstream connection - channels 10/11/12 are just not even connecting and you have unacceptable PostRS errors on many other channels - this probabl;y needs a Tech visit to investigate


--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

nathanlfc1996
Joining in

Further log updates as this just occured.

24-06-2023 16:00:27noticeREGISTRATION COMPLETE - Waiting for Operational status
24-06-2023 16:00:22warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 16:00:22warningDynamic Range Window violation
24-06-2023 16:00:22warningDynamic Range Window violation
24-06-2023 16:00:21warningRCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 16:00:21warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 16:00:21warningREG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 16:00:21warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 16:00:21warningDynamic Range Window violation
24-06-2023 16:00:16noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:59:53warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:59:51noticeHonoring MDD; IP provisioning mode = IPv4
24-06-2023 15:59:27criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:59:19criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:59:08criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:59:06criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:35noticeCM-STATUS message sent. Event Type Code: 2; Chan ID: 1 2 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:35noticeCM-STATUS message sent. Event Type Code: 1; Chan ID: 2 10 11 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:28warningDBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:26noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 6 8 9 10 13 19 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:25criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:23critical16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:23criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:23criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:23criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:23critical16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:23criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:23critical16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:23criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:23criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:23critical16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-06-2023 15:58:23criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Kain_W
Forum Team (Retired)
Forum Team (Retired)

Thanks for the response there, 

That does appear to be a few error logs recently.

So we can get this investigated I've dropped you a PM.

The message will appear within the envelope icon.

Regards,

Kain

nathanlfc1996
Joining in

When it goes down the router glitches out and cant even display the information screens properly

nathanlfc1996
Joining in

Internet is unusable at the moment, i swear virgin only said it was fixed so they could stop paying compensation