If every meeting has that moment where someone's screen freezes, the Wi-Fi isn't usually the internet, the router, and your devices at the same time — it's one of them, and the rest are a symptom. The triage order is the same every time: router first, ISP second, the device itself last. Here are five fixes a non-tech can try in under ten minutes — and an honest pitch for the $89 backup line when DIY isn't the answer.
About 90% of the time, "unreliable" Wi-Fi is a router problem or an ISP problem, not a device problem. Two-minute checklist before the longer guide:
1. Restart your Wi-Fi router (unplug, count to thirty, plug back in and wait for the lights to settle).
2. Check the modem lights — both "online" and "sync" should be solid. If they're blinking or off, it's your ISP, not anything on this list.
3. Forget the network on one device and reconnect it. If that one device is now rock-solid while the rest still drop, that one device is the problem (Fix 3).
If not, walk through the five fixes below in order.
The single most common reason an office Wi-Fi goes flaky is the router itself — not the internet, not the devices, the router. Routers are small Linux computers running 24/7, and like any small computer, their internal state slowly goes bad over weeks or months. A power blip, an ISP-side DHCP renewal, or a firmware update that happened overnight is enough to leave the router running but no longer routing traffic cleanly — especially on the 2.4 GHz band, which most IoT devices and older laptops still use.
What to do: power-cycle it. Unplug the router (don't just hit the power button — physically unplug it). Count to thirty (this isn't superstition — the capacitors inside need a moment to fully drain or the router does a "warm boot" instead of a true reboot). Plug it back in. Wait two to three minutes for the lights to settle.
What the lights mean: most consumer routers show a power light, a WAN/internet light, a Wi-Fi light, and several LAN lights for wired ports. After a clean boot, the power light goes solid, the WAN light turns solid once the router has talked to your modem and gotten a public IP, and the Wi-Fi light goes solid once the radios are broadcasting again. If the WAN light keeps blinking for more than two minutes, the router can't reach your ISP — jump ahead to Fix 5.
Most office routers broadcast two networks: one ending in "5G" or "5GHz" and one without. The 5 GHz band is faster but shorter-range; the 2.4 GHz band is slower but reaches further and is what almost every IoT device, older laptop, and older printer still uses. If your team is mostly on phones and laptops, you probably have every device in the office piling onto the same 2.4 GHz channel — and once you hit 8–10 simultaneous devices on the same channel, the airtime essentially stops working.
What to do: log into your router (type 192.168.1.1 into a browser — most routers print this on a sticker on the bottom) and change the 2.4 GHz channel from "Auto" to a fixed channel. Pick channel 1, 6, or 11 — those three don't overlap. "Auto" usually picks the wrong channel in a small office because it can see your neighbors' networks and gets confused.
What "channel 1/6/11" means in plain English: Wi-Fi channels are radio frequencies. Channels 1, 6, and 11 are the only three in the 2.4 GHz band that don't overlap with each other. If your router is on channel 3 and your neighbor's is on channel 4, your devices spend half their time waiting for the other network to finish talking. Channel 1, 6, or 11 — pick whichever is least crowded when you look at your router's scan page.
Sometimes the Wi-Fi is fine and one specific device is the problem. The classic case: a laptop woke from sleep mode, the router handed the same laptop's old IP address to your printer by mistake, and now every device in the office has trouble reaching the printer (and the laptop keeps "just barely" working). This is called a stale DHCP lease, and it's surprisingly common in offices where people close their laptops at the end of the day instead of shutting them down.
How to tell which device is the problem: on your router's device list (the same 192.168.1.1 page as before), look for any device whose hostname you don't recognize, or whose IP address looks duplicated. Write down the offending device's MAC address — it's usually listed alongside the IP.
The fix is on the bad device, not the router: forget the network and reconnect. On macOS: System Settings → Wi-Fi → click the small "i" next to your network → "Forget This Network" → rejoin with the password. On Windows: Settings → Network & internet → Wi-Fi → your network → Forget. On iPhone or Android: long-press the network name → Forget. Then rejoin with the password written down somewhere. The next time the device wakes from sleep, it'll ask the router for a fresh IP and stop fighting everyone else for the same one.
Wi-Fi is just radio, and radio doesn't travel through metal, mirrors, or water very well. A coworker with a metal filing cabinet between their desk and the router will have unreliable Wi-Fi six feet away from someone on the other side with clear line of sight. So will anyone sitting near a microwave when it's running (microwaves leak 2.4 GHz on purpose — the same band your office Wi-Fi uses), a large aquarium, or a wall with foil-backed insulation.
The "is it me or is it the wall" test: stand directly next to the router with a phone, run a speed test, then walk to where you actually work and run it again. If the speed drops to a third or worse when you move away from the router, the wall (or something in it) is the problem. Move the router. If the speed stays roughly the same, the wall isn't the problem — go back to Fix 2 or Fix 5.
When to add a cheap mesh node: if the router has to stay where the cable comes into the building (often a corner, often in a closet, often on a different floor from where your team actually sits), grab a $50–80 mesh node and put it halfway between the router and where your team works. Skip the all-in-one "range extender" boxes — they're usually worse than the router alone. A mesh node that pairs with your existing router is the right move.
This is the one everyone blames the router for but isn't. Your ISP — Comcast, Verizon, Spectrum, whatever — runs the line from the street into your building. That line and the box it ends at (the modem) are not your router, even though they're usually stacked next to each other. The symptoms that mean it's the ISP and not your router: every device in the office is bad at the same time, the bad moments all happen at the same hour every day, and the Wi-Fi was fine until 6 PM last Tuesday.
How to read the modem lights: most cable modems have four lights — power, downstream ("DS" or a down-arrow), upstream ("US" or an up-arrow), and online/status. After a clean boot, all four go solid within two minutes. "DS" solid means the modem is locked onto the ISP's downstream signal; "US" solid means it's successfully sending data back; "Online" solid means the ISP has accepted your modem onto its network. If any of those three is blinking, the problem is between the street and your building — your router can't fix it by rebooting.
What to tell the ISP so they don't bounce the call: when you call, say "My modem is showing a blinking downstream light," not "my Wi-Fi is slow." Frontline phone support will route that to a network-side team immediately, instead of sending you back to square one with "have you tried restarting your router?" Have the MAC address printed on the bottom of the modem ready — they'll ask for it regardless.
If you've tried the five fixes in order and the Wi-Fi is still dropping, the rest of the rabbit hole — DNS settings, wireless bridge mode, VLAN tags, mesh hand-off timing — takes more time than it's worth for a single small office.
Here's the honest answer: if your team has spent more than thirty minutes on Wi-Fi this month, that's usually a process problem, not a Wi-Fi problem. Once Wi-Fi reliably carries the tools your team uses, the bigger wins are in what those tools are doing — the same way businesses automate invoicing or onboarding or reporting, the right move is often a small workflow fix and a stable connection, not another afternoon googling. (Half the time an office that "has bad Wi-Fi" actually has a printer that's quietly losing its IP lease every ninety minutes — same root cause, and the fix is in our printer-offline guide.) When the connection is stable but the revenue cycle is what's leaking — late invoices not getting out because the SOS laptop is offline an hour a day — the same shape of fix is in our invoice-chasing guide.
We automate one business process for $89 — same-day fix or your money back. No retainer, no monthly fee. You describe what's broken, Nikita builds the fix.
Not sure what counts? See a real example: the Shopify-to-Sheets guide.
Start — $89OneFix is a small automation service for small businesses — we don't sell routers, mesh systems, or ISP plans. If you'd rather keep troubleshooting, our refund policy doesn't apply (you haven't paid us anything yet). Back to onefix.tech.