@Carl It has now been 1 full month since any of us have heard from you. Radio silence is absolutely not customer service.

Please update us as soon as possible with any information about what you have done with the info we have all painstakingly provided you with.

@Gmadu1993 Well said.

Been following this thread for 3 weeks, new firmware out as of today. I'm about to try it out. I still have a week or two to return this router.

@TheOnlyEgg good luck man, which router do you have? I'm on the AX50 and I haven't had any firmware updates.

@Gmadu1993 Neither do I... No new firmware for AX50. Best solution for everybody is return it asap, they've abandon us, as it seems, this company is not to be trusted.

@Carl 

Thank you for taking the time to check in with us.

I think what everyone here is trying to say, is that there has been 2 full pages of comments and I formation provided by the community over the last month, and we had zero acknowledgement of it all. The last we had heard from you, you asked us for info to share with the R&D department.

Since then, the community has gathered video evidence demonstrating the problem showing the latency spikes and lag,(see BeemanDev's post on page 6) pictures of the Virtual Desktop performance overlay capturing the latency spike on the network tab, (see bfair31's post on page 6) detailed computer specs from many setups including both AMD and NVIDIA, and detailed exactly which hardware and firmware models of the routers we are all using.

I want to say that I understand you are only 1 person, and not even R&D yourself. I simply want to explain why people are feeling abandoned. After spending over $150 on your AX50 router here in Thailand, it is frustrating to hear that the R&D team "can't replicate" the issue that has literally almost every person in this thread saying the solution is to return the router and buy with a different company.

If the R&D would like to save more of their time and effort for recreating the issue, I can happily make a video for them showing how to use the AC mode with the correct settings to largely eliminate this problem. Perhaps then they can take 5 or 10 new products off the shelf and follow all the evidence we have laid out to recreate the issue, then find a solution for this problem that only affects TPLINK AX branded routers. It is absolutely a shame to know that even a cheap, Chinese brand as Huawei can make a better router without these problems. People bought an AX router. We want to use the AC router.

In the end, I will again say thank you Carl. While it's obvious I'm sure by my tone that I am disappointed in the service the R&D department and TPLINK has given this problem as a whole, I respect that you have many more obligations and responsibilities than this one thread. This thread is now the #1 thread ranked by Kudos and page 2 of overall threads on the TPLINK forum. I simply hope that your R&D team reaches out of their own initiative on this thread to talk to us, and follow the evidence we've laid out for them. It boggles my mind that the R&D can't be bothered to actually read the thread and instead relies entirely on you to bring them the information. No one here has been contacted by the R&D team to support them in solving this issue, which I know many of us would be happy to do. 

@Carl @Gmadu1993 

"Especially if our R and D teams cannot replicate the issues."

Doubt. 

@Carl 

Thank you for your understanding Carl. I think I can speak for everyone when I say we really look forward to the R & D team joining the thread so that we can speak with them directly!

Gonna pop in here and say I have an Archer Ax1800 with a Quest 2 and I'm using 80mhz width with AX mode only, 5ghz band only and no other devices connected with all other settings perfect and I get murderous microstutters. 

Its not hard to reproduce it. Your team is just too lazy. 

This router is going back to the store. I only have one week before I can no longer return it.