Case Studies / Latest Case The WiFi Disappeared Every Time a Download Started: Six Months of Dropouts Traced to a Failed ASUS RT-AX59U (Lidcombe)
On-site · LidcombeOpticomm fibre25 Mbps planASUS RT-AX59UWiFi vanishes on downloadRouter hardware failure
Two details made this one unusual. The WiFi did not just stop working — the network name disappeared from the list entirely. And it happened most reliably the moment a download started. The router was near new, its settings were normal, and it had already been reset. That combination points somewhere most people never look.
Why "the WiFi disappears" is different from "the WiFi has no internet"
People describe both as the WiFi dropping out, and they are not the same fault at all.
If the network name is still in your list and you are connected to it but nothing loads, the wireless side is alive and the problem is somewhere between the router and the internet. If the network name vanishes from the list, the wireless radio itself has stopped broadcasting. Everything that happens after that first observation depends on which of the two you actually have. On this job it was the second one, and that is what moved a hardware failure to the top of the list rather than the bottom.
A configuration problem or a dead router?
| Usually a configuration or service issue | What we found here |
|---|
| What the WiFi does | Stays visible, just has no internet | Network name disappears completely |
| Admin settings | Something is wrong in there | Everything normal |
| After a reset | Usually improves or changes | Fault came back unchanged |
| Under load, e.g. a download | Slows down but stays connected | Drops out entirely |
| Swapping in another router | Same fault follows the line | Fault does not follow — unit is dead |
Which link was actually failing
Which link was actually failing
Opticomm fibre to the property
fine
→
→
→
Phones and laptop
network vanishes
Everything on the service side was doing its job. The settings inside the router were normal too, which is what makes this class of fault so easy to misdiagnose — there is nothing to find in the configuration, so people keep looking at the provider. The failure was in the box itself, and the only way to prove that is to put a different box on the same line and watch the symptom fail to follow it.
Why we waited on site instead of asking questions
The fault had been going on for around six months. By the time we arrived, the customer had stopped noticing exactly when it happened — early on they were not using the connection much, so the original pattern could not be reconstructed from memory.
Reported history is useful, but it is not evidence. So we stayed and waited until the fault reproduced itself in front of us. That one observation is worth more than any amount of description, because it fixes what the symptom actually is, and it gives you something you can retest against later. Without it, you are fixing a story rather than a fault.
How we isolated it on site
1
Went through the history — around six months of dropouts
Early occurrences not reproducible
2
Waited on site until the fault reproduced itself
Confirmed with our own eyes
3
Checked the ASUS admin settings
All normal, already reset once
4
Swapped in a test router on the same line
Would not connect at first
5
Customer called the provider to remotely reset the line
New router online
6
Ran the new router and watched for the same symptom
No dropouts — original unit faulty
The swap test, and the step that nearly blocked it
Proving a router is dead means putting a different one on the same line. If the symptom stays with the line, the router was innocent; if the symptom disappears with the old unit, you have your answer.
The complication here was that the new router would not connect straight away after being configured. The customer called the provider, and the connection came up once it had been reset remotely on their side. That wait took a while, and it is worth planning for — if you are testing a spare router at home, expect that swapping hardware on some connections needs the provider to do something before the new unit is allowed online. Once it was up, we ran it and the dropouts did not return.
What we would take from this one
- Describe the symptom precisely. "The network name disappears" and "I am connected but nothing loads" send you down two completely different paths.
- A near-new router is not automatically a healthy router. Age makes hardware failure less likely, not impossible.
- Normal settings plus a reset that changed nothing is itself a finding. It moves hardware up your list instead of leaving it at the bottom.
- Wait for the fault if you can. One reproduction in front of you beats an hour of recalled history, especially after months of it.
- The swap test is the proof. Without a second router to compare against, most people end up blaming the provider — and the provider is often right to say their side is fine.
- Budget time for the provider step. Some connections need a remote reset before a replacement router is allowed online.
Result
With a test router on the same Opticomm line — online after the provider reset the connection remotely — the dropouts did not return, and downloads no longer made the WiFi vanish. That confirmed the original ASUS RT-AX59U had failed as hardware, despite being near new and having normal settings, and gave the customer a clear answer after around six months of intermittent dropouts.