The evening collapse is often physics, not a fault code
It is a familiar story: the connection feels fine in the morning, and after dinner everything buffers. The usual suspects are a tired router, a “bad” ISP, or the classic turn‑it‑off‑and‑on again. Some of that can help, but the pattern that tracks the clock more than the weather is usually contention in the radio spectrum, especially on 2.4 GHz where the channels overlap like crowded tables at a market. On cable or fibre to the home from Eir or Vodafone in Ireland, or Openreach-based BT in the UK, the link to the cabinet or exchange can be clean while the last metres inside your home are a shouting match.
What actually happens on 2.4 GHz
Consumer Wi‑Fi on 2.4 GHz in Europe typically uses a slice of band where only three 20 MHz channels (1, 6, 11) do not overlap. Every neighbour on an overlapping setting adds noise. Add microwave ovens, baby monitors, and cheap IoT devices that only speak 2.4 GHz, and the modulation rates drop. The access point then spends more time on retransmissions, and latency spikes even when the speed test still shows a “fine” number every now and then. This is not something the ISP can “boost” with a line reset if the last hop is a congested airspace.
Why your TV stick makes it worse, quietly
A 4K stream in the same room is not evil by default, but it is hungry. It lives next to a phone on a video call, a child on a tablet, and three background sync jobs. If any of that traffic is forced to 2.4 GHz because 5 GHz was never configured or a device is too old, you feel it first where the signal is already weak. Mesh systems help coverage; they are not a spell against spectrum overlap. A mesh node that repeats 2.4 congestion still repeats the problem.
Move what you can to 5 GHz and wire what never moves
5 GHz offers more non-overlapping 20 MHz channels in practice and shorter range, which is a feature: your neighbours’ signals fade sooner. The practical steps are dull but effective. Rename SSIDs with care so you do not strand devices; if you use one name for both bands, make sure the client is actually attaching to 5 GHz in the problem room. For the TV, desktop, and games console, Ethernet (or a small switch behind the TV) removes entire classes of problems. A £20–40 cable in a UK chain store or a €15–25 one from a local shop is cheaper than another Saturday lost to stuttering.
Pick a channel, but pick it with sense
Auto channel works until everyone’s auto at dinner picks the same winner. A manual 20 MHz width on 2.4, on channel 1, 6, or 11, and a scan from a phone app to see the densest point in your area is still good hygiene. If you are on 40 MHz on 2.4 in a town house in Dublin, you are usually donating airtime to the neighbourhood. For 5 GHz, a wider channel is fine in many suburban homes, but in an apartment in Manchester you may be happier on 20/40 than on 80 if the environment is busy.
Mesh, when the house wins over the budget
A single router at the front hall in a long cottage will never cover the attic office without help. A modest mesh — two or three units from a line that receives security updates, not a forgotten three‑year‑old “repeater” with no patch path — is often the right call. The goal is a stable backhaul: Ethernet backhaul is best, dedicated 5/6 GHz second, and repeating the same 2.4 as the only path last. Look at LED behaviour at peak times. If the mesh hop is saturated, a cable run along the skirting board is still a professional tool.
QoS: stop the one chatty client from the rest
Quality of service in the router, when it exists and is set sensibly, can protect voice and video on a contended link. The UI varies wildly, but the question is the same: “What is allowed to shove the queue when the line is full?” A misconfigured QoS can make things worse, so take a photo of defaults, change one thing, and test. For families with a Vodafone-supplied all‑in‑one, some features are simply hidden. A standalone AP or a budget router in bridge mode is sometimes the cheaper sanity fix.
The weekly reboot is not a religion
Restarting a router clears stuck states. Doing it on a timer every night is a patch for hardware that is overheating or leaking memory, not a lifestyle. If you need a scheduled restart for stability, you likely need a firmware update, better ventilation, or a box that is not a decade old running every guest Wi‑Fi feature at once. Fibre customers still need good LAN and DNS; when slowness is only DNS or only one site, the radio story is a red herring and you chase resolver and path next.
A sane checklist you can do before you buy anything
- Note whether pain tracks 8–10pm more than weekend afternoons — that points to RF and load.
- On a problem device, check band and RSSI if the OS exposes it.
- Move the worst offenders to 5 GHz or wire.
- Channel and width on 2.4: conservative beats aggressive in dense areas.
- If coverage is the limiter, plan mesh with cabled backhaul if you can.
- QoS last, and only after a stable baseline.
If this is too much hassle, we can do it for you — get a quote.