The complaint almost always takes the same shape: the video call breaks up exactly when someone at home starts a large download. The subscription speed hasn't changed, and a speed test still looks fine when run at a quiet moment.

What changed isn't the speed. It's the queue.

A network is a queue, not a pipe

The "pipe" image suggests bandwidth is shared evenly and smoothly. What actually happens looks more like a service counter: data arrives in small pieces, and when it arrives faster than it can be sent out, the rest waits in the router's buffer.

A large download doesn't wait politely. It sends as much as it's allowed to, and within seconds that buffer is full. Your video call's packets then join the back of a long line, they still arrive, just late.

Half a second late means nothing to a file being downloaded. To a voice, it's an audible break. The difference between the three measurements people routinely confuse is covered in the guide to bandwidth, latency, and throughput.

This symptom has a name of its own: bufferbloat: oversized buffers making latency spike precisely when the network is busy. And that is what QoS actually fixes.

What QoS actually does

QoS does two things, and both need understanding so the expectation is right:

  • It holds back slightly below capacity. The router deliberately sends a little slower than the line can manage, so that the queue that matters sits in your router, not in the provider's equipment, which you can't configure.
  • It reorders that queue. Once the queue is under its own control, the router can put small time-sensitive packets ahead of large ones that don't mind waiting.

The trade is honest: you give up a little peak speed for steadiness. Peak download speed drops by roughly the margin you set aside, usually ten to fifteen per cent. Video calls stop stuttering. For nearly every household, that trade is worth making.

Three forms you'll meet

Menu names differ between brands, but what's underneath falls into three forms.

Per-device priority

You choose which device goes first, the work laptop, say, ahead of the television. Easiest to reason about, hardest to get wrong, and enough for most homes. It requires the device to be recognised consistently; some phones randomise their MAC address, so that needs turning off on the home network or the rule quietly stops applying. That behaviour is covered in the guide to MAC address filtering.

Per-traffic-type priority

The router tries to identify what's a video call, what's a game, what's a download. Tidy in theory. In practice nearly all traffic today is encrypted, and the router's guess often misses, a work meeting mistaken for entertainment streaming, then placed at the back.

Smart queueing with no rules at all

Names vary: Smart Queue, SQM, Adaptive QoS, or fq_codel on open firmware. It asks you to write no priority list whatsoever. The router simply prevents any single flow from dominating the queue for long.

For most people this third form is the one that helps most: and demands the least upkeep. If your router has it, start there and leave everything else alone.

Setting it up

  1. Measure the real speed first at a quiet time, and note both the download and upload figures.
  2. Open the router's admin page and look for QoS, Bandwidth Control, or Traffic Management.
  3. Enter roughly 85–90 per cent of those figures as the limit. That number is what moves the queue into your router. Entering 100 per cent leaves QoS doing almost nothing.
  4. Prioritise the upload side. On home connections upload is far smaller and fills first, and it's what ruins video calls. The reason is covered in the guide to why upload is slower than download.
  5. Test it deliberately. Start a large download, then make a video call on another device. If the call stays clear, the setting is right.

If your measured speed varies, common on wireless and cellular links, pick a figure near the worst case, not the best.

An example: a test at a quiet hour gives 48 Mbps down and 19 Mbps up. Enter about 42 and 17 Mbps. Measure again around eight in the evening. If the evening figures are much lower, use those, because that's exactly when the house is busiest.

Checking for bufferbloat without extra apps

On a Windows laptop, open Command Prompt and run ping -t 8.8.8.8. Leave it running, then start a large download or a video upload to cloud storage from another device. Watch the time figures. If they jump from the teens of milliseconds into the hundreds while the transfer runs, that's bufferbloat. Repeat with QoS switched on; the jump should be far smaller. Reading ping output is covered in the guide to using ping and traceroute.

On provider ONTs and routers common in Indonesia

Most Indonesian homes use an ONT installed by the provider, such as the ZTE F609 or F670L found in many IndiHome customers' homes, the Huawei HG8145V5, or the Fiberhome HG6243C. These devices are built to terminate fibre and broadcast Wi-Fi, not to manage queues. The account handed to customers rarely shows a full QoS menu, and smart queueing such as SQM is usually not available.

