QoS (Quality of Service) manages how your router prioritises traffic during upload saturation. Proper QoS reduces bufferbloat, stabilises latency, and prevents gaming packets from being delayed by streaming or downloads. Incorrect QoS settings can increase latency instead of reducing it.
What QoS Does in a Gaming Network
QoS is a router-level traffic management system. When multiple devices use your connection, QoS controls upload queue size, prioritises specific devices or traffic types, and prevents large uploads from overwhelming smaller packets. Gaming packets are small and frequent. Without QoS, large uploads (cloud backups, video streaming, file transfers) fill the router's queue, increasing latency and jitter. QoS does not increase bandwidth. It redistributes available bandwidth more intelligently.
Why QoS Matters on Fibre
Fibre connections in South Africa often provide high download speeds, but upload speeds vary by package, multiple devices share the same upload pipe, and evening streaming increases congestion. When upload saturation occurs, bufferbloat develops. See: What Is Bufferbloat and How to Fix It QoS helps by limiting queue depth and ensuring gaming traffic is transmitted first.
How QoS Reduces Latency
Without QoS: upload begins (e.g., cloud backup), router queue fills, gaming packets wait behind bulk data, ping spikes. With QoS: upload begins, router limits queue size, gaming packets are prioritised, upload is slightly throttled, ping remains stable. Proper queue management prevents artificial delay.
Step-by-Step QoS Configuration
Step 1: Establish Baseline
- Disable QoS temporarily.
- Run a latency test with no background traffic.
- Run the same test during heavy upload.
- If ping increases significantly during upload, QoS is beneficial.
- See: How to Test Gaming Latency Properly
Step 2: Enable Smart Queue Management
- In your router, enable QoS or Smart Queue Management.
- Enter your actual upload speed.
- Set upload limit slightly below maximum capacity.
- Setting the limit slightly lower allows the router to control the queue.
Step 3: Prioritise Gaming Traffic
- Options vary by router, but typically: prioritise specific device (PC/Console) or prioritise gaming traffic category.
- Device-level prioritisation is often simpler and effective.
Step 4: Retest Under Load
- While someone streams or uploads, monitor in-game ping, observe jitter, and watch for packet loss.
- Ping should remain stable compared to baseline without QoS.
Step 5: Adjust If Necessary
- If latency worsens: confirm upload speed was entered correctly, ensure limits are not set too low, and avoid stacking multiple QoS systems.
- Incorrect configuration can introduce additional delay.
When QoS Does Not Help
QoS cannot fix international routing distance, undersea cable rerouting, server-side congestion, or packet loss occurring before local peering. If traceroute shows clean routing and no upload saturation, QoS is not the issue.
Definition
A router feature that manages traffic priority and queue size to prevent upload saturation from increasing latency. It does not increase bandwidth but controls packet scheduling to maintain consistent ping during congestion.
South African Gaming Context
Most gaming infrastructure is hosted in Johannesburg. Stable local routing is common. However, multi-device households, evening streaming, and cloud storage uploads often trigger upload saturation. For CPT players routing to JHB, small latency increases from bufferbloat are amplified due to added geographic delay. Queue management is often more important than higher Mbps.
Common QoS Mistakes
- Setting incorrect upload speed
- Over-prioritising too many devices
- Using outdated firmware
- Running double NAT with two active QoS systems
- QoS must be configured once, cleanly, and validated under load
When to Escalate
Escalation is not appropriate if ping spikes only during uploads, wired testing improves performance, or no packet loss appears before local peering. Escalation may be appropriate if packet loss appears consistently before peering or latency is high even without congestion. QoS addresses home-level congestion, not upstream routing.