Router Keeps Restarting? Fix It at Home

A router that keeps restarting is easy to blame for every drop, yet the national picture is quieter than a failing box. In the ACCC’s September 2024 Measuring Broadband Australia report, NBN connections recorded an average of 0.37 outages per day, 89% of monitored households experienced fewer than one outage per day, and 69% of outages lasted no longer than three minutes. Those figures describe service interruptions, not a modem that loses power and cycles its lights. If your unit goes dark and comes back again and again, you’re looking at a more persistent local symptom than a typical short NBN drop.

Before you unplug anything, write down what you can still see. The time, the lights, and whether a cable still works will tell you more than another restart.

Table of Contents

Tell a Router Reboot from a Normal NBN Drop

Name the connection type before you compare your log with that benchmark. FTTN, FTTC, HFC, FTTP and fixed wireless don’t fail the same way, and power backup plus fault ownership change with the technology. On FTTN or FTTC you’re watching a connection box or wall plate as well as the router. On HFC the cable modem’s sync light matters. On FTTP the white NBN box is a separate device. Fixed wireless depends on the outdoor unit and the indoor box. A three-minute pause on any of those can be a normal service blip. A box that loses power, cycles every status light and reconnects on a loop is not that blip.

An infographic comparing a typical brief NBN connection drop to a standard router reboot event.

Write the exact restart time and whether every light goes dark. Then check the NBN connection status in your provider’s app, or on the connection box, for that same minute. If the NBN box stays lit and only your router dies, the fault is inside the premises: a failing power adaptor, heat, firmware, damaged cabling or unstable power. If the NBN lights drop with the router, you’re closer to an upstream fault. Fixed wireless in the same report sits near the wired pattern, at 0.39 outages per day, with 91% of households under one outage a day and 57% of outages at three minutes or less. Use the table as the yardstick for your own notes, not as a reason to ignore a unit that keeps rebooting.

MeasureNBN connectionsNBN fixed wireless
Average outages per day0.370.39
Households with fewer than one outage a day89%91%
Outages lasting three minutes or less69%57%

Practical rule: One short drop inside those ranges is ordinary. Restarts that repeat through the evening, with the lights going fully dark, are a local fault until the log says otherwise.

If Wi-Fi is the only thing that vanishes, follow a separate path in our Wi-Fi troubleshooting steps rather than treating every dropout as a reboot. Keep the paper log. You’ll need the times when you ring the telco or sit down with a technician.

Match the Restart Symptom to One First Check

Pick one row and stop. Running every fix in an afternoon wipes the clue you needed. Plug a computer in by Ethernet, note the clock, and ping the router’s local gateway and an outside address together. Read the table from the top and take the first match.

What you seeLikely layerFirst check
All lights go dark then cycleRouter or power lossOriginal adaptor on a wall outlet
Gateway and external pings fail togetherDevice reboot, heat or firmwarePower, vents, then logs
Gateway answers, external ping failsNBN, WAN login or ISPRecord time and connection type
Wi-Fi drops, Ethernet stays up2.4 GHz interferenceMove interferers, try 5 GHz
Restart after a brief power flickerShared board or failing adaptorSeparate NBN box and router outlets
Hot case or restart after an updateHeat or firmwareVentilation, then a controlled update

When both pings die

If all status lights go dark and then cycle, treat it as power loss or a device reboot. Put the original adaptor straight into a wall outlet before you ring the ISP. A shared board, a loose plug or a tired adaptor will mimic an internet fault, and a new router won’t fix a bad supply.

If a wired computer’s pings to the gateway and an outside address fail together, the router itself has left the network. Inspect power, heat, firmware and hardware, in that order. Pull USB dongles and spare switches so they aren’t part of the story. Open the system log afterwards and look for watchdog, kernel or power-loss lines. Don’t factory-reset yet. A reset deletes the entries that explain the restart.

When only the outside world fails

If the gateway still answers and only the external ping fails, the router is up. The break is NBN sync, WAN login or the provider. Record the time and the connection type, then leave the hardware alone. Buying another router here wastes money. The WAN light, the NBN box and the provider’s status page are the useful checks.

A house flicker followed by a restart points at a shared board or a failing adaptor. Put the NBN connection box and the router on separate wall outlets so you can see which one lost power.

