Question Constant Disconnecting/Connecting

[tidusx99]

Ive had Suddenlink/Optimum for 11 months now and have had this issue non stop to the point where I've lost close to $150K in business income due to these issues that are nonstop. Out of these 11, 3 of which were Ground Survey/SRO and recently was told the node is deteriorating and no project/plan to address it as of now.



Ive seen a variety of issues in the troubleshooter ranging from Gateway is not available; windows cant communicate with the device or resource (primary DNS); doesnt have a valid IP Configuration and so no.



I get these issues both with hardwire ethernet and with WiFi.



I have changed my DNS to both automated through the company, setting to Google's and Cloudflare's Primary/Secondary and still can never keep the connection despite that.



Router: TP Link Archer A8

Modem: Motorola MB7621



I have had 11 techs come out and "adjust" everything and never find any issues, but aside from that consistently keep having these issues.



Time Priority Description

Mon Oct 03 18:02:02 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:06:21 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:06:22 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:07:22 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:07:22 2022 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:07:22 2022 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:10:34 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:10:42 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:14:34 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:14:34 2022 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:14:34 2022 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:14:58 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:15:02 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:18:59 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:19:22 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:20:11 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:20:29 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:22:36 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:23:42 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:25:24 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:25:24 2022 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:25:24 2022 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:27:48 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:28:02 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:32:12 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:32:22 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:34:36 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:34:36 2022 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:34:36 2022 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:36:36 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:36:42 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;

Mon Oct 03 18:36:43 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;





Mon Oct 03 18:50:13 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 18:50:13 2022 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 18:50:13 2022 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 18:53:49 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 18:54:02 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 18:58:14 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 18:58:22 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:01:26 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:01:26 2022 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:01:26 2022 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:02:38 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:02:42 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:07:27 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:07:51 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:09:03 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:09:03 2022 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:09:03 2022 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:11:52 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:12:11 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:16:16 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:16:31 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:16:40 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:16:40 2022 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:16:40 2022 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:20:40 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:20:51 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:22:02 2022 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:25:11 2022 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = APM
Time Not Established Critical (3) DHCP failed - RS sent, no RA received;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.0;CM-VER=3.0;
Mon Oct 03 19:26:27 2022 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 03 19:26:28 2022 Notice (6) TLV-11 - unrecognized OID;CM-MAC=00:40:36:7d:c8:70;CMTS-MAC=00:01:5c:77:50:6d;CM-QOS=1.1;CM-VER=3.0;






Startup Sequence

Startup Step Status Comment





Acquire Downstream Channel 747000000 Hz Locked



Upstream Connection OK Operational



Boot State OK Operational





Configuration File OK ^1/60010EA4/TYPE=RES/COS=189/IP=2



Security Enabled BPI+







Connection Status

System Up Time 0 days 00h:01m:47s



Network Access Allowed







Downstream Bonded Channels



Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected

1 Locked QAM256 32 747.0 10.3 41.4 0 0

2 Locked QAM256 1 561.0 9.8 42.5 0 0

3 Locked QAM256 2 567.0 9.4 42.2 0 0

4 Locked QAM256 3 573.0 9.3 42.1 0 0

5 Locked QAM256 4 579.0 9.4 42.2 0 0

6 Locked QAM256 5 585.0 9.6 42.2 0 0

7 Locked QAM256 6 591.0 10.0 42.5 0 0

8 Locked QAM256 7 597.0 9.5 42.1 0 0

9 Locked QAM256 8 603.0 8.6 41.7 0 0

10 Locked QAM256 9 609.0 7.2 40.8 0 0

11 Locked QAM256 10 615.0 6.6 39.8 0 0

12 Locked QAM256 11 621.0 7.2 40.6 0 0

13 Locked QAM256 12 627.0 8.6 41.5 0 0

14 Locked QAM256 13 633.0 8.4 41.5 0 0

15 Locked QAM256 14 639.0 7.9 41.0 0 0

16 Locked QAM256 15 645.0 8.3 41.1 0 0

17 Locked QAM256 16 651.0 9.1 43.0 0 0

18 Locked QAM256 19 669.0 8.2 42.8 0 0

19 Locked QAM256 20 675.0 8.5 43.0 0 0

20 Locked QAM256 25 705.0 9.8 42.8 0 0

21 Locked QAM256 26 711.0 10.2 43.0 0 0

22 Locked QAM256 28 723.0 11.1 43.0 0 0

23 Locked QAM256 30 735.0 9.8 43.0 0 0

24 Locked QAM256 31 741.0 10.3 42.6 0 0

Total 0 0





Upstream Bonded Channels



Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)

1 Locked ATDMA 28 2560 19.9 47.8

2 Locked ATDMA 25 5120 35.5 49.5

3 Locked ATDMA 26 5120 28.7 49.3

4 Locked ATDMA 27 2560 23.5 48.3

5 Not Locked Unknown 0 0 0 0.0

6 Not Locked Unknown 0 0 0 0.0

7 Not Locked Unknown 0 0 0 0.0

8 Not Locked Unknown 0 0 0 0.0

 

[kanewolf]

Maybe post screen shots to imgur for your modem status. The format you posted is unreadable.

 

[tidusx99]

Maybe post screen shots to imgur for your modem status. The format you posted is unreadable.

Apologies. There we go. Fixed it up just originally copy/pasted direct from the modem admin panel.

 

[kanewolf]

Apologies. There we go. Fixed it up just originally copy/pasted direct from the modem admin panel.

