@Joseph-TP 

Hello,

I’ve noticed the issue mainly on the 5 GHz band.
The affected Wi-Fi 6 clients are POCO F3, POCO F6, and POCO F7, which are relatively modern devices.

I’m not sure about the 2.4 GHz band — I only have a printer connected there, and it seems to be working fine.

The distance between the router and the devices is appropriate, and there shouldn’t be any interference issues.

Sometimes the connection appears to freeze or get stuck. I’ve confirmed this by testing with a direct Ethernet connection, and the issue still appears intermittently.

It seems that for firmware versions earlier than 1.0.13, the performance might actually be better.

Thanks for your follow-up and support.

  @Joseph-TP

Yes, the connectivity was stable before the firmware update — I didn’t experience these issues with the previous version.

Regarding other Wi-Fi 6 clients, I’ve also tested a Lenovo Legion 5 Gen 6 laptop. Its connection is mostly stable, although I’ve noticed some minor drops or slower responses compared to how it performed before the update.

All my Wi-Fi 6 devices (POCO F3, F6, F7, and the Lenovo Legion 5 Gen 6) show some degree of instability on the 5 GHz band.

These issues started appearing since firmware version V1.0.13 and continue with the latest releases. Earlier versions seemed to perform better in terms of stability.

  @Joseph-TP for me it's about stability and speed. On 5ghz with 80 MHz width I get about 260mbps ( when I'm lucky 500mbps but it's rare). On 160mhz width I was getting near 960mbps (some times even over an gigabit) over wifi, it was blazing fast. Now this router is slower than an wifi 5 router, this is ridiculous. Also, I don't know if this latest firmware is the reason but my connection it's quite unstable ( high ping with low down/up speeds at random times). This behavior was very rare before (tho I didn't tested on 80mhz as I was using only 160mhz). I was the only router in my area with 160mhz so it was working pretty smooth. Here most routers are on 80mhz. I hope the 160mhz wasn't removed intensionally ( as I can see downgrading is blocked...)

 @Joseph-TP

Honestly, there should be some pressure for the AX50 to support OneMesh, EasyMesh, and WPA3. I can’t believe TP-Link’s engineers picked such a powerful chip for the AX50 and didn’t include that compatibility in their roadmap.

This WiFi router uses the same chipset and supports mesh networking:RT-AX58U

  @Joseph-TP 

Thanks, I will give it a go. Meanwhile, I have submitted a new post regarding a separate issue with upload speed when using IPv6 here. Relevant to this post because it's the same firmware version.

  Hi @Joseph-TP   I want to share my experience and concerns regarding the Archer AX50 firmware update 1.1.1 Build 20250917 rel.63889(4555).

Since the update, I have encountered several critical issues:

• PPPoE not working: My GPON is in bridge mode, everything was correctly configured to avoid double NAT. Previously, PPPoE worked perfectly, but after this update, I cannot connect, even though the username and password are correct.

• 160 MHz on the 5 GHz band missing: The option is no longer available.

• Router performance degraded: The device feels slow and unstable; it seems the firmware was not properly tested.

I have attempted to downgrade to previous firmware versions:

• Archer AX50(US)_V1_1.0.16 Build 20241206

• Archer AX50(US)_V1_1.0.14 Build 20240108

but both attempts failed. There must be a way to revert the firmware, as I cannot be the only user relying on PPPoE for proper network setup. Blocking downgrade effectively makes the device partially unusable.

I need a way to use PPPoE on my device. The beta firmware does not fix this, so I literally have a device I cannot use until TP-Link provides a solution. The easiest approach would be to allow users to downgrade to a version where everything worked, because I don’t expect the firmware to be fixed in one or two days.

Provide a reliable downgrade path for users: if the firmware is not updated quickly, we cannot wait for them to fix it in order to use a device that previously had no major problems. Blocking downgrade is basically a very clear strategy: something was removed or is intended to be removed, and this is how many companies operate.

Therefore, TP-Link should:

• Fix PPPoE functionality

• Restore or clarify the status of 160 MHz support

  @Alohomora 

Regarding OneMesh, the Archer AX50 was initially advertised as OneMesh Ready (coming soon). I still have the original box with gold and black stickers saying “OneMesh Ready (coming soon)”. It was officially listed on TP-Link’s website: https://www.tp-link.com/us/onemesh/product-list/

The AX50 was on the list with coming soon OneMesh support until around 2020. Even WebArchive snapshots from 2020 showing this have been silently removed. This suggests TP-Link may have been covering themselves on this issue. There is a related discussion about the AX50 and OneMesh where users noticed that the support was removed without any official announcement: community.tp-link.com/en/home/forum/topic/207652

  @SharkLatan @Joseph-TP 

I completely agree with the comments in this thread.
I used to be a big fan of TP-Link — I trusted their routers for their stability and good price-to-performance ratio. But lately, the firmware updates have been disappointing and seem to create more problems than they solve.

The Archer AX50 firmware is a clear example of this: the router has become less stable, sometimes it freezes randomly, and features have been removed without any notice (such as 160 MHz on the 5 GHz band). On top of that, firmware downgrades are now blocked, which makes it impossible to return to a version that was working correctly before.

Honestly, it feels like the developers are not properly testing the firmware before releasing it.
Losing something as important as 160 MHz support is a very serious issue, especially for users who bought this router specifically for high-speed Wi-Fi performance.

Additionally, it’s embarrassing that cheaper models like the AX20 or AX10 already support WPA3 and EasyMesh, while the AX50 — a supposedly higher-tier model — doesn’t have these features.

And now we clearly see that the Archer AX3000/AX50 V2 does include WPA3 and OneMesh/EasyMesh, according to the official product page:
https://www.tp-link.com/us/home-networking/wifi-router/archer-ax3000/#specifications

This means that TP-Link gave these features only to the V2 hardware revision and left V1 users behind, even though many of us purchased the device expecting long-term support and feature parity within the same model line.

Here is also the image shared by another user for reference:
https://static-community.tp-link.com/other/11/8/2020/7eb51e83435442b284b09b4ad376994e.png

It’s frustrating to see a router that used to work perfectly become unstable due to software decisions.
If TP-Link continues in this direction, my next router will probably be an ASUS, which generally provides better firmware support, more control, and more transparency when features are changed or removed.