CR1000A router disabling 2.4Ghz wifi band after a few minutes

[magent]

Same here. 3.2.0.7

[Chrisl2022]

Give your routers a reboot to see if they have the new firmware load on boot up. 

[top83banana]

Make sure your IoT Network has a same Wi-Fi name as your Primary Network.

[Chrisl2022]

I switched back to using the 2.4 GHz wireless last night and the 2.4 GHz radio disappeared again this morning. The new firmware did not resolve the issue . I am back to using my separate access points for 2.4. 

[Chrisl2022]

Here's what I have done and it is working okay for over 4 days now:

I don't use the SON (self organizing network) feature. 

Renamed the regular 2.4GHz network name to something else so no one connects to it. 

Used the IOT network and renamed it to what I usually use for my 2.4GHz Network with the same passcode. 

Devices have been connecting through the IOT network for over 4 days and the radio has not failed yet. 

I'll just leave like this until we hear news of this issue being fixed permanently. 

Chris

[aPastafarian]

• I really hope this works for you but I have tried everything you have and it hasn't worked for me.  The radio failure is inconsistent for me, I can go 4-5 days up, then have it go down every hour or less .  I also don't know how Verizon is working the new firmware rollout, it's been over 3 week since I saw the first report of 3.2.0.8, I'm still on 3.2.0.7.  There can't be that many out there for this slow a roll out?   I'm thinking about forcing another swap, if just to annoy them  . In pretty sure it won't help one bit and that this router is little more than e-waste. 

[Kohl-Kurt]

Same problem for me with a CR-1000A router.  Firmware version is 3.2.0.7

[aPastafarian]

This router is junk, plain and simple and I've sort of given up on it ever working as advertised.  I've had 3 now, and all have identical 2.4Ghz disconnect issues, none have upgraded to 3.2.0.8 and I'm convinced it wouldn't matter anyway. I shouldn't be too bitter, I was given the router n/c after downgrading my $120/m cable/100mb service to $44/m 1GB and I see many reporting they pay significantly more.  My choice is to continue with my CR1000/Asus CT8 combo with acceptable 5Ghz and ethernet speed and less than stellar 2.4Ghz speed with the added complication that if the CR1000 reboots, everything connects to the Asus at 2.4Ghz and won't connect at 5Ghz till I reboot the Asus too, or buy a new functional router adding even more e-waste to the world.  My experience leaves me wondering, are most of the people using this router just accepting that it can't stay connected via 2.4 GHz and reboot it constantly?  Do they just not have any 2.4 GHz devices (I have 30+ mostly IOT)?  Or have they all like me, given up and moved on to another solution?

[Chitchat7295]

I got a replacement cr1000a (still rev A hardware) but upgraded to 3.2.0.8 Firmware.  Between April 22nd and May 5th, I didn't run into this issue once and thought I was in the clear (though, I did have one mid-week "Kernel Panic" that reset my router in the middle of a work meeting 😡).

Then, on May 6th, with nothing different happening on my network than any 'normal day', the issue popped up again.  So, for those hoping it was fixed in the latest Firmware, you can give up on that route.  I use the 2.4Ghz Wifi exclusively for the IoT network.  That mean, when 2.4Ghz goes out, all my connected devices disconnect .  

Next thing to evaluate is whether this is a HW rev issue.  Is anyone that's having this issue on rev B hardware??

[nycuser2]

Have people solved this by getting their own router? I think that's the only option at this point apart from switching to another provider. I just got a new router, separated the networks by band, only connected Nest and smart devices to IoT network, and the issue is happening even more frequently. Been having this issue for months as well.