Starlink SNR Explained

Signal-to-noise ratio is the difference between useful radio signal and unwanted background noise, usually expressed in decibels. In Starlink terms, it is not a cosmetic statistic; it is the margin that decides whether the dish can keep decoding data cleanly while satellites move overhead. Ku-band is a microwave frequency range used by many satellite services, including consumer satellite broadband, and it is more sensitive to blockage and rain than lower-frequency cellular bands. Rain fade is a loss of signal caused when water droplets absorb or scatter radio energy. Obstruction percentageis the share of the dish's required sky view blocked by trees, rooflines, poles, or terrain.

For Starlink owners, the right question is not “what is my perfect SNR?” It is “do I have enough margin for the worst 10 minutes of the day?” A rural cabin can look perfect at 2pm and fail at 8pm because the signal margin is thin, the cell is busy, and a wet tree canopy eats another 3-8 dB. That is why this guide ties SNR to symptoms: Mbps, latency, outages, obstruction percentage, and weather. Start with the obstruction checker if you have any tree line inside the dish's sky view, then validate the result with repeat tests on the Starlink speed test.

“For home Starlink, I treat 25 dB as the practical floor for a stable install. Below that, you may still see a 100 Mbps speed test, but the link has too little reserve for rain fade or a satellite handoff.”

What SNR numbers mean in the real world

SNR is logarithmic. A 3 dB change is not tiny; it represents roughly a doubling or halving of power ratio. A 10 dB improvement is a 10x better signal-to-noise ratio. That is why moving a dish 6 feet sideways can feel dramatic if it clears one branch from the satellite path. It is also why a marginal setup can go from usable to broken in one storm.

Use the table below as a practical diagnostic range, not a manufacturer promise. Starlink does not expose one universal consumer-facing SNR meter in the same way a Wi-Fi scanner does, and firmware can summarize signal health differently by kit generation. The physics still hold: more margin gives the modem more room to use cleaner modulation, recover from short fades, and keep latency stable during handoffs.

How to read Starlink SNR without overfitting one number

The mistake is treating SNR like a speed tier. A 32 dB link does not guarantee 250 Mbps, because Starlink speed also depends on the satellite overhead, gateway backhaul, cell congestion, plan priority, router placement, and client Wi-Fi. A low SNR does prove something more useful: the install is losing signal quality before the network has a chance to perform well. Fix that first.

Run three checks in order. First, inspect physical sky quality with the app or our sky obstruction tool. Under 1 percent obstruction is excellent; 1-5 percent is usually livable; 5-10 percent needs careful testing; above 10 percent is a problem for calls and gaming. Second, run wired or near-router speed tests at 7am, 2pm, 8pm, and after rain. Third, compare your result against the expected plan and region using the ISP comparison tool and the deeper guide to Starlink actual vs advertised speed.

If mornings are fast and evenings are slow, SNR may be fine and congestion is likely. If performance collapses during rain or whenever wind moves the treetops, SNR margin is probably thin. If every test is bad at every hour, look at obstruction, cable damage, router placement, or a service issue. The troubleshooting flow in Why Is My Starlink So Slow? is the right next read once you isolate the pattern.

“One speed test is a snapshot. Four tests across the day tell you whether the limit is radio margin, cell congestion, or your local Wi-Fi. I want at least a 20 Mbps floor at 8pm before calling an install healthy.”

The four obstacles that drag SNR down

Low SNR usually has a physical cause. Starlink is a low Earth orbit network, so the dish is constantly tracking moving satellites and handing off between them. The FCC describes NGSO fixed-satellite service as directional earth stations sharing Ku-, Ka-, E-, and V-band spectrum under interference rules, which matters because your terminal is not simply listening passively. It has to maintain a clean directional link while other satellites, gateways, weather, and local electronics exist around it.

1. Trees and partial obstructions

Trees are the top SNR killer because they combine blockage, scattering, and movement. A bare winter branch may be tolerable; the same branch with wet leaves in July can erase several dB. The tricky part is that the obstruction may only affect one slice of the sky. You can get 180 Mbps for 10 minutes, then a 4-second outage when the active satellite crosses behind the canopy. That is enough to break a video call or kick a game session.

If obstruction is 5-10 percent, raise the dish before changing plans. A 10-foot pole often beats a $380/month plan jump because it fixes the actual signal path. Use the Starlink obstruction guide for mount decisions, and check the coverage map if your site sits near mountains or a steep tree line.

2. Rain, snow, and wet surfaces

Starlink can handle normal weather, but radio links still obey physics. Rain fade is more visible at microwave frequencies, and Ku-band satellite links are known to be affected by atmospheric absorption and scattering. Light rain may only trim speed. Heavy rain can lower the link margin enough that a marginal 18 dB setup becomes a 10 dB setup. Snow adds a second issue: buildup on the dish or nearby branches can obstruct the view until melt mode or clearing catches up.

Weather is not fixable in the same way as trees, so the answer is headroom. A clear-sky SNR near 30 dB gives the system room to lose a few dB and keep working. A clear-sky SNR near 16 dB gives it no reserve. If your outages happen only in storms, improve the mount location, remove nearby wet foliage, and confirm the dish face drains cleanly.

3. Local radio noise and electrical interference

Local interference is less common than trees, but it is real around metal roofs, dense electronics racks, poorly grounded inverters, and industrial sites. Off-grid users should pay attention here: charge controllers, cheap inverters, and long unshielded DC runs can add noise to the local environment or create power instability that looks like RF trouble.

Keep the dish and cable away from high-current AC lines, solar inverters, electric motors, and radio transmitters when possible. Do not coil excess cable beside the router power brick. For cabins and RVs, use the Starlink power sizer to avoid undersized batteries and voltage sag, then re-test during inverter load. A clean morning test and a bad evening test while the inverter is loaded can point to power path noise, not the sky.

4. Cable, mount, and router path problems

The last category is not true satellite SNR, but users experience it the same way: unstable service. A kinked cable, loose dish connector, water in a wall penetration, or a mount that vibrates in wind can create random outages. Router-side Wi-Fi can also hide a healthy Starlink link behind a weak indoor signal. Before you re-mount the dish, run a test close to the router and read the Starlink speed test guide so the measurement itself is clean.

“The fastest SNR fix I see is height. If a 6-foot move cuts obstruction from 8 percent to under 2 percent, that usually beats any router upgrade and can recover 30-80 Mbps in the evening.”

A 15-minute SNR diagnosis workflow

Use this workflow before you spend money. It catches the common issues in the order they are easiest to prove.

1. Photograph the sky from the dish location and check obstruction percentage. Target under 5 percent; under 1 percent is ideal.
2. Run three speed tests from the same device: morning, evening, and during or immediately after rain. Save Mbps, ping, and jitter.
3. Inspect the cable for tight bends, crushed sections, standing water, and loose connectors. Replace before splicing.
4. Test near the router, then test over Ethernet if your setup supports it. Separate satellite problems from Wi-Fi problems.
5. Move the dish temporarily to a clearer spot for 2 hours. If outages disappear, the permanent mount is the issue.

If the temporary move fixes performance, do not overthink it. Install height or location is the lever. If nothing changes, the next suspects are cell congestion, plan priority, router placement, or hardware failure. At that point, compare your results with the Starlink troubleshooting guide and decide whether the support ticket needs obstruction screenshots, outage logs, or speed-test history.

FAQ