“Elevated packet loss” is a Starlink status, not a speed. It means some data never arrived, so apps must wait, retry, or glitch. The dish can still show a connection. Download can still look acceptable. The session can still feel broken.
This guide explains what that app message points to, how loss feels compared with high latency and low throughput, and the checks that can change the result: obstructions, Wi-Fi, load and weather. A warning on one kit is local evidence, so start with the installation in front of you.
What the app is telling you
A packet is a small chunk of internet traffic. Loss means a chunk did not show up in time to be used. Real-time apps cannot wait forever. File transfers can retry. Web pages can stall, then jump.
Starlink’s app and router status can flag elevated loss when the kit sees more missing packets than it considers normal. The useful reading is qualitative:
- Something on the path is dropping or delaying traffic enough that recovery is visible.
- The warning is about integrity, not about how many megabits a speed test printed.
- It can be brief. A passing obstruction, a rain cell, a Wi-Fi collision, or a busy household can raise loss and then drop it again.
Do not treat the word “elevated” as a published percentage. Operators do not owe you a public threshold, and inventing one does not help you fix the link. Watch whether the status is a blip, a pattern at the same hours, or a constant banner.
If the same minutes also show disconnects, use Starlink keeps disconnecting for drop-focused isolation. Loss and disconnects overlap; they are not the same ticket.
How packet loss feels
Loss is easier to recognize by behavior than by a single chart.
Calls and meetings. Voices clip. Faces freeze, then jump. Someone says “you’re robotic.” The meeting app may still show “connected.”
Games. Teleporting, hitting a ghost, rubber-banding. That can also be delay. Loss adds missed inputs, not only late ones.
Streaming. A sudden quality drop or a rebuffer when the player’s guess about the path was wrong. Mild loss can be invisible if the buffer is large.
Browsing and cloud apps. Tabs spin, then load all at once. Uploads restart. A VPN session dies and reconnects.
“The Wi-Fi is fine.” The phone still shows the Starlink SSID with a full indicator. That indicator is local radio to the router, not a promise that packets are surviving the satellite path.
If the only symptom is “pages feel late but complete,” you may be looking at latency rather than loss. If everything completes but takes forever on large files, you may be looking at throughput. Fix the metric you actually have.
Packet loss vs latency vs low speed
Keep the three columns separate. Mixing them produces the wrong repair.
| What you notice | Likely metric | Typical wrong fix |
|---|---|---|
| Actions happen late but in order | Latency (delay) | Buying a “faster” plan you do not need |
| Actions arrive late and jump around | Jitter (delay variation) | Rebooting in a loop without testing Ethernet |
| Pieces of the session vanish | Packet loss | Chasing download Mbps on a speed test |
| Files crawl; calls are still OK | Low throughput | Assuming the dish is “offline” |
A speed test can show healthy download and still coincide with a bad call if loss or jitter is clustered in the interactive traffic. Conversely, a low download number with clean ping and no loss can still stream a movie.
How to read Starlink speed test results is the decoder for those columns. Use it after you reproduce the symptom, not as a substitute for watching the app status.
Check obstructions first when loss repeats
Starlink needs a view of the sky. Trees, eaves, a mast, a hill, a neighboring roof, and even a seasonal leaf-out can clip the path. A brief blockage often looks like a burst of loss rather than a clean “offline” banner.
Practical order:
- Read the obstruction tools in the Starlink app. A map that is “mostly clear” can still have a repeating wedge at the worst hours.
- Note whether loss clusters when the dish is looking through a known object. Time of day can line up with satellite geometry and with sun glare on your notes; do not overfit a single evening.
- If the kit is portable, try a truly open patch of sky as a test, not a permanent install decision.
- Do not ignore false warnings, but do not dismiss a real tree because the app once cried wolf.
The dedicated walkthrough is how to read the Starlink obstruction map. Placement mistakes belong there. This page only needs the rule: repeating loss with a dirty sky view is an obstruction problem until proven otherwise.
Indoor “temporary” setups and dishes placed under a porch are frequent sources of elevated loss. The radio path is not a Wi-Fi extender. If the dish cannot see sky, the router can still hand out a local network that goes nowhere useful.
Then separate Starlink from Wi-Fi
A lot of “Starlink packet loss” is Wi-Fi packet loss wearing a Starlink costume.
Home Wi-Fi drops packets when the device is far from the router, when walls are dense, when a microwave or neighbor network collides, when a mesh hop is weak, or when the client radio is old. The Starlink app may still be healthy because it sits next to the router.
Isolation is simple:
- Repeat the failing task on a device sitting next to the Starlink router.
- If the kit has Ethernet, use it for one computer. If the call clears on Ethernet and fails across the house, you found a local-network problem.
- Pause mesh backhaul experiments until the near-router test is clean.
- Avoid running the meeting through a travel extender that repeats a weak SSID.
If Ethernet is clean and Wi-Fi is not, improving the local network will do more than rebooting the dish. If both are bad, keep going down the Starlink-side list.
Load, weather, and other local causes
Household load. One 4K stream may be fine. Several streams, a cloud backup, a console download, and a camera upload together can fill the path and raise retries. That can surface as loss in the call you care about. Pause the heavy jobs and see whether the status calms down. This is congestion and queueing, not proof of a national incident.
Device load. A laptop with a failing radio, an aggressive VPN, or a security tool that inspects every packet can look like network loss. Test a second device.
Weather. Heavy rain, wet snow on the dish, and storm-driven power flicker can raise errors on a satellite path. Ordinary overcast is a weak explanation by itself. For the weather-shaped symptoms, use Does Starlink work in bad weather? rather than duplicating that pillar here. Clear snow and standing water from the dish using the product’s own guidance; do not chip ice with tools that damage the surface.
Cables and power. A nicked cable between dish and router, a loose connector, or an undersized power path can produce errors that look like “the network is dropping packets.” Reseat connections with power off if you are going to touch them. After storms, inspect for water at outdoor joints.
Software state. A reboot of router and dish, then the client device, is a fair test after you have notes on when the loss happens. Rebooting without notes just resets the clock.
None of these checks require a rumor that the whole constellation failed. Your kit’s status is local evidence. Treat it that way.
A short repair order that does not chase ghosts
Work one change at a time:
- Write down when it happens, which apps fail, and whether the Starlink app still shows a connection.
- Test next to the router, then on Ethernet if you can.
- Stop large uploads and downloads; retest the call or game.
- Read obstructions; move to a clearer sky only as a test.
- Check weather and dish surface if the timing matches precipitation or snow.
- Reseat power and the dish cable if the problem is constant across devices.
- Reboot once, then retest.
- If the link stays up but apps still break, measure.
When you can load a page, run a Starlink speed test from the same device that failed. Compare download, upload and ping, then review saved jitter in the dashboard when available. Check packet loss in the Starlink app or the affected game or meeting tool. If the speed test is clean while the meeting is not, look at the meeting app, VPN, or Wi-Fi again.
If the kit says connected and the internet still never arrives, switch to Starlink connected without internet. That page is for a dead path, not for a glitchy live one.
Use the Connection Outlook to plan around conditions at a place and time, and the Starlink app to inspect the terminal and tree line in front of you.