When it isn’t a reboot at all

Wi-Fi that drops while Ethernet stays up is radio trouble, not a rebooting router. ACMA testing found that all tested devices showed some susceptibility to external interference in the 2.4 GHz band, while 5 GHz generally delivered better performance. Microwaves, cordless phones, baby monitors, wireless cameras, electrical cabling, neighbouring networks and industrial equipment are the usual suspects. Switch those devices off for a short test, move them, and try a 5 GHz network name. Those tests can’t explain a router whose wired gateway also disappears.

A hot case, or a restart that began right after an update, belongs with ventilation first and a controlled firmware step second. Change one thing only, and write the clock time beside it.

Change two settings at once and you no longer know which one stopped the restart, or which one caused the next one.

Run the Power, Heat and Cable Check

Photograph the lights and write the time before you touch a cable. A reset can erase the only clue you had, and seniors or anyone working from home will want those notes on paper for a later visit.

An instructional graphic showing steps to troubleshoot a router by checking lights and logging into the gateway.

Work through this sequence and stop once the pattern is obvious. Each step has a reason.

  1. Photograph the lights and write the time. You’re recording the state before a power pull changes it. Note which lamps are solid, which are blinking, and whether the NBN connection box matches the router.
  2. Find the gateway, then use a cable. The address is often 192.168.0.1 or 192.168.1.1. On Windows, run ipconfig and read the default gateway. On a Mac, open network settings and look at the router address. Plug one laptop into a LAN port so Wi-Fi can’t confuse the test.
  3. Ping for two minutes. Ping the gateway and an outside address such as 1.1.1.1. On Windows, ping -t keeps the test running. If both fail at the same second, the router left the network. If only the outside address fails, the box is still alive.
  4. Move the original adaptor to a wall outlet. Take it off a shared power board that also feeds a heater, a printer or the NBN box. Don’t borrow another adaptor unless the voltage, polarity and current on the label match. A wrong supply can damage the router or hide the underlying fault.

The next check is electrical, and it’s the one Melbourne houses miss after a brief flicker. ACMA’s better practice guide states that NBN service will not work during a power failure unless the connection is FTTP and an NBN battery backup power supply unit is installed and operating. If the modem, router and NBN box share a loose board or an overloaded outlet, a short sag looks like an internet fault. Note whether the NBN box lost power too.

If you want a short walk-through of reading lights while you ping, this clip covers the same idea of watching the box instead of guessing.

  1. Give the case air, then feel it. Lift the router off carpet, out of a cupboard and away from a sunny window. Keep about a hand’s width clear of the vents. After an hour of normal use, the case should be warm, not hot enough that you pull your hand back. Heat triggers restarts that look random because they follow streaming, backups or a closed cabinet, not the clock.
  2. Strip the extras, then read the log. Unplug USB dongles, spare switches and anything in the USB port. In the admin screen, open the system log and search for watchdog, kernel panic or power-loss lines. A watchdog line means the software gave up and restarted itself. A power-loss line means the supply dipped even if the house lights didn’t flicker.
  3. Stop when the pattern is clear. Three matching events are enough. More resets only train the household to live with the fault. Leave the paper note where a technician or the telco can read it: times, which lights changed, what was plugged in, and whether the NBN box died too.

What to leave alone

Don’t press the reset pinhole during this pass. Don’t swap the Ethernet lead, the channel and the adaptor in one sitting. The lead can wait until the log shows a link that drops while the router stays powered. I would start with the cheapest fix, the original adaptor on a bare wall outlet, before anyone talks about a new router.

Update Firmware Without Losing the Setup

Firmware comes after power and heat are stable. A reset first throws away the log entries that showed a watchdog or a power dip. An automatic-update toggle is also not proof the build is current. An ACMA household survey found 79% of households with smart devices ensured updates were applied, but only 50% enabled automatic updates. Plenty of homes are waiting on a manual check or a vendor prompt that never quite gets done.

A hand using a pencil to point at a laptop screen showing firmware update information for a router.

Back up, then update

Check the vendor page or the router’s admin screen and compare the installed build with the current release for that exact model and hardware revision. Photograph the screen if the export button is missing.

