Hi @Danny--,

Thank you for contacting our community.

Did this problem start after the AX53 firmware update? 

• It is recommended that you can try a different cable to test the connection between AX10 and C5. 
• Or, you can swap the Ethernet cables between the main router and AX10 to confirm whether the problem is caused by a specific cable.
• Please also try to change the topology to AX53→C5→AX10 for a comparison.

Hi @Joseph-TP 

Thanks for responding.

Yes, the issue started only after I switched to AX53 as the main router. Previously, I used AX10 as the main router with two C5s as nodes, all connected via Ethernet, and everything worked perfectly — no switching, no performance issues.

Now, with the setup AX53 → AX10 → C5, even though everything is wired, the nodes randomly switch to wireless backhaul. The web interface on AX53 is also very laggy, regardless of the browser I use — so it’s not a browser issue. I believe this is either a firmware issue or something related to how AX53 handles EasyMesh and resource load.

Also, I noticed something very specific — if I manually disable Wi-Fi on the AX53, the nodes instantly switch to wired mode. So clearly, wired is working fine, but the firmware might be forcing fallback to wireless unnecessarily.

I’ve tested with different cables and swapped ports, and all devices are already running the latest firmware — including AX10 and C5s.

Another observation is that the AX53’s CPU spikes to 90% frequently (especially since it’s handling a PPPoE connection), and at those times, upload speeds tend to drop too.

So, my request is simple:
Please consider adding an option in EasyMesh to select backhaul type (e.g., “Wired Only,” “Wireless Only,” or “Auto”). That way, users like me who rely on Ethernet wiring can avoid unnecessary backhaul switching.

This will help maintain a stable, high-performance mesh without needing to buy additional switches just to force a wired setup.

Thanks again for your help and hoping for improvements in future firmware updates!

Hi@Danny--,

Thank you for your detailed reply.

I may need to confirm again, the Archer C5 is an ISP customized device and end of life now. I am not sure if it supports Easymesh. 

Did you also create an easymesh network when you used AX10+2*C5 before?
Can you see AX10 and C5 in the Mesh list now?

For new feature request, you can go to Start a New Thread on the Feature Request Board. 

Hi   @Joseph-TP ,

Thanks for your response.

Yes, both Archer C5 units are ISP-customized, but they do support EasyMesh, and I can confirm that. Previously, when I used the AX10 as the main router (AX10 + 2*C5), everything worked perfectly in wired backhaul mode with no issues.

Currently, with the AX53 as the main router, both the AX10 and C5 units show up in the EasyMesh list. However, the issue is that sometimes the C5s randomly switch to wireless backhaul, even though they are wired properly. That’s the main concern I’m facing now.

Additionally, the web interface of the AX53 is extremely laggy, especially when accessing or scrolling through the EasyMesh section. Sometimes the router even restarts itself during this. This behavior is strange, as I’ve tested it on two different high-end PCs (including my gaming PC), and on four different browsers: Brave, Microsoft Edge, Chrome, and Firefox. The problem persists across all browsers, so it is clearly not a system or browser issue.

Interestingly, the TP-Link Tether app works smoothly with no lag. However, I’ve noticed that even when I’m connected to the local network at home, the app sometimes detects the router as a cloud device, which is unexpected — although it still functions properly.

To summarize:
 

• Firmware is up to date on all devices.

• C5s work with EasyMesh, even if ISP-customized.

• Main issue: C5s randomly switch to wireless mode, even though wired.

• Major issue: AX53 web interface is extremely laggy, sometimes leading to a router reboot.

• Tether app works fine, but cloud detection happens even on the local network.

Request: Please add a feature in the firmware to allow users to force “Wired Only” backhaul instead of automatic switching. This would fix most of the mesh-related instability. Also, please fix the extreme lag in the AX53 web interface, especially under EasyMesh — it’s nearly unusable in its current state.

Thanks for your support.

Hello@Danny--,

Many thanks for your detailed reply.

