Archer AX12 V1 – Request for a Stability-Focused Performance Firmware Update
Title: Archer AX12 V1 – Comprehensive Firmware Optimization, Stability, Performance and Reliability Improvement Request
Hello TP-Link Technical Team, Engineers and Community Members,
I would like to make a detailed firmware improvement request for the TP-Link Archer AX12 V1.
The purpose of this request is not simply to ask for additional features. My main goal is to request a comprehensive review and optimization of the existing firmware so that the Archer AX12 V1 can provide the most stable, consistent, efficient and reliable performance possible from its existing hardware.
The Archer AX12 is a Wi-Fi 6 router, and I believe its firmware should make full and efficient use of the available hardware resources.
Instead of focusing primarily on adding more features, I would like TP-Link to prioritize wireless stability, consistent throughput, low latency, efficient CPU/RAM utilization, reliable multi-device performance and long-term system stability.
I would like the TP-Link firmware/wireless engineering team to consider the following areas.
1. Overall firmware optimization
Please review the complete firmware architecture and identify any components, services, processes or background functions that may unnecessarily consume CPU, RAM or other system resources.
Possible improvements could include:
- Reducing unnecessary background processes
- Optimizing CPU utilization
- Optimizing RAM usage
- Improving memory management
- Preventing memory leaks
- Improving long-term uptime stability
- Reducing unnecessary firmware overhead
- Improving system response time
- Improving network-processing efficiency
The objective should be to make the existing hardware work as efficiently as possible.
2. 2.4GHz wireless stability
The 2.4GHz band should receive particular attention.
Reported problems with wireless performance can include:
- Sudden speed reductions
- Very low throughput
- High latency
- Packet loss
- Retransmissions
- Random instability
- Channel-related performance changes
- Recovery after reboot
- Temporary recovery after changing channels
- Performance degradation after extended operation
In my case, the 2.4GHz connection can sometimes experience a dramatic performance drop, with throughput falling to approximately 1Mbps and latency reaching around 300–1000ms.
Changing the Wi-Fi channel or restarting the router can temporarily improve the situation, but the problem may return later.
I would therefore like the engineering team to investigate whether the problem could involve:
- Wireless driver behavior
- Channel management
- Automatic channel selection
- RF management
- Interference handling
- Power management
- Retransmission behavior
- Packet scheduling
- Firmware resource utilization
- Wireless radio stability
3. 5GHz stability
Although the 5GHz band generally provides higher performance, firmware should also be reviewed for possible:
- Random disconnections
- Unexpected speed reductions
- Throughput fluctuations
- Long-term stability problems
- Recovery problems
- Performance degradation after extended uptime
The objective should be consistent 5GHz performance rather than simply achieving a high negotiated link rate.
4. Maximum practical Wi-Fi performance
I would like TP-Link to investigate whether the firmware consistently allows the router to achieve the maximum practical throughput supported by its hardware and the connected client.
A high theoretical link rate is useful, but real-world throughput should remain stable and predictable.
The firmware should ideally minimize unnecessary performance loss caused by:
- CPU limitations
- Wireless driver behavior
- Firmware overhead
- Queue management
- Background services
- Inefficient packet processing
- Poor resource allocation
5. Multi-device performance
Please optimize the firmware for situations where many devices are connected simultaneously.
For example:
- Smartphones
- Computers
- Smart TVs
- Streaming devices
- IoT devices
- Gaming devices
- Downloading devices
One device performing a large download or upload should not unnecessarily cause severe latency or performance degradation for other clients.
6. QoS improvement
I would like TP-Link to significantly improve the QoS system.
More advanced controls could include:
- Per-device bandwidth limits
- Separate upload and download limits
- Device priority
- Application/traffic priority
- Minimum bandwidth allocation
- Maximum bandwidth allocation
- Better traffic scheduling
- Better multi-device fairness
- Better latency management
- Better bufferbloat control
- Better handling of upload saturation
- Better handling of download saturation
A more advanced QoS system would be particularly useful for users with multiple devices and high-speed Internet connections.
7. Latency and bufferbloat
Please investigate whether the current queue management and packet scheduling can be optimized.
During heavy traffic, the router should attempt to maintain reasonable latency instead of allowing ping to increase dramatically.
This is especially important for:
- Online gaming
- Voice calls
- Video calls
- Remote work
- Streaming
- Real-time applications
The objective should be to maintain responsiveness even when the connection is being heavily utilized.
8. WAN-to-Wi-Fi performance
Please review the complete data path:
Internet/WAN → Router processing → QoS/NAT → Wireless driver → Wi-Fi client
If there is unnecessary processing overhead anywhere in this path, firmware optimization could potentially improve real-world throughput and latency.
9. NAT and hardware acceleration
Please review:
- NAT acceleration
- Hardware offloading
- Flow acceleration
- Packet forwarding
- Connection tracking
- QoS interaction with hardware acceleration
If enabling QoS disables or reduces hardware acceleration, the firmware could potentially provide a more optimized implementation.
10. Channel management
Please review the automatic channel-selection mechanism.
The router should be able to make sensible channel decisions without unnecessarily moving clients between channels or selecting channels that produce poor real-world performance.
Manual channel selection should also remain reliable and predictable.
11. Wireless roaming and client handling
Please review how the router handles multiple wireless clients.
Potential improvements could include:
- Better client association
- Better client steering
- More stable connections
- Better handling of weak clients
- Better handling of idle clients
- Reduced unnecessary disconnects
- Better coexistence between 2.4GHz and 5GHz
12. Firmware update reliability
Future firmware updates should ideally improve performance without introducing regressions.
I would strongly encourage TP-Link to perform extensive regression testing before releasing new firmware.
Testing should include:
- 2.4GHz stability
- 5GHz stability
- Long-duration uptime
- Maximum throughput
- Multiple simultaneous clients
- QoS
- High-speed WAN connections
- IPv4
- IPv6
- AP Mode
- EasyMesh
- Ethernet-to-Wi-Fi throughput
- Large downloads
- Large uploads
- Gaming latency
- Streaming
- Long-duration traffic
13. Configuration migration
Please also consider problems that may occur when an old configuration is retained after a firmware update.
If certain settings become incompatible with a new firmware version, the router should ideally detect this automatically rather than allowing an old configuration to cause unexpected performance problems.
14. Better diagnostic tools
It would be extremely useful if future firmware provided more detailed diagnostic information.
For example:
- CPU usage
- RAM usage
- Wireless channel utilization
- Client traffic
- Packet loss
- Retransmissions
- Wireless signal information
- QoS activity
- WAN utilization
- LAN utilization
- System events
- Wireless driver events
- Connection history
This information could help both users and TP-Link engineers identify problems much faster.
15. Optional Lite / Performance firmware
I would also like TP-Link to consider an optional Lite or Performance firmware for the Archer AX12 V1.
This firmware would not need to contain every feature of the standard firmware.
Instead, it could focus on:
- Maximum stability
- Maximum practical throughput
- Low latency
- Efficient CPU usage
- Efficient RAM usage
- Multi-device performance
- Long-term reliability
- Reduced background processing
- Optimized wireless drivers
In other words:
Stability and performance first, additional features second.
Users who want the full feature set could continue using the normal firmware, while users who prefer maximum performance and stability could use the Lite/Performance version.
16. Hardware utilization
If the existing AX12 V1 hardware has additional unused processing or memory capacity, please consider whether future firmware can make better use of those resources.
The goal should be to extract the maximum practical performance from the hardware already installed in the router.
17. Long-term reliability
The router should ideally maintain similar performance after hours or days of continuous operation.
Please consider testing:
- 24-hour operation
- 48-hour operation
- 7-day operation
- Continuous network traffic
- Multiple connected clients
- Heavy download/upload
- Continuous Wi-Fi activity
If performance gradually decreases over time, the firmware should be investigated for possible memory, driver, queue-management or resource-management problems.
18. User-selectable performance modes
If technically possible, future firmware could provide different modes such as:
- Standard Mode
- Performance Mode
- Stability Mode
This would allow users to choose whether they prefer maximum features or maximum network performance.
19. Engineering-level firmware review
Most importantly, I would like this request to reach the TP-Link firmware and wireless engineering team rather than being treated only as a standard configuration-support question.
I am not simply asking for instructions such as changing the channel, rebooting the router or resetting the configuration.
Those steps can sometimes temporarily improve the situation, but I would like the underlying causes to be investigated.
My request is for a deeper firmware/driver-level review.
20. Future firmware request
If these problems can be addressed through software or firmware, I would greatly appreciate TP-Link developing a firmware update that focuses on:
- 2.4GHz stability
- 5GHz stability
- Maximum practical throughput
- Lower latency
- Better QoS
- Better bufferbloat management
- Better multi-device performance
- Better CPU/RAM utilization
- Better long-term stability
- Better wireless-driver reliability
- Fewer firmware regressions
If a beta or test firmware is available, I am willing to test it and provide detailed feedback.
I can provide:
- Speed-test results
- Ping/latency results
- Wi-Fi screenshots
- Channel information
- Router logs
- Client information
- QoS tests
- 2.4GHz vs 5GHz comparisons
- Ethernet vs Wi-Fi comparisons
- Before/after firmware testing
Router information:
Model: TP-Link Archer AX12
Hardware Version: V1
Region: US
Firmware: 1.5.1 Build 20260721 Rel. 50105(5553)
Final request to the TP-Link Engineering Team:
Please consider prioritizing firmware stability, wireless performance, latency, resource efficiency and reliability for the Archer AX12 V1.
The main goal should not simply be to add more features.
The goal should be to make the existing AX12 V1 hardware perform as efficiently, consistently, reliably and stably as possible.
If there are known limitations that cannot be solved through firmware, I would also appreciate a clear technical explanation.
Thank you to the TP-Link engineers, technical support team and experienced community members who take the time to investigate these issues.
I hope this request can be reviewed by the appropriate TP-Link firmware and wireless engineering teams and considered for a future firmware release.
