That's not good. What brand of modem/router are you using? And just to clarify, is it a combined unit, or do you have a separate modem/router?

Just one basic thing: are there any issues with the outlet into which the modem is plugged? If not, check to make sure the AC power cord into the modem is secure.

If that all checks out, it might be time to get a new modem. If you do need to get one, consider whether you can take advantage of Xfinity/Comcast's highspeed services. I switched to a DOCSIS 3.1 cable modem rated for Xfinity/Comcast and we are getting BLAZINGLY fast speeds for about what we were paying before we switched.

No physical issues with the power that I can see. I did buy this one several years ago to take advantage of those higher speeds I was paying for and it made a big difference at the time.

Check the breaker box....we had an issue in our new house where the Xfinity cable tv box kept going on and off....I called Xfinity, but they couldn't figure it out. I then called an electrician, and it turned out that a circuit breaker in the panel needed to be replaced.

If that's not it, it is absolutely not normal for a modem to do this.

Can I suggest you call Xfinity and see if they will help. They probably won't since it's your own equipment. However, ask them what speeds you can upgrade to and what kind of equipment you need. I was PLEASANTLY surprised at the massive increases of speed we got (which also helps with multiple users all sharing the same bandwidth) plus HBOMax for pretty much the same price I was paying for speeds 67% below what they were offering. I don't know if you need it (we did), and I had to buy a DOCSIS 3.1 modem for around $159 to take advantage. It was WELL WORTH, since we have several video conferences for work and school going on at our home.

I've got it in GMT time, so that accounts for time disparity below. What the heck is notify_rc_start_webs_update, though? Is someone remotely causing a firmware update or something? That's kind of like what the behaviour appears to suggest...

Jun 3 22:36:23 rc_service: ntp 492:notify_rc restart_diskmon
Jun 3 22:36:23 disk_monitor: Finish
Jun 3 22:36:23 disk monitor: be idle
Jun 3 22:36:24 dhcp client: bound xxx.x.x.x/255.255.252.0 via x.1x.x.1 for 4907 seconds.
Jun 3 22:36:41 crond[350]: time disparity of 1621051 minutes detected
Jun 3 22:36:43 dnsmasq-dhcp[348]: DHCPDISCOVER(br0) 00:0e b:44:3b:a8
Jun 3 22:36:43 dnsmasq-dhcp[348]: DHCPOFFER(br0) 192.168.0.45 00:0e b:44:3b:a8
Jun 3 22:36:43 dnsmasq-dhcp[348]: DHCPREQUEST(br0) 192.168.0.45 00:0e b:44:3b:a8
Jun 3 22:36:43 dnsmasq-dhcp[348]: DHCPACK(br0) 192.168.0.45 00:0e b:44:3b:a8 nazgul
Jun 3 22:40:25 rc_service: httpd 351:notify_rc start_webs_update

I suppose that could be causing it somehow.

Lots of information on the reboot loop.

The DHCP reference is one that I have very little familiarity with....I do know that I have had huge problems with a Google VOIP phone causing DHCP problems because of a static IP address that I assigned to the phone device. I haven't quite cured the issue yet.

But again, it's been years.

I'm beginning to think it's the old XP system because of the timing. I've shut it off for now and will see if the problem goes away.

My Google phone device worked and then all of a sudden it didn't....it caused a LOT of issues with the internet, and I faced the wrath of an angry spouse and kids.

Just for kicks, I reconnected the device after I got the new high-speed modem, and boom: it caused problems.

If you have time, disconnect it and reboot everything (including your modem/router and devices)....because I have kids taking online exams until next week, I'm not going to troubleshoot the Google phone device, but it was CLEARLY causing severe problems.

All I ever get on that Vonage line are spam/scam calls anyway. I should really get rid of it in any case, but I've had that number for 30 years and for some reason feel reluctant to part with it. I know it's s not rational. It's a first generation adapter, so it's certainly plausible enough.

Thanks!

I had no computer or phone but had TV. Unplugged router and modem, took out the battery, etc. Nothing worked. I re-did it at 1:30 AM and it finally started coming back up. This is the first time this has happened in 3 years.