For the issue of Archer C5, it is recommended that you can ask your ISP for suggestions. Even if we add a "Wired Only" backhaul option to the main router, Archer C5 must also support this function in order to use it simultaneously.

For Archer AX53 issue, it is recommended that you clear the cache on your browser;
Temporarily turn off the computer's firewall, antivirus software or VPN to test whether the lag is alleviated;
If it still doesn't work, try to reset the router AX53, or replace it with another router for testing.

  @Joseph-TP 
 

Hi @Joseph-TP ,

Thank you for your response.

Let me clarify a few important points regarding the issues I’m facing with the Archer AX53 and the EasyMesh setup:

1. Archer C5 Compatibility

• Both of my Archer C5 units are ISP-provided but fully support EasyMesh — confirmed by:

  • AX53 detecting both C5s under the EasyMesh tab.

  • Previously with AX10 as the main router, both C5s connected over wired backhaul without issues.

• So this is not a compatibility issue — the real issue is that the AX53 is randomly switching to wireless backhaul despite a proper Ethernet connection.

2. “Force Wired Backhaul Only” Option Request

• Please add a firmware-level toggle to force mesh connections to use only wired backhaul.

• This would solve issues for setups like mine with multiple mesh routers, where auto-switching to wireless severely affects performance.

3. Severe Lag in AX53 Web Interface

• The web interface is extremely laggy, especially when accessing the EasyMesh section.

• It becomes unusable, and sometimes even causes the router to restart by itself.

• I have tested this thoroughly:

  • On two different PCs (including a high-end gaming PC)

  • Using Brave, Chrome, Firefox, and Edge

• I also reset the router and set everything up from scratch — still the lag continues.

• Only the web interface is affected — the TP-Link Tether app works fine, though occasionally it misidentifies the router as a cloud device even when I’m connected locally.

4. Overheating & CPU Usage

• The AX53 overheats significantly under normal usage.

• As I'm using a PPPoE connection, the CPU usage spikes to 70–90% often, which could explain the lag and instability.

• This is not normal and likely needs firmware optimization for both PPPoE load handling and thermal management.

Final Request:

Kindly escalate this to your firmware/engineering team and please address the following:

• Add a “Force Wired Backhaul Only” setting for EasyMesh.

• Fix the web interface lag, crashes, and random reboots.

• Optimize CPU usage for PPPoE connections.

• Improve thermal performance to reduce overheating.

Thanks again for your time and support,
Danny

 @Joseph-TP Hi,

Thanks for your response.

Just to clarify and update a few things:

🔁 Firmware:

I already tested the pre-release firmware (v1.4.3) mentioned in the link. Unfortunately, it was more laggy than the current one, so I have reverted back to the stable version v1.4.2.

Please understand: the web interface is still extremely laggy, especially when managing EasyMesh. It sometimes even causes the router to restart by itself.

⚠ AX53 Web Interface Issues:

• I've tested on two different PCs (including a gaming PC).

• Tried multiple browsers: Chrome, Brave, Edge, Firefox.

• All show same laggy behavior on web interface.

• TP-Link Tether app works fine, but sometimes it detects the router as a cloud device even when I’m on WLAN.

This problem never happened on my old AX10 router — the interface was smooth and stable.

🔥 Overheating & CPU Spike:

• The AX53 gets very hot during regular use — seems like thermal optimization is needed.

• CPU usage spikes to 70–90%, even without any active load.

• I'm using PPPoE, and yes — this issue is reproducible every time.

🚫 About USB:

You asked about USB storage — but the AX53 doesn't even have a USB port. So that’s not relevant.

✅ Already Tried:

• Router reset and full re-setup was already done.

• Still, nothing fixes the web UI lag issue.

🟩 Final Request:

Please escalate this to the firmware/dev team. The web interface lag, overheating, and CPU usage need to be optimized in future firmware updates.

Let me know if you still need system logs — I’ll send them.

Thanks again,
Danny

Hi@Danny--,

Thank you for your reply.

We would like to escalate your case to the support engineers, and they will help follow it up, if you are willing to do further analysis, please check your inbox and respond.