@sermad I am having this same exact issue with a brand new Archer A10 I installed 3 days ago. Is there a fix?

thanks

@Kevin_Z I am having this same exact issue. How can I proceed getting assistance?

@JasonB89 

Hi, 

In my case, I dealt with TP-Link's technical support (which was superb) and after debugging on their part, the issue turned out to be a bug in the latest firmware specific to the A10 model (although not sure if it affects all A10s).

The technical support seemed aware of the issue and actively working on a fix, and I was told that the solution would eventually take the form of a new firmware update at some time down the road.

At the time, the only solution that did not involve a firmware update seemed to be a replacement of the router by a different model (not another A10). In my case, I upgraded to TP-Link's C4000 model and the issue has completely disappeared.

That being said, my case is a few months old and maybe there are other solutions that have been developped since then. I would recomment that you reach out to technical support so that they can confirm the issue and propose solutions. The process took some time in my case, but they were really helpful in the end.

Good luck!

@sermad thanks, I will reach out and see what can be done!