Internet dropping at random intervals

[SteveHal]

Hi,

I have Comcast coming out tomorrow and want to be prepared. I have  C6300 and my service drops out at regular intervals. It goes to a crawl! It will then repair itself and get a full 170MB connection. When it fails the tracert drops between routerlogin.net and the first comcast node, and the rest after that... with about 50% *'s.

When I log into routerlogin.net getting to some of the tabs do not work, or it takes VERY long. I just get the spinning loading circle. I can get to some pages quickly, and others just stay spinning, and they may eventually load.

Do you all have any suggestions based on this? Could the modem be failing? Anything I should do to prevent Comcast from charging me tomorrow? If they say my modem is bad they may charge me for the visit. If you think the modem is bad I will RMA this one and cancel the visit tomorrow. I did not do a factory reset, but I have kept most everything default.

Here are the logs.

Apr 17 2019 07:57:49	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Apr 15 2019 10:02:06	Critical (3)	No Ranging Response received - T3 time-out
Apr 15 2019 07:21:59	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Apr 14 2019 21:05:36	Critical (3)	No Ranging Response received - T3 time-out
Apr 14 2019 20:19:31	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Apr 13 2019 14:19:29	Critical (3)	No Ranging Response received - T3 time-out
Apr 13 2019 03:23:02	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out
Apr 13 2019 03:20:39	Error (4)	CheckDmgProvision dmg_provisioning process is not running, need to restart.
Apr 12 2019 19:54:54	Critical (3)	No Ranging Response received - T3 time-out
Apr 10 2019 22:44:27	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out
Apr 10 2019 22:42:04	Error (4)	CheckDmgProvision dmg_provisioning process is not running, need to restart.
Apr 08 2019 03:34:19	Warning (5)	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Apr 08 2019 03:32:02	Error (4)	CheckDmgProvision dmg_provisioning process is not running, need to restart.
Apr 08 2019 03:31:56	Critical (3)	No Ranging Response received - T3 time-out
Apr 08 2019 03:31:32	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Apr 08 2019 03:31:32	Critical (3)	Ranging Request Retries exhausted
Apr 08 2019 03:31:32	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Apr 08 2019 03:31:31	Critical (3)	Ranging Request Retries exhausted
Apr 08 2019 03:25:07	Critical (3)	No Ranging Response received - T3 time-out
Apr 08 2019 03:24:43	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Apr 08 2019 03:24:43	Critical (3)	Ranging Request Retries exhausted
Apr 08 2019 03:24:43	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Apr 08 2019 03:24:43	Critical (3)	Ranging Request Retries exhausted
Apr 08 2019 03:18:18	Critical (3)	No Ranging Response received - T3 time-out
Apr 08 2019 03:17:54	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Apr 08 2019 03:17:54	Critical (3)	Ranging Request Retries exhausted
Apr 08 2019 03:17:54	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Apr 08 2019 03:17:54	Critical (3)	Ranging Request Retries exhausted
Apr 08 2019 03:11:30	Critical (3)	No Ranging Response received - T3 time-out
Apr 08 2019 03:11:06	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Apr 08 2019 03:11:06	Critical (3)	Ranging Request Retries exhausted
Apr 08 2019 03:11:06	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Apr 08 2019 03:11:06	Critical (3)	Ranging Request Retries exhausted
Apr 08 2019 03:04:41	Critical (3)	No Ranging Response received - T3 time-out
Apr 08 2019 03:04:17	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Apr 08 2019 03:04:17	Critical (3)	Ranging Request Retries exhausted
Apr 08 2019 02:57:53	Critical (3)	No Ranging Response received - T3 time-out
Apr 08 2019 02:57:29	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Apr 08 2019 02:57:29	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted

I registered my modem today, but Netgear said I had no support. It should start at registration if you are in the warranty period. I got the modem about 4 months ago. So I need to post here because support expired.

[additude]

I had this issue before however with a different ISP/MODEM/ROUTER setup and it ended up being a bad/corroded splitter. Replaced the splitter and problem dissapeared.

Once on a DSL connection I had same issue, the problem was outside in a phone line junction box. We took the incomming pairs and swapped them to an unused jumper pair and it worked just fine after that.

Oxidation and Corosion cause db losses and that messes up a lot of things.

You can try swapping in a new modem or take this one to a friends house that has the same service and verify it is good or bad.

Thats the best way to verify the modem.....

[FURRYe38]

Also contact the ISP and have them check the signal up to the modem. 

[plemans]

A couple things you could try doing before the tech comes to hopefully prevent a charge. 

1. Move the modem to the coax where it is coming into the house and directly connect there. This removes possible splitters, bad wires, amplifiers, or other interference that could be causing the issue.

2. Check your power levels within the modem configuration page once you've done this.  Good Downstream power levels are within -7 to +7 dBmV. Good Upstream power levels are within 38-48 dBmV.  If you're within these specs, thats good. it doesn't mean the connection coming into the house is perfect as it just takes a snapshot of whats going on.  I

3. Do a full reset of the router and upon re-install, just run your basic wifi/routing features to reduce the chance of them saying user error is causing the issue.

If the fault is within the house is when they charge you. so if you can reduce the likelyhood of it being within the house, it might save you some $. Plus if it fixes the problem, it tells you its something like wiring/connector causing the issue thats within your house. If it doesn't, its either the drop from comcast or the combo device and you're kind of gambling on it being the drop coming in. 

[SteveHal]

Thanks for the replies!

I moved into this place about 4 months ago... and the line to the box (the orange type wire that goes underground) was replaced about 3 weeks prior to me moving in while the previous owners were there. What is odd is that the home is only 5 years old. Maybe they had similar issues.

Some may not notice, but I need to do tasks that require a pretty good connection...

I will check the splitter(s). The snr ratios appear to be within limits. I just do not quite understand how it would be perfect connectivity and then just drop. If comcast comes and says that their connections are correct and splitters replaced then I guess replacing the modem would be the only other option. It is about 1 hour connected at full speed, all the sudden 5 minutes down or reduced, 1 hour connected, 5 minutes down or reduced, repeat...