Hi everyone,
I’m reaching out because I’m hitting a wall with my ASUS RT-BE86U and I suspect there might be a firmware bug or a resource handling issue specific to this model.
The Setup:
The Issue:
I experience massive desync and "heavy gameplay" (shoot first/die first, players skating) after the router has been running for a while.
The Anomaly (Why I'm posting here):
Since a simple reboot doesn't clear the "bad state" but a factory reset does sometimes, it feels like some deep persistent table, cache, or log is getting corrupted or saturated.
Has anyone experienced this behavior with the BE86U? Is there a known degradation issue with the current firmware for this model?
Thanks in advance!
I’m reaching out because I’m hitting a wall with my ASUS RT-BE86U and I suspect there might be a firmware bug or a resource handling issue specific to this model.
The Setup:
- Router: ASUS RT-BE86U (Stock Firmware).
- ISP: Digi Spain (1Gbps Fiber, PPPoE connection).
- Main Usage: Competitive Gaming (Call of Duty: Black Ops 7, EA FC 26) on PS5.
- Current Settings: Adaptive QoS is Enabled. I have also tried Port Forwarding, but the issue persists.
The Issue:
I experience massive desync and "heavy gameplay" (shoot first/die first, players skating) after the router has been running for a while.
- Ping: Stable and low (approx. 20ms).
- Packet Loss: None reported by game/tests.
The Anomaly (Why I'm posting here):
- Rebooting the router (power cycle) or the ISP modem (ONT) does NOT fix the issue. The desync persists immediately after the reboot.
- Factory Resetting (Hard Reset/Initialize) the router is the ONLY thing that fixes it. After a factory reset, the hitreg and connection feel perfect and crisp.
- However, after few hours of usage, the performance degrades again, returning to the unplayable desync state until I perform another factory reset.
Since a simple reboot doesn't clear the "bad state" but a factory reset does sometimes, it feels like some deep persistent table, cache, or log is getting corrupted or saturated.
Has anyone experienced this behavior with the BE86U? Is there a known degradation issue with the current firmware for this model?
Thanks in advance!