The sensible route is your own router behind the ONT, with the queue managed there. The layout is covered in the guide to ONT bridge mode and your own router. One condition is often missed: every device must connect through your router. If the ONT's built-in Wi-Fi is still on and some of the family use it, their traffic skips your router's queue entirely and still competes for the line in front of it. Turn the ONT's Wi-Fi off, or make sure nobody uses it.

Menu details for home routers such as TP-Link are in the guide to limiting Wi-Fi speed.

MikroTik in warung, boarding houses, and RT/RW net

MikroTik is widely used in small Indonesian businesses for its hotspot and voucher features, see the guide to MikroTik hotspots for business. RouterOS 7 offers the fq-codel and CAKE queue types, the same smart queueing described above. Neither switches itself on. You create the queue type, then use it in a Simple Queue or Queue Tree.

The trap that most often makes the setting seem to do nothing is FastTrack. MikroTik's default configuration includes a FastTrack rule for established connections, and Simple Queues don't limit FastTracked traffic. Two choices: disable that rule if you use Simple Queues, or use a Queue Tree with an interface as its parent, which still works with FastTrack on. Smart queueing also costs CPU, so on an entry-level MikroTik with a large subscription, check the CPU load after enabling it.

Examples at home and in business

SituationTypical symptomWhat to set
Home with one person in online meetings, children in online school, TV onMeeting audio breaks up when another phone backs photos up to the cloudSmart queueing with the upload limit at 85–90 per cent; failing that, prioritise the work laptop
Children gaming online while parents watch videoGame ping spikes whenever a video startsSmart queueing; QoS won't help if ping is already high when the house is quiet
Boarding house (kos) with 10–15 rooms on one subscriptionOne resident downloads a large game and every room slowsSmart queueing that shares fairly per flow, then per-room limits if still needed
Café with customer Wi-Fi and a tillQRIS or card-terminal payments slow when the café is busyTill and EDC terminal first; guest Wi-Fi limited and kept separate

For gaming, first tell apart spikes caused by queueing from ping that's high simply because of distance to the server, as covered in the guide to high ping in games. For boarding houses and cafés, network layout is in the guide to Wi-Fi for boarding houses and the guide to networking tills and EDC terminals.

When QoS won't help

Several situations look like priority problems and aren't:

  • Weak Wi-Fi signal. QoS manages the queue on the internet side, not the air between router and device. What to check is in the guide to full signal but slow internet.
  • Congestion at the provider. If it slows at the same hour every day across every device, the queue isn't in your house, the guide to internet slow at certain hours covers how to tell.
  • Too many devices for one router. The limit there is device count, not ordering.

One more thing worth stating plainly: router QoS only governs traffic passing through that router. It cannot ask a service out on the internet to send faster.

Closing notes

QoS adds no speed. It moves the queue somewhere you can control, then makes sure small time-sensitive things don't end up behind a large download.

If your router offers smart queueing, switch that on and stop there. If not, per-device priority is enough for almost any home, and the side that most needs managing isn't download but the much narrower upload.

And if the network never felt congested to begin with, QoS will change nothing. Turning it on only adds one more setting to remember on the day something behaves oddly.

Frequently asked questions

What is QoS on a router?

QoS (Quality of Service) decides which traffic goes first when the network is busy. It doesn't add speed; it only changes the order of the queue once capacity is already full.

Does QoS make the internet faster?

No. Total speed stays the same. What changes is how it feels: video calls and games stay steady because they no longer wait behind a large download.

When is QoS not worth enabling?

If your connection is comfortably larger than daily use and never feels congested, QoS will change nothing. It only shows its value on connections regularly pushed to their limit.

Should I prioritise devices or traffic types?

At home, prioritising devices is easier to reason about and goes wrong less often. Per-traffic-type rules look tidier in theory, but many routers misidentify modern apps, which are encrypted end to end.

Can QoS be set on the ONT supplied by IndiHome or other Indonesian providers?

Usually not adequately. The customer account on ONTs such as the ZTE F670L or Huawei HG8145V5 rarely shows a full QoS menu, and smart queueing is generally absent. Put your own router behind the ONT, configure QoS there, and make sure no device is still using the ONT's built-in Wi-Fi.