Go Loaded All articles
Performance

Bandwidth Diplomacy: How to Stop Flatmates Torching Your Ranked Connection

Go Loaded
Bandwidth Diplomacy: How to Stop Flatmates Torching Your Ranked Connection

Photo: Rodney J Herrera, CC BY 3.0, via Wikimedia Commons

There’s a special kind of silence that falls over a shared flat when your ranked match stutters, your ping spikes to 180ms, and a flatmate wanders past asking whether “the internet is being weird”. It isn’t weird. It’s a 4K stream, a Steam update and somebody’s phone backing up to the cloud, all having a party on your upstream. The good news: you don’t need a new router, a second line or a passive-aggressive note taped to the kettle. You need a bandwidth audit, a handful of fair rules and a ceasefire agreement everyone can live with.

Start with an audit, not an argument

Before you accuse anyone of “eating the bandwidth”, get evidence. Run a speed test on a wired connection when the flat is quiet, then again during the exact window you usually queue. Note the download and upload figures, but don’t stop there: run a bufferbloat test as well. A line that tests at 200Mbps down can still feel dreadful if latency balloons the moment somebody starts a video call.

Next, count the devices. Not just phones and laptops — consoles in rest mode, smart TVs, tablets, watches, doorbells, that old Sky box nobody admits to using. In a UK flat-share, the router admin page is often a museum of forgotten hardware. Log in, check the client list, and rename the worst offenders so you know what you’re looking at. If your router has a “traffic monitor” or “usage” tab, screenshot it during a ranked night. Nothing ends a group-chat row faster than a graph showing a 40GB game update starting at 8:05pm.

Also check your own setup before you point fingers. Wi-Fi is a lottery in a Victorian terrace or a new-build with foil-backed plasterboard. If you can, put your console or PC on Ethernet. If you can’t, move the router out of the cupboard under the stairs and use a cheap powerline kit only as a last resort — they’re better than nothing, but they’re not magic.

QoS without the router manual meltdown

Quality of Service sounds like enterprise networking. In practice, it’s just queue management. If your router supports “Smart Queue”, “SQM”, “Adaptive QoS” or “Gaming Priority”, switch it on and set your device to the highest priority. That won’t magically create bandwidth, but it stops your flatmate’s 4K binge from pushing your game packets to the back of the queue.

If your router is a basic ISP box, you may only get device prioritisation by MAC address. That’s still worth doing. Find your console or PC’s MAC address, add it to the priority list, and label it clearly — “Ranked PC — do not throttle” is a useful name. Some routers let you schedule a “gaming window” too; use it for the two hours you actually care about, not all day. Fairness matters if you want the agreement to stick.

A few zero-cost rules do most of the heavy lifting:

The ranked-night agreement

Rules written in a group chat get scrolled past. A one-page agreement on the fridge gets respected, or at least mocked into existence. Keep it short, specific and a bit ridiculous. Include the ranked window — say 7pm to 10pm on weeknights — the behaviours everyone agrees to, and what happens when somebody slips. The “penalty” should be social, not financial: make the next brew, take the bins out, or supply the snacks on the next ranked night.

Print two copies. One for the fridge, one for the router. Get everyone to sign it with a marker. Yes, it’s daft. That’s the point. A flat that can laugh about the agreement is a flat less likely to start a cold war over the Sky box.

£0 scripts that do the boring bits

You don’t need to code to keep the peace, but a couple of free automations help. On Windows, set your game downloads to a schedule and turn on “metered connection” for background apps during ranked hours. On consoles, disable auto-updates during the evening and set them to download overnight. These are switches, not scripts, and they cost nothing.

If you want proof of what’s happening, run a simple ping logger on a laptop or Raspberry Pi. A one-line cron job that pings your router or a known server every minute and writes the timestamp and latency to a text file is enough to show whether the problem is your line, your Wi-Fi or your flatmate’s 8pm “essential” download. No cloud subscription, no fancy dashboard — just a log you can screenshot when the next argument starts.

And put a calendar reminder in the shared flat calendar: “Ranked night — downloads paused, 4K off, router breathing.” It sounds small. It works.

When someone still eats the pipe

There will be a night when somebody forgets. Don’t open with “you’ve ruined my game”. Open with the evidence: “Ping spiked at 8:12pm, looked like a big download. Can we move that to after 11?” Most people comply when they can see the problem. If they don’t, escalate to the agreement, then to the router schedule. You’re not trying to win an argument; you’re trying to win a lobby.

A shared flat will never give you a dedicated fibre line and a soundproofed gaming room. But with a quick audit, sensible QoS and a fridge treaty, you can stop the bandwidth cold war before it costs you another rank. Gear up, level up — and maybe put the kettle on for the flatmate who finally paused their download.

All Articles

Related Articles

Plugged In, Let Down: A UK Field Test of Powerline Ping

Plugged In, Let Down: A UK Field Test of Powerline Ping

Nine Quid, No Wrist Drama: The Late-Queue Protocol That Keeps You Loose

Nine Quid, No Wrist Drama: The Late-Queue Protocol That Keeps You Loose

Thaw the Trigger Finger: A Twelve-Quid Cold-Hands Protocol for Winter Ranked

Thaw the Trigger Finger: A Twelve-Quid Cold-Hands Protocol for Winter Ranked