4 days old Archer C9, no iOS 14 devices, started rebooting yesterday.

Shall I throw it out or is there a hope for fix from TP-Link? 

BTW - WPA3 would be 'nice to have' with an FW update.

@elmiko 

You can try TPLink support. They were fairly responsive to me when I opened a case but they never did actually come up with a fix because the iOS 14.1 update seemed to resolve. 

They do have a debugging firmware they can send out that gives them more info than the system logs.

@stevem999 Just wrote to them. Waiting for feedback.

@Applebe I'm using AES by default. No luck on my side.

One more.

Error in log comes from LED Control. I turned it off. But after another self-reboot it is turned on again.

@Applebe 

FW downgrade also didn't help...

I had to disconnect it because i can't work and kids can't learn.

Piece of crap. Unfortunately.

Sadly after 4 or 5 days of stable connection, my router has started rebooting again. Twice today so far. Going to raise with TP Link again.

@stevem999 

mine started rebooting about a week ago as well. Right around the time where my desktop PC auto updated to a new insider build of windows 10 Pro (slow ring). So maybe something with that? 
 

I tried updating two of the iPhones to the latest 14.2 but left my personal phone on 13.2.2 because it's jailbroken. 
 

on a side note, I'm fairly knowledgeable of networking, having passed most of the MCSE tests before choosing todo other things, and I can't think of any examples of connected devices causing something like a router reboot. In fact I can't think of how it could even be possible aside from a command being sent. 

I have the same problems. Unsure when it started, but at least a couple of weeks. We have a few iOS devices, but none that has been upgraded to iOS 14.

Since we are working from home, with a lot of meetings, this is just not acceptable. Is there any solution coming? Otherwise we will have to return the router to the seller. 

So, update after more emails from TP-Link support. I have had by debug firmware installed for a couple of days and got some reboots yesterday in particular, so ran the debug logs and sent them over to TPLink.

They have advised that they can see some errors with certain devices joining the network which causes some negotiation errors and a 'null pointer' is created. They also believe the NAT Boost function is involved and asked me to disable it in the firmware. They are working on a new beta and say they will send it to me in a few days.

Let's see what happens.