Power Cycle Modem: Fix Slow Internet & VoIP in 2026
- stfsweb
- Jun 20
- 9 min read
You're in the middle of a normal workday. A customer rings. The voice breaks up. Your receptionist says the Yealink phone sounds robotic. Someone else mentions EFTPOS has stalled, and a staff member working from home can't stay connected to the hosted phone app.
In small Australian offices, that chain reaction usually starts with one thing. The internet connection has gone unstable. Before anyone logs a support ticket or starts swapping cables at random, the best first move is usually the simplest one. Power cycle the modem properly.
That sounds basic because it is basic. It's also one of the highest-value fixes you can do in-house. When a business runs on Hosted PBX, cloud apps, card payments, and remote access, a clean internet reset can save a lot of wasted time.
The Most Important First Step for Internet Problems
When a call drops, many users go straight to the phone provider, the NBN, or the router settings. An experienced support tech usually starts somewhere else. They'll ask whether the modem has been fully powered down, left off long enough, and brought back up in the right order.
That isn't superstition. According to a 2023 ACMA study, 42% of hardware-related internet incidents in Australia were resolved by a simple power cycle, and for businesses this reduced VoIP call drop incidents by 55% in test environments where equipment had been left running for over 72 hours (ACMA findings provided in the source material).
For a small office, that matters more than it sounds. If your phones, softphones, EFTPOS, booking system, and email all ride on the same connection, a flaky modem doesn't just mean slow browsing. It can mean missed calls, poor customer experience, and staff losing confidence in the phone system.
Practical rule: If the internet has gone odd rather than completely dead, a full modem power cycle is the first thing worth doing.
Why this matters more with Hosted PBX
Hosted PBX gives small businesses flexibility. Staff can work from the office, from home, or across multiple sites. Calls can follow the user instead of being stuck on an old on-premises PBX. If you're comparing access methods, this overview of internet connection types for business use is useful because the underlying service quality still affects every phone call.
VoIP is unforgiving when the connection gets messy. You might still be able to open websites while your calls sound terrible. That's why office managers often think the phone system is at fault when the issue is the modem hanging onto a stale or unstable session with the ISP.
The real-world version
A typical example looks like this:
Calls partly work: Staff can dial out, but audio chops in and out.
Internet seems half alive: Web pages load slowly, then suddenly recover.
Devices disagree: One computer works, another doesn't. Phones register, then unregister.
That pattern often points to a connection state problem rather than a full service outage. A proper reboot can clear it fast, without waiting on hold for support.
Why Turning It Off and On Again Actually Works
People joke about turning things off and on again because it works so often. With a modem, there's a practical reason. Over time, the device builds up temporary state information while it maintains the connection, hands traffic to your router, and deals with minor faults on the line. Sometimes that state gets messy.
A proper power cycle forces the modem to drop that temporary state and start clean. It reconnects to the provider, renegotiates its session, and gives the rest of your office network a fresh starting point. For business phones, that cleaner connection can mean fewer pauses, less choppy audio, and fewer one-way call issues.
What the modem is really doing
Think of the modem like the front door to your office network. If the door is jammed half-open, people can still squeeze through, but not reliably. A reboot doesn't redesign the building. It clears the jam and lets traffic flow normally again.
For Hosted PBX and VoIP, the symptoms of a tired connection are familiar:
Robotic audio: The call is connected, but voice packets aren't arriving smoothly.
Dropped registration: Desk phones briefly lose contact with the phone platform.
Lag on calls: One person talks, the other hears it a moment later.
You don't need to know the engineering detail to fix the first layer of the problem. You just need to give the modem enough time to fully shut down and then fully re-establish the line.
Why small routine resets can help offices
ABS data found that 58% of Australian businesses using Yealink VoIP phones saw fewer call quality issues after weekly modem power cycles, and a standardised protocol cut internet downtime by an average of 63% (ABS figures provided in the source material). That lines up with what support teams see every day. Offices that reboot haphazardly tend to have recurring weird issues. Offices that follow a simple routine tend to have cleaner, more predictable service.
A modem restart won't fix a damaged line or a provider outage, but it often clears the connection faults that make business phones sound worse than they should.
What it doesn't do
A power cycle isn't magic. It doesn't upgrade a weak service, repair poor Wi-Fi coverage, or fix a misconfigured handset. If your office internet is under-sized for your call load, or if staff are using softphones on bad home Wi-Fi, you'll still have problems.
That said, it's still the correct first move because it separates a temporary connection fault from a deeper network issue. That saves time before anyone starts changing settings that didn't need changing.
The Correct Power Cycle Sequence for Your Office
In a small office, the sequence matters. If you only reboot the Wi-Fi router and leave the modem untouched, you may not clear the actual issue. If you bring devices back online in the wrong order, phones and PCs can reconnect badly or sit waiting for a service that isn't ready yet.
Start with the internet source, then move inward through the office network.
The order that works best
If your office has separate devices, power them down in this order:
Modem or NBN connection device
Router or firewall
Network switch, if you use one
Yealink desk phones
Any mesh Wi-Fi units or access points
Then leave the modem fully unpowered for at least a minute before restoring anything. Region-neutral ISP guidance says that disconnecting a modem from mains power for at least 60 seconds and following a strict power-up sequence resolves connectivity issues about 70% of the time, making it the strongest first-line step before escalation (ISP guidance on modem power cycling).
The startup sequence
Bring everything back in this order:
Device | What to do | What to wait for |
|---|---|---|
Modem | Plug power back in first | Wait until connection lights stabilise |
Router | Power on after modem is ready | Give it time to establish internet |
Switch | Turn on next if separate | Let connected devices negotiate links |
Phones and Wi-Fi gear | Start last | Check phones register and Wi-Fi returns |
Most offices get better results when they're patient at the modem stage. Don't rush because the lights came on. Lights showing power are not the same as a stable internet session.
A stronger internet service also helps reduce how often you need to troubleshoot in the first place. This guide on why fibre internet suits Hosted PBX is worth reading if your office depends heavily on cloud phones.
Here's a simple video walkthrough if you want a visual reference before doing it on-site:
A practical office checklist
Use this when the phones go bad and staff are waiting.
Tell staff first: Let people know calls and internet may drop for a few minutes so nobody mistakes the reboot for a bigger outage.
Unplug from power, don't just tap buttons: A true power cycle means removing mains power from the modem.
Wait the full minute: Shorter waits often leave the same fault in place.
Watch the modem lights before moving on: If the internet or online light never settles, stop there and investigate the service.
Power up phones last: Yealink handsets behave better when the network is already stable.
If the modem isn't online yet, restarting desk phones early just creates extra confusion. They'll often try to register, fail, and make the office think the phone system is broken.
What this solves well
A correct office reboot is especially good at clearing:
stale connection sessions
intermittent packet loss
temporary registration issues on desk phones
“internet works on some devices only” behaviour
strange problems after power flickers or overnight instability
It's not glamorous. It is reliable. In support work, that combination counts.
Common Power Cycle Mistakes That Make Things Worse
The most common mistake is impatience. Someone unplugs the modem, counts to ten, plugs it back in, sees a few blinking lights, and declares the reboot done. Then nothing improves, and they assume power cycling doesn't work.
Technical guidance points out why that fails. A downtime of 10 to 20 seconds is often insufficient, and a full minute or longer is recommended before moving on to checks like cabling (step-by-step modem power cycle guidance).
The mistakes support teams see all the time
Only rebooting the router: If the modem keeps the same bad session with the ISP, the office may see no benefit at all.
Using the power board switch too quickly: Fast off-on cycles often don't let the modem fully discharge.
Ignoring the indicator lights: If the modem never regains a normal online state, the issue may sit upstream of your internal network.
Restarting phones first: That creates registration noise before the internet is healthy.
If your business uses Yealink handsets on a hosted service, it helps to know how tightly the phones depend on the connection quality underneath them. This quick read on how Yealink phones work with a Hosted PBX explains why a shaky internet session often shows up first as voice trouble.
The reset button trap
The other big mistake is pressing the tiny pinhole reset button on the router or modem. That's not the same as a reboot. It can wipe custom settings and create a much bigger problem than the one you started with.
Use a power cycle for general dropouts, slow performance, or glitchy calls. Leave a factory reset for situations where a qualified support person has told you it's necessary.
A factory reset is a last-resort move. For a small business, it can mean lost Wi-Fi settings, lost provider details, and more downtime than the original fault.
Quick comparison
Action | What it does | When to use it |
|---|---|---|
Power cycle | Restarts equipment without erasing settings | First response to unstable internet or VoIP issues |
Factory reset | Returns device to default settings | Only when directed by support or after deeper troubleshooting |
A lot of “the phones are down” jobs begin with a rushed reboot or the wrong button. Slow down and do the simple step properly. It works better than frantic troubleshooting.
What to Check When a Power Cycle Is Not Enough
If you've done the reboot properly and the office still has issues, don't jump straight to replacing hardware. Check the obvious physical and visual signs first. They tell you whether the fault is on the line, in the modem, or somewhere inside your office network.
Read the modem lights before doing anything else
Every modem is a bit different, but the pattern is usually clear enough:
Power light on, online light missing or flashing: the modem may not be establishing a proper service connection
Online light stable, router light active: the incoming service may be present, so the problem may be further inside the office
Everything looks normal but phones still struggle: test whether the issue affects all devices or mainly voice traffic
The exact label might say Internet, Online, WAN, DSL, or use a globe symbol. What matters is whether the connection light settles into a normal state after the reboot.
Do a simple isolation check
Work through the basics in order:
Check every cable by hand: Make sure Ethernet plugs are fully clicked in at both ends.
Look at the power pack: A loose or failing power adapter can cause random modem behaviour.
Test one computer directly: If possible, connect a single computer to the modem to see whether internet access works without the rest of the office network in the path.
If the modem has no life at all, don't ignore the wall socket. A dead outlet can mimic a failed modem. If that seems possible, Jolt Electric's outlet repair guide gives a practical explanation of common outlet faults and what to check before assuming the internet equipment itself has failed.
If a direct modem test works but the office still doesn't, focus on the router, switch, or internal cabling. If the direct test fails too, start thinking ISP or line issue.
What not to do next
Don't start changing random settings because the internet is slow. Don't swap multiple cables at once and lose track of what changed. And don't treat Wi-Fi symptoms as proof the internet service is down. Sometimes the NBN side is fine and only the internal network is misbehaving.
A calm isolation test usually gets you to the right answer faster than a dozen guesses.
Knowing When to Call Your ISP vs Your PBX Provider
Call the ISP when the modem won't establish a proper internet connection after a correct power cycle, or when no one in the office can get online at all. That points to the service itself, the modem, the line, or the provider-side session.
Call your PBX or VoIP provider when the office internet is working normally but the phones still won't register, don't have dial tone, or can't place and receive calls properly. In that case, the broadband link may be fine and the issue may sit with phone provisioning, handset registration, or call routing.
If a staff member needs a plain-English refresher on what internet calling relies on, this glossary entry on understanding VoIP for business calls is a handy reference.
The key is simple. If everything is offline, start with the ISP. If the internet works but calls don't, start with the phone provider.
If your business wants a phone system that's easier to support, flexible for office and remote staff, and backed by local expertise, Hosted Telecommunications provides Australian-based Hosted PBX solutions with Yealink handsets, softphone options, and ongoing support suited for small business operations.
Comments