Person on a video call at a home workspace using a laptop

Starlink QoS: How to Prioritize Calls and Gaming on a Busy Network

Speed & Performance

A busy Starlink connection can feel unreliable even when the dish and service are working normally. A large backup, update or upload may fill the router's queue, making a work call or game feel delayed.

Quality of Service (QoS), traffic prioritisation and Smart Queue Management (SQM) are different names used by different routers for managing that traffic. They can help a busy home network, but they cannot repair an obstruction, an outage, weak Wi-Fi or congestion outside your home.

This guide shows how to decide whether QoS is appropriate, set it up without creating a second routing problem, and test whether it actually improves the calls or games that matter.

Check the connection before changing QoS

Start with evidence so you do not use QoS to mask a different fault.

Open the Starlink app and check for outages, obstruction warnings and equipment alerts.
Choose one device and one network path for every comparison. Ethernet is useful when available because it removes most Wi-Fi uncertainty.
Run a quiet baseline while large transfers are paused. Record download, upload, latency, jitter and packet loss when the test provides them.
Create one controlled load, such as a cloud backup or operating-system download that you can stop.
Repeat the same test while the load is running and note what happens to the call, game or other interactive task.
Stop the transfer and confirm whether the connection becomes responsive again.

QoS is worth investigating when the connection is usable while quiet, becomes noticeably delayed under household traffic, and recovers when that traffic stops. A connection that is poor while idle needs a different diagnosis first.

Know where QoS can live

The Starlink app and router features vary by hardware generation, firmware and setup. Do not assume that every Starlink router has a general QoS menu.

You may have one of these arrangements:

Starlink router only: Use the controls it actually exposes, such as pausing a device or scheduling large activities if available. Do not invent a QoS rule that the router does not support.
Starlink router plus your own router: Decide which device is doing the routing. Two routers both performing NAT can create double NAT and confusing device rules. Put traffic management on the router that controls the home network.
Your own router in the main role: A compatible router, mesh system or firewall may offer QoS, SQM or traffic shaping. Menu names differ, so follow that vendor's current instructions and change one setting at a time.

Bypass mode is a design choice, not a QoS requirement. Do not switch modes solely because one test showed delay. First confirm that the local queue is the likely cause and that you understand how the change affects mesh, IPv6, app access and other services.

Choose what to prioritise

Keep the first rule small and easy to remove. A work laptop, desk phone, console or gaming PC is usually easier to identify than every application in the house.

Useful starting choices include:

Prioritise the device used for an important call or game.
Shape upload as well as download when the router supports both; a full upload can make interactive traffic wait.
Prioritise one or two real-time devices rather than every device.
Leave large backups, game updates and bulk sync traffic at normal priority or schedule them outside important sessions.
Prefer device-based rules when application detection is unreliable or traffic is encrypted.
Avoid marking streaming, downloads and all household traffic as high priority. That removes the distinction QoS needs to make.

QoS cannot create more bandwidth. It only decides how available capacity is shared when several activities compete.

Set conservative bandwidth values

Some routers ask for an upload and download limit before they can manage the queue. Use measurements from several quiet and busy periods rather than the best result from one speed test.

Start below the lowest repeatable rate you measured.
Shape upload if the router allows it; upstream capacity is often the first part to become crowded.
Follow the router's required units carefully, especially when it asks for megabits per second or kilobits per second.
Leave enough headroom for changing Starlink speeds and normal protocol overhead.
Record the original values before saving the change.

A setting that is too high may leave the queue unmanaged. A setting that is too low can reduce usable throughput and make the connection feel slower. The useful setting is the one that keeps interactive traffic responsive during the household's real workload.

Test one change at a time

Use the same device, server or application and traffic pattern for a fair comparison.

Run the quiet baseline again.
Start the same single background transfer.
Join a short work call or run the same game activity.
Record latency, jitter, packet loss and how the call or game feels.
Enable one QoS or SQM rule.
Repeat the same loaded test for the same amount of time.
Stop the load and confirm the normal result returns.
Keep the change only if the loaded experience improves without an unacceptable throughput loss.

If the router offers separate device priority and queue management, test the queue setting first. Then add a single device rule only if the evidence shows it helps. Keep a note of each change so you can undo the last step when a result gets worse.

Match the result to the likely cause

Calls or games improve only while another device is transferring: QoS or SQM may be helping a local queue.

The problem appears only in one room or on one mesh node: Improve Wi-Fi placement or use a wired path before changing internet traffic rules.

Every device becomes slow at the same time, including a wired device: Check the Starlink app, dish view, power and cables, and compare the time pattern over more than one session.

The connection stays poor with no background traffic: Investigate the underlying service, Wi-Fi, device, obstruction or remote-server problem. QoS is unlikely to be the main fix.

Only one game or call service has trouble: Check its service status and test another destination. Different services take different network paths.

The result improves only after a very large speed reduction: Recheck the bandwidth values and units. A rule that works by wasting most of the connection may need a better measurement or a simpler traffic schedule.

Avoid common QoS mistakes

Do not enable QoS, change DNS, switch router modes and replace Wi-Fi equipment at the same time.
Do not assume a Starlink firmware update gives every customer the same router controls.
Do not run several speed tests while trying to measure a loaded connection.
Do not factory-reset working hardware before recording the current settings.
Do not use QoS to work around an obstruction, outage or damaged cable.
Do not create two competing priority systems on two routers.
Do not expect QoS to remove satellite, peak-period or remote-server latency.
Do not leave a complicated rule set in place when a scheduled backup or one simple device rule solves the problem.

Quick checklist

Before an important call or gaming session:

Check the Starlink app for active alerts.
Use Ethernet or the strongest practical Wi-Fi path.
Pause or schedule large uploads, backups and updates.
Confirm that only one router is managing the home network.
Test a quiet baseline and a loaded comparison.
Shape upload as well as download when supported.
Prioritise only the device or traffic that needs low delay.
Keep a record of the setting that worked so it can be restored after a router reset.

The goal is not the highest possible speed-test score. It is a connection that stays responsive while your household is doing normal work, entertainment and backups.

Get One Month of Starlink Free

Order through my referral link and activate your service. Your second month of Starlink service will be free.

Claim Your Free Month

Related Starlink guides

This guide is general information. Router menus, Starlink hardware, plan features and available performance can vary by model, location and software version.