Your modem statistics don't look bad. You have no corrected or uncorrected errors. That may be a factor of how long since you booted.
The power and signal to noise is good. Could be a little overdriven. Many of your signal levels are above +7dB. Some modems optimum are -7 to +7dBm but some modems are up to +14dBm.

I guess the next step would be to have you better describe the issue. What is constantly "disconnecting / reconnecting" ? What do the LEDs on the modem show when this happens?
What do the router logs show? What do the router LEDs look like ?
I think you need to look at this more holistically.

 

[tidusx99]

Router just shows everything but the actual connection signal which will display red/orange showing no signal.

Modem lights are all lit with green/blue/blue/green and blinking green for active signal.

I basically cannot stay online, constant connection/disconnections every few minutes of actual internet connection and it happens nonstop and has for months.

Nothing will connect as well when this happens, wireless connections to phone/streaming services for TV/surface/desktop, just everything is negated from going to any website, launching any internet required program.

If I'm not mistaken, on my modem its -10/+10 from what I recall researching mostly, and have had those adjusted plenty of times (originally were up to +45 from the get go).

 

[kanewolf]

Router just shows everything but the actual connection signal which will display red/orange showing no signal.

Modem lights are all lit with green/blue/blue/green and blinking green for active signal.

I basically cannot stay online, constant connection/disconnections every few minutes of actual internet connection and it happens nonstop and has for months.

Nothing will connect as well when this happens, wireless connections to phone/streaming services for TV/surface/desktop, just everything is negated from going to any website, launching any internet required program.

If I'm not mistaken, on my modem its -10/+10 from what I recall researching mostly, and have had those adjusted plenty of times (originally were up to +45 from the get go).

What assistance do you believe a forum can provide?
Tell you "Yep, you got a problem." ... We can't fix anything, if it is an ISP problem.
Your only option may be to find an alternate ISP provider. But if you have lost the amount of revenue you claim in your original post, you should have had a backup internet service from the beginning.

 

[bill001g]

Generally a router will only detect the loss of its IP address. The router itself does not send any real traffic so if you would get packet loss someplace in the network that the router would need see.
You also would think that the modem would show much worse errors if it was going completely down.

The unicast maintenance messages are basically similar to a ping message but using docsis messaging. You will see some here and there on all connections. It appears you have a lot in very short periods of time. Although this can be your issue it should not cause the router to go down.
Do the messages in the router always happen at the same time you have issues.

Only the ISP can really say why. It can be because of issues with the connection to your house but as kanewolf stated everything looks pretty good. This means this problem is farther into the network.

Although I doubt it will show anything different try to plug your pc directly into the modem to test . You will likely have to reboot the modem when you plug your pc in and then again when you move back to the router. Cable modems tend to lock to the first mac address they see.
Maybe it is some issue with the router or a cable but this test is more so you can prove to the ISP it is not your router causing it.

 

[tidusx99]

What assistance do you believe a forum can provide?
Tell you "Yep, you got a problem." ... We can't fix anything, if it is an ISP problem.
Your only option may be to find an alternate ISP provider. But if you have lost the amount of revenue you claim in your original post, you should have had a backup internet service from the beginning.

Ive had to result to using my mobile hotspot. September alone was 980 gigs of data due to the contractual downloads/uploads and various files/videos/marketing materials.

the ISP has told me “nothings wrong on their end” and to contact Motorola to fix the issue (which makes no sense since how would they do anything if there is no service connection).

 

[tidusx99]

Generally a router will only detect the loss of its IP address. The router itself does not send any real traffic so if you would get packet loss someplace in the network that the router would need see.
You also would think that the modem would show much worse errors if it was going completely down.

The unicast maintenance messages are basically similar to a ping message but using docsis messaging. You will see some here and there on all connections. It appears you have a lot in very short periods of time. Although this can be your issue it should not cause the router to go down.
Do the messages in the router always happen at the same time you have issues.

Only the ISP can really say why. It can be because of issues with the connection to your house but as kanewolf stated everything looks pretty good. This means this problem is farther into the network.

Although I doubt it will show anything different try to plug your pc directly into the modem to test . You will likely have to reboot the modem when you plug your pc in and then again when you move back to the router. Cable modems tend to lock to the first mac address they see.
Maybe it is some issue with the router or a cable but this test is more so you can prove to the ISP it is not your router causing it.

when I connect straight into the modem I still get no connections. I tend to see no DNS (whether I use automatic to the ISP or change manually to googles or cloudflares). Or configuration is correct however no default gateway.

with the flip going to router wireless I’ll get no valid ip configured (which is inverted from modem having a configuration but no gateway/dns).

the connection itself is up for a matter of a minute or two then it cuts out reconnects and recycles this pattern.

tried a few things ranging from flushing dns, releasing/renewing IPs, even ran a few net 25 pings and packet losses which I’d see 20K+ ms/packet loss responses for the average across 25.

kind of at a loss all around and using my hot spot on a repetitive basis like how I do with the throttling is exhausting.

sadly there isn’t any other ISP in the area due to a city contract they had for 10 years and just didn’t renew it finally opening up Blue Peak/Dobson Fiber to lay the framework but still months out.

 

[bill001g]

Although unlikely it could be the modem is defective and causing this. This is the case where if you were leasing the modem and the ISP tried to make that claim you ask them to bring you a new one.

I am unclear what you mean configuration is correct but no gateway. If you do IPCONFIG /all when connected directly to the modem do you have a IP address but no gateway. Not sure how that can happen. I could see if you lose both the IP and the gateway.

When you do ping make sure you ping by IP address...ie 8.8.8.8