Write these down before you change anything:

  • ISP login and, where your NBN type needs it, the VLAN ID.
  • Wi-Fi name and password, including a separate 5 GHz name if you use one.
  • Port forwards and any content-filter or parental-control rules.
  • VPN, QoS and mesh settings, but don’t turn those back on yet.

Apply the vendor update on a wired computer, and don’t pull power mid-install. Use a controlled factory reset only when the log already points at corruption, not as a first move. Afterward, rebuild the minimum: internet access and one Wi-Fi name. Leave guest networks, schedules and filters off.

Watch it for a day

Run a 24-hour wired monitoring test before you restore VPN, parental controls, QoS or mesh backhaul. Ping from the laptop you left on Ethernet, or note whether that PC loses its gateway while you’re out. If the day stays clean, add one feature and watch again. If it restarts with only the basic setup, the optional features weren’t the cause.

Replacing the router because an older phone is slow on a new modem, or because the lounge Wi-Fi dips at dinner, often misses the real fault.

2.4 GHz and 5 GHz use class-licensed spectrum, and protection from interference can’t be guaranteed. Older phones and laptops may also fail to get the best from a newer modem-router. Fix channel, placement, compatibility or the WAN path first. While you’re in the admin screen, it’s worth tightening router security settings so remote admin isn’t left open, but don’t mix that tidy-up with the update test.

Replace the power supply or the router only when logs, a warm-to-hot case and repeated wired drops still point at the device after this watch. Otherwise you’re paying for hardware that was never the fault.

Know When to Call the Telco or a Technician

Stop resetting once the evidence is clean. Three tests are enough if they show the gateway dying with the NBN connection box, or the gateway staying up while the WAN light never syncs. Stop as well if the original adaptor, clear vents and current firmware still produce wired restarts. Another power cycle won’t create a better story for the person who has to fix it.

An infographic titled Know When to Call the Telco or a Technician with three numbered troubleshooting steps.

Who owns the fault

ACMA’s guide to NBN problems splits responsibility in a way that saves a week of phone tag. Service problems, speed issues, and damage or problems involving NBN equipment go to the telco on your NBN plan. Work on existing phone and data cabling is the household’s job and needs a registered cabler. If the telco doesn’t resolve the complaint, or sends you back and forth with NBN, the Telecommunications Industry Ombudsman may assist.

Fault typeWho to contactEvidence to bring
Service, speed or NBN equipment damageTelco on the NBN planReboot times and light changes
Damage to existing phone or data cablingRegistered cablerLocation and connected equipment list
Telco and NBN passing the complaint back and forthTelecommunications Industry OmbudsmanFull log and the complaint history

Attach the paper log to the call. Include reboot times, which lights changed, what was plugged in, and whether the NBN box lost power. That packet separates a router fault from a line or provider fault faster than a description of “the internet keeps dropping”.

A cracked wall plate, a stapled phone lead or a data point that sparks when you move the plug is cabling, not a warranty claim on the router. Point the cabler at the room and the list of what’s connected. For a sync failure on a healthy router, stay with the telco and quote the connection type, FTTN, FTTC, HFC, FTTP or fixed wireless, plus the minutes the WAN light refused to settle.

What to have ready if you want hands-on help

The fix is often a power supply or a setting, not a new router. Have the reboot times, the NBN type and the adaptor label ready before you book anyone. We troubleshoot slow connections and internet drop outs, and we sort Wi-Fi setup and coverage upstairs or out to the garage. Our technicians identify the issue first and match the solution to the fault and your budget, including a proper NBN modem setup when the connection itself was never finished cleanly. Remote help suits a network that’s already stable enough to reach. An on-site visit suits a box that dies before anyone can log in.

Don’t keep resetting overnight to “see if it settles”. You’ve already got the test that says who should take the next step.


If your router keeps restarting after the adaptor, vents and firmware checks, Computer Daddy can troubleshoot the drop outs at home across South East Melbourne, from a patient on-site look to remote support once the line stays up. We’ll separate a tired power supply or a bad setting from a genuine NBN fault, and we’ll favour a repair that fits the problem. Visit Computer Daddy when you want that log read with you rather than another weekend of unplugging.

Scroll to Top