Starlink diagnostics guide
Starlink Packet Loss: How to Test It and How to Fix It
Quick answer:
Packet loss is the quiet killer of Starlink calls and games — it barely dents your download number but wrecks anything real-time. A browser speed test cannot confirm it, so measure it with a continuous ping on Ethernet, learn which brief handoff loss is normal, and fix the real causes: obstructions first, then WiFi, then your router.
What packet loss actually is — and why it hurts so much
Packet loss is exactly what it sounds like: some of the small data packets your connection sends never arrive at the other end. Every internet link loses a few packets occasionally, and for a download it barely matters — the missing pieces are simply re-sent and the file still completes. The problem is real-time traffic. A video call, an online game, or a voice chat has no time to wait for a re-send. A lost packet is gone, and you feel it as a frozen frame, a robotic voice, a rubber-banding character, or a sudden ping spike.
This is why people are so often confused by Starlink packet loss. Their speed test looks healthy, downloads are quick, yet calls stutter and games feel broken. Throughput hides packet loss. If your download is fine but live sessions fall apart, packet loss and jitter are almost always the reason, and they need a different test than a speed number.
The honest part: a browser speed test can’t confirm packet loss
We will be straight with you, because guessing here wastes hours. Our Starlink speed test measures download, upload, ping, and jitter from your browser. Those are strong indirect signals — when packet loss is present, ping and jitter usually climb with it. But a browser cannot run the sustained, low-level probing needed to report a trustworthy packet-loss percentage. Anyone who tells you a one-tap web widget precisely measured your Starlink packet loss is overselling it.
So use the two tools for what each does well. Run our speed test to spot a problem in seconds — a high jitter reading is a red flag — then confirm actual packet loss with a continuous ping, described next. Our methodology page spells out exactly what we do and do not measure, and why.
How to test Starlink packet loss the right way
The reliable, free method is a continuous ping to a stable host, run long enough to catch the intermittent drops Starlink is known for. Test on Ethernet whenever possible so you are measuring the satellite link, not your WiFi. Here is the exact process:
| Method | How to run it | What it tells you |
|---|---|---|
| Windows continuous ping | Command Prompt: ping -t 8.8.8.8, let it run ~5 min, then Ctrl+C | Summary line shows % packets lost |
| macOS / Linux ping | Terminal: ping 8.8.8.8, wait ~5 min, then Ctrl+C | Prints packet-loss % and timing on stop |
| Starlink app → Statistics | Open the app, view Statistics / uptime and obstruction history | Shows dropped time, obstructions, outages |
| Longer sampling (advanced) | Extended ping or a dedicated monitor over 30+ min | Catches rare, periodic handoff drops |
Pinging a well-known resolver such as 8.8.8.8 is fine for a loss check. Run the test while you actually use the connection so real traffic and handoffs are represented.
Read the summary, not individual replies. A single missed reply proves nothing; the percentage across hundreds of packets is the signal. And cross-check the jitter reading on our speed test: high jitter alongside a dropping ping is a strong, consistent story.
What counts as “normal” Starlink packet loss
Starlink is a moving network. Your dish hands the connection from one satellite to another every few seconds, and each handoff is a moment where a packet can slip. Because of that, brief, occasional loss is expected and usually harmless for browsing and streaming. A short spike as a cloud burst crosses the wrong part of the sky is also normal. You should not chase perfection to zero.
The line to watch is persistence. If a wired continuous ping keeps dropping packets minute after minute, with a clear sky, that is not normal handoff behavior — it is a real fault worth fixing. The same is true if loss lines up tightly with the obstruction events shown in the Starlink app. Judge the pattern over time, not one bad second, exactly as you would when diagnosing a general Starlink slowdown.
The real causes of Starlink packet loss
1. Obstructions and marginal sky view (most common). A branch, roofline, chimney, or pole that blocks even a slice of the sky forces extra handoffs and drops. It rarely causes a full outage — it causes exactly the intermittent, every-few-minutes loss that breaks calls. Check what the dish sees with our obstruction checker before touching anything else, and read the obstruction guide for placement fixes.
2. WiFi, not the satellite. If you only see loss over WiFi, the satellite link is fine and your indoor radio environment is the problem — distance, walls, interference, or a weak client radio. Confirm by repeating the ping on Ethernet. 3. Congestion. During the busy 7–11pm window a saturated cell can shed more packets. 4. Router stress. A cheap or overloaded router juggling cameras, VPNs, and QoS can drop packets locally. 5. Cabling. A damaged or loosely seated dish cable produces erratic loss that mimics an obstruction.
How to fix Starlink packet loss, in order
| Step | Do this | Fixes |
|---|---|---|
| 1. Clear the sky | Check obstructions; raise or relocate the dish for a wide, clean view | Handoff drops, intermittent loss |
| 2. Isolate WiFi | Re-run the ping on Ethernet; if WiFi-only, improve placement or add mesh | Room-specific loss |
| 3. Reboot & check bypass | Power-cycle; if using a third-party router, confirm bypass mode | Router contention, double-NAT |
| 4. Inspect the cable | Re-seat connectors; look for kinks, pinches, or water ingress | Erratic hardware loss |
| 5. Retest & escalate | If wired loss persists with a clear sky, capture before/after and contact support | Genuine faults |
For gamers, packet loss matters even more than raw speed, and a few extra fixes help — see the Starlink for gaming guide, and if your issue is more about connection type than loss, the Starlink NAT type guide covers the CGNAT quirks that break some multiplayer titles.
Packet loss vs latency vs jitter — don’t confuse them
These three get lumped together, but they are different failures. Latency (ping) is how long a packet takes to make the round trip. Jitter is how much that time varies from packet to packet. Packet loss is how many packets never arrive at all. You can have low latency and still suffer packet loss, and it is entirely possible to have a great download number with all three real-time metrics quietly falling apart. When you diagnose a Starlink connection, look at all of them together, then treat the worst offender first.
If your investigation keeps pointing at congestion or plan deprioritization rather than hardware, compare your tier against your real usage in the plan picker and work through the broader Starlink troubleshooting checklist. Packet loss is rarely mysterious once you test it properly and fix the causes in order.
Don't just read — check your own setup.
Run a Starlink-focused speed test and compare download, upload, ping, and jitter against your real connection.
Related tools
Recommended next steps
Starlink Speed Test
Measure download, upload, ping, and jitter — the fastest way to spot a problem.
Obstruction Checker
The #1 cause of sustained packet loss is a blocked sky view. Check it here.
Coverage Map
See how dense satellite passes are in your area for context on handoffs.
Plan Picker
Compare Starlink plans against your real location and use case.
FAQ
How do I test Starlink packet loss?
Run a continuous ping to a reliable host and let it run for several minutes while you use the connection normally. On Windows, open Command Prompt and run 'ping -t 8.8.8.8'; on macOS or Linux, run 'ping 8.8.8.8' in Terminal. Let it collect a few hundred packets, then stop it (Ctrl+C) and read the summary line, which reports the percentage of packets lost. Test on Ethernet first so you are measuring the Starlink link and not your WiFi. The Starlink app's Statistics screen also tracks dropped-connection time, which is a useful second signal. A browser speed test alone cannot confirm packet loss, so use a ping for this.
What is a normal amount of packet loss on Starlink?
Brief, occasional loss is normal on Starlink because it is a moving network that hands your connection between satellites every few seconds. Very short spikes during those handoffs, or during a passing cloud burst, are expected and usually harmless for browsing and streaming. What is not normal is sustained loss that persists across a multi-minute test on Ethernet with a clear sky. If a wired continuous ping keeps dropping packets minute after minute, treat it as a real problem — most often an obstruction, a marginal mount, or a cabling fault — rather than normal satellite behavior.
Why does Starlink packet loss ruin video calls and gaming but not downloads?
Downloads are resilient: lost packets are simply re-sent, so a big file still arrives, just a little slower. Real-time traffic has no time to wait for a re-send. In a video call or an online game, a dropped packet is gone, and you experience it as a frozen frame, a robotic voice, a rubber-banding character, or a spike in your ping. That is why your speed test can look healthy while calls stutter: throughput hides packet loss that real-time apps cannot. If your download number is fine but live sessions feel broken, packet loss and jitter are the first things to investigate.
Can your speed test measure Starlink packet loss?
Not directly, and we will not pretend otherwise. Our Starlink speed test measures download, upload, ping, and jitter from your browser, which are strong indirect signals — rising ping and jitter often travel with packet loss. But a true packet-loss figure needs a sustained, continuous ping or a specialized tool, which the browser cannot run reliably. Use our speed test to spot a problem quickly, then confirm packet loss with a command-line ping as described above. Our methodology page is explicit about what we do and do not measure.
Does packet loss mean my Starlink dish is broken?
Usually not. The most common cause of real, sustained Starlink packet loss is an obstructed or marginal sky view, not a failed dish. Trees, rooflines, and poles that block even a slice of the sky force extra handoffs and drops. The next most common causes are WiFi interference (which is your local network, not the satellite), a stressed router, and occasionally a damaged cable or connector. Work through sky view, then Ethernet-versus-WiFi isolation, then the router, before you conclude the hardware itself has failed.
How do I fix packet loss on Starlink?
Fix it in order of likelihood. First, clear the sky view — check for obstructions and raise or relocate the dish so it has a wide, clean view. Second, test on Ethernet to rule out WiFi, and if WiFi is the culprit, improve router placement or add a mesh node. Third, reboot the router and, if you use a third-party router, verify bypass mode is set correctly so two routers are not fighting. Fourth, inspect the cable and connectors for damage or a loose seat. If a wired continuous ping is still dropping packets with a clear sky after all of that, capture before-and-after tests and contact Starlink support with the evidence.