Why your wifi slows down when the neighbours move in

The signal bars are lying to you

Most people troubleshoot a slow wifi connection by staring at the signal strength icon. Full bars, so the problem must be somewhere else, right? Wrong assumption, and it’s the first thing worth unlearning. Signal strength measures how loud your router’s radio is at your device. It says nothing about how much of the airtime you’re actually getting to use.

Wifi doesn’t work like a dedicated cable. It’s a shared radio medium, and “shared” is doing a lot of work in that sentence. Every device on the same channel, in range of each other, is taking turns talking. When a new household moves in next door and their router powers on, they don’t cost you signal. They cost you turns.

Wifi is a talking stick, not a pipe

The mechanism underneath almost all consumer wifi is called CSMA/CA, carrier-sense multiple access with collision avoidance. Before any device transmits, it listens. If the channel is busy, it waits. If it’s clear, it sends, then waits for an acknowledgment before sending the next chunk. This is deliberately conservative, because two devices transmitting on the same channel at the same time garbles both signals and neither gets through.

That listen-wait-send cycle means the channel behaves like a talking stick passed around a room, not a highway with lanes for everyone. Every additional network on your channel, whether it’s your laptop, your smart TV, or your neighbour’s entire household of phones and streaming boxes, is another participant waiting for the stick. More participants means more waiting, more retransmits when collisions do slip through, and a real drop in the airtime any single device gets, even though the raw signal reaching your laptop hasn’t changed at all.

This is why “my bars are full but Netflix keeps buffering” is such a common and confusing complaint. Signal quality and channel congestion are two different problems, and the second one has nothing to do with distance from the router.

There are only three usable channels on 2.4GHz

Here’s the part that makes new neighbours specifically painful. The 2.4GHz band, which is still the default for a huge number of consumer routers, IoT devices, and anything trying to maximize range through walls, only has three channels that don’t overlap and bleed into each other: 1, 6, and 11. Everything in between smears energy across adjacent channels too.

In a dense apartment block, dozens of routers are all fighting over three slots. Most consumer routers ship in “auto channel” mode, which sounds smart but in practice just means the router picks whatever looks quietest at boot time and rarely re-evaluates. Add one more strong router next door on your channel and the auto-selection logic doesn’t proactively rescue you. You just inherit a noisier channel until you manually intervene or reboot at the right moment.

5GHz is a partial escape, because it offers far more non-overlapping channels, but it comes with a catch: a chunk of the best 5GHz spectrum is DFS, dynamic frequency selection, reserved to avoid interfering with radar systems. Cheap routers and many client devices either don’t support DFS channels or avoid them by default because the compliance requirements are more complex. The result is that even on 5GHz, everyone’s equipment tends to cluster on the same small handful of “safe” non-DFS channels, recreating the same congestion problem one band up.

Modulation drops before you even notice

The other piece people miss is that wifi doesn’t fail cleanly. When the noise floor on a channel rises, whether from a new neighbour’s router, a microwave, a baby monitor, or a Bluetooth speaker, your device and the access point negotiate down to a more robust but slower modulation scheme to keep the connection reliable. This happens automatically and silently. You don’t see an error message. You just see a video that used to load instantly now take a few seconds to buffer, or a video call that starts stuttering during peak evening hours.

This is genuinely the same tradeoff that shows up in a completely different context: when you’re running dense wireless gear at scale, like banks of access points and cellular modems for infrastructure work, the number one silent killer of throughput is never “not enough signal.” It’s contention. A device that reports strong signal and terrible throughput almost always has a noisy or congested channel underneath it, not a coverage problem. The fix in that world is the same one that applies in a home network: stop trusting the bars, and go look at what’s actually competing for airtime.

Why it gets worse specifically at certain hours

If the slowdown tracks with a new neighbour rather than being constant, there’s usually a pattern to when it bites. Evenings and weekends are worse because that’s when every household in range is streaming, gaming, and video calling simultaneously, all competing for the same three-and-a-bit usable channels. A neighbour’s smart home devices, security cameras in particular, often transmit continuously rather than in bursts, which eats into shared airtime around the clock rather than just at peak hours.

Router placement matters here too, in a way people don’t expect. A router pushed to maximum transmit power to cover a large apartment doesn’t just reach further, it also raises the noise floor for everyone nearby on the same channel, because CSMA/CA requires devices to defer to any signal they can hear, not just the one they’re trying to talk to. Two routers both cranked to max power fighting for the same channel produce worse outcomes for both households than two routers running at a sane, appropriately sized power level.

What actually moves the needle

None of this is solved by buying a more expensive router with bigger antennas, if the underlying problem is channel contention rather than coverage. A few things that address the actual mechanism:

Manually setting your channel instead of leaving it on auto, after checking which channels are least occupied in your area with a wifi analyzer app, gives you more control than waiting for firmware to notice and react.

Moving latency-sensitive or bandwidth-heavy devices to 5GHz, and reserving 2.4GHz for things that genuinely need the range, like a smart plug in a back room, reduces how many devices are fighting over the scarcer band.

Wiring anything stationary, a desktop, a streaming box, a game console, takes it off the shared radio medium entirely. Every device you move to ethernet is one less participant competing for the talking stick, which directly helps everyone left on wifi, including your neighbours.

Narrower channel widths on 5GHz, 40MHz instead of 80MHz, sound like a downgrade but often perform better in dense areas, because a narrower channel is less likely to overlap with what neighbouring routers are using and picks up less interference in exchange for a small ceiling on peak speed you probably weren’t reaching anyway.

The honest limit

It’s worth being straight about this: some of the congestion is genuinely outside your control. You can’t stop a neighbour from buying a router that blasts on channel 6 at full power, and you can’t force the building to coordinate channel assignments the way a well-run office network would. Shared spectrum means your experience is partly a function of decisions made by people you’ll never talk to. The tools above shrink the problem and often fix it entirely, but in a sufficiently dense building, wifi is a negotiation you’re always having with your neighbours whether you know it or not.

If you’re curious about the other invisible machinery running underneath the internet you use every day, from how platforms fingerprint your device to how traffic gets routed and rerouted at scale, there’s more of that on the Hidden Internet home page.

Get new guides and videos first — join the Telegram channel.