Get One Month of Starlink FreeSPECIAL OFFER: GET A FREE MONTH OF STARLINK >
Wireless router and cable representing Starlink hardware and accessories

Starlink Bufferbloat: How to Diagnose and Reduce Lag During Downloads

Speed & Performance

Back to Speed & Performance

Bufferbloat is delay caused by a network queue filling up when a connection is busy. On Starlink, it often feels like this: the connection looks fine when nobody is using it, but calls, games and page loads become sluggish as soon as another device starts a large upload or download.

This does not automatically mean the dish is faulty or that you need a faster plan. The first job is to reproduce the problem with a controlled comparison, then fix the part of the network that the evidence points to.

Claim Your Free Month

Check the basics before testing

Use the same device and network path for every comparison. If possible, test once over Ethernet or close to the Starlink router so weak Wi-Fi does not hide the result.

Before starting:

  • Check the Starlink app for an active outage, obstruction warning or equipment alert.
  • Note the time, the device, whether it is wired or on Wi-Fi, and what the household was doing.
  • Pause non-essential downloads and uploads for the quiet baseline.
  • Close extra browser tabs and applications that may be using the connection.
  • Do not factory-reset the router or change several network settings before you have a baseline.

A speed test can use a meaningful amount of data. Cloudflare notes that its test may consume up to 200 MB, so avoid running repeated tests on a limited allowance.

Run an idle and loaded comparison

You are looking for a repeatable change in latency when the connection is busy, not the highest possible download number.

  1. Run an idle baseline. With other traffic paused, use the same device to run a speed and quality test. Record download, upload, latency, jitter and packet loss where the test provides them.
  2. Create controlled load. Start one large, legitimate transfer that you can stop, such as a cloud backup or an operating-system download. Do not start several transfers at once.
  3. Repeat the quality check. While the transfer is running, make a short call, open several normal pages or run the same network-quality test. Note how latency and jitter change under load.
  4. Stop the transfer. Wait for the network to settle, then repeat the test once more.
  5. Repeat at a different time. A second comparison helps separate queueing delay from a busy Starlink cell, a game server problem or a one-off Wi-Fi fault.

Bufferbloat becomes more likely when the idle result is usable, latency rises sharply during the upload or download, and the problem clears soon after the traffic stops. A slow or unstable result even while the connection is idle points to a different problem.

Separate Wi-Fi delay from queueing delay

A busy Wi-Fi link can look exactly like an internet problem. Run the same comparison in this order:

  • Test near the router on the device's normal Wi-Fi band.
  • Test over a supported Ethernet path if one is available.
  • Repeat the loaded comparison without changing the transfer or test server.
  • If only the distant Wi-Fi test suffers, improve router or mesh placement before changing Starlink settings.
  • If wired and nearby Wi-Fi devices show the same loaded delay, investigate the router queue, household traffic and the Starlink connection itself.

For a fair comparison, disable Wi-Fi on a laptop or console when testing Ethernet. Otherwise the device may silently continue using the wireless path.

Fix the least complicated cause first

1. Reduce background traffic

Uploads are often the most disruptive because they can fill a smaller upstream queue. Check for:

  • Cloud photo and file backups
  • Security-camera uploads
  • Large file synchronisation
  • Video uploads or livestreams
  • Game, console and operating-system updates
  • Multiple 4K streams during a call

Pause one activity and repeat the same test. If the call or game immediately improves, schedule that transfer outside important work or reduce its upload rate if the application allows it.

2. Use queue management on a compatible third-party router

Some third-party routers offer SQM, QoS or traffic shaping. These features control how much traffic is allowed into the queue and can reduce delay while the connection is busy.

If you use one:

  • Change one setting at a time.
  • Start with a conservative bandwidth value below the lowest reliable speed you measured, not the best speed from one test.
  • Shape upload as well as download when the router supports both.
  • Prioritise the work device or call traffic only when you understand what the rule does.
  • Retest idle and loaded latency after each change.

Starlink hardware, router generations and plan options vary. Do not assume the Starlink app exposes the same queue controls as a third-party router. If you are already using your own router, keep the routing and traffic-shaping design simple and avoid changing to bypass mode solely because a test showed queueing delay.

3. Improve the local path

If the loaded problem appears only on Wi-Fi, move the router into an open, central position, reduce unnecessary mesh hops and use a wired backhaul where practical. A new mesh node may improve coverage, but it will not fix a queue that is already full at the internet-facing router.

4. Retest under the conditions that matter

After each change, repeat the same idle and loaded comparison. A fix is useful only if it improves the call, game or work task that originally exposed the problem. Keep the result that was working before you try another adjustment.

Know when it is probably not bufferbloat

Look elsewhere when:

  • Latency is poor even with no household traffic.
  • The Starlink app shows an obstruction, outage or equipment alert.
  • Every device loses service completely rather than becoming slow under load.
  • Only one game, website or remote service has a problem.
  • The issue appears only in a weak room or on one mesh node.
  • The connection remains bad after all background transfers stop.

For these cases, compare a nearby or wired device, inspect power and cables, check the app and preserve timestamps before contacting support. An evening slowdown can also reflect peak demand; it is not proof of bufferbloat by itself.

Keep useful evidence

Record a short table with:

  • Date and time
  • Device and wired or Wi-Fi path
  • Idle latency, jitter, packet loss and throughput
  • Loaded latency, jitter, packet loss and throughput
  • What created the load
  • Whether stopping the load restored normal performance
  • Starlink app alerts or obstruction events

This makes it easier to tell the difference between a household queue, weak Wi-Fi, a Starlink interruption and a remote service problem.

Avoid these common mistakes

  • Do not treat one speed test as a diagnosis.
  • Do not run several speed tests at once while trying to measure a busy connection.
  • Do not change DNS, MTU, router mode and Wi-Fi channels all together.
  • Do not buy a faster plan solely because latency rises when a backup runs.
  • Do not factory-reset working hardware before collecting evidence.
  • Do not assume a game ping is the same as a speed-test latency; they use different routes.

The practical goal is a connection that stays responsive during the traffic your household actually creates. A modest, repeatable improvement in loaded latency is more valuable than a single spectacular download result.

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

Get One Month of Starlink Free

Related Starlink guides

References

This guide is general information, not a guarantee that every Starlink router or third-party router offers the same controls.