The Starlink app gives you a number — but it doesn’t tell you what that number means for your actual life online. Whether 5% ruins your video calls or barely touches your streaming depends on more than just the percentage. This guide explains exactly what each level costs you and what to do about it.
These are the questions that come up the moment someone stares at a number in the Starlink app and has no idea what it means for them in practice.
The obstruction percentage in the Starlink app is the share of critical satellite sky that was blocked during the last 12 hours of operation. More precisely, it reflects how often a passing satellite was blocked by something in the dish’s field of view during the period the dish has been running — not an abstract coverage area, but a real count of blocked satellite-to-dish communication events. A 5% obstruction doesn’t mean 5% of your sky is covered. It means that roughly 5% of the satellite handoff opportunities in the last 12 hours were blocked by something physical — a branch, a roofline, a chimney — preventing the dish from completing the connection to that satellite. Each blocked handoff is a potential dropout lasting 1–3 seconds or more, and at 5%, those events can happen dozens of times per hour depending on which part of the sky is blocked.
One to two percent is genuinely fine for most users. Most first-day installs at well-chosen locations score between 0 and 1%. Single-digit percentages in the low range — below 2% — produce so few blocked satellite passes per day that most users never notice the drops. Video calls hold. Streaming plays without buffering. Gaming performs acceptably for casual and moderate play. The distinction: 1–2% obstruction might mean one or two brief micro-drops per hour, typically lasting less than 2 seconds each, occurring when a satellite happens to pass behind a specific branch. That’s tolerable for almost any use case. What makes it less tolerable is if those drops happen to cluster at a specific time of day during your work calls — even a rare obstruction in a heavily trafficked part of the sky feels much worse than the number suggests.
Probably manageable for streaming and browsing, but not without occasional noticeable interruptions. At 8%, you’re well into the range where most users experience brief drops — typically 1–3 seconds — several times per hour. For video streaming, the adaptive bitrate systems on Netflix, YouTube, and similar platforms hide many of these drops by briefly lowering quality. You may see the picture go slightly softer for a few seconds rather than experiencing an obvious freeze. For casual browsing and email, 8% obstruction is annoying but rarely breaks a task. For video calls (Zoom, Teams, FaceTime), the same drops cause freezes or pixelation that your other participants can see. For gaming, expect occasional rubber-banding or disconnects from match servers. Whether 8% is “okay for you” really comes down to how much real-time use you do — and Starlink offers a 30-day return window specifically to let you test before committing.
Significantly. The percentage tells you how much — the map tells you where, and where matters more than the number alone. For U.S. users, the densest satellite traffic moves through the northern portion of the sky. A 3% obstruction in the northern arc causes more drops per hour than a 5% obstruction in a direction where satellites rarely pass. A small red zone at the 12 o’clock position of your map (northern sky) will interrupt your connection far more frequently than a same-sized red zone at the 6 o’clock position (southern sky). This is why two installations with identical percentage scores can have completely different user experiences. Always look at the map alongside the number — the map shows you exactly which satellite corridors are being blocked, not just how much sky is covered.
Several reasons, all normal. First, the percentage updates as more satellite passes accumulate — a dish that’s been running for 6 hours has less data than one running for a week, so early readings may be less stable. Second, wind moves branches, so a tree that was still during one measurement period may have swayed into satellite paths during another. Third, the percentage reflects the last 12 hours specifically — if you check after a windy night versus a still morning, the numbers will differ. For a reliable baseline, check the percentage after the dish has been running for at least 5–7 days in typical weather conditions. The map becomes progressively more accurate over that period. Short-term readings within the first 24 hours of operation should be treated as estimates, not established facts about your location.
Beam switching improves real-world performance at a given obstruction level, but it does not change the percentage number itself. The percentage reflects how often satellite paths are blocked regardless of whether the system successfully rerouted. What beam switching actually does: when a satellite’s path is heading into a known obstruction zone, the dish proactively switches to a different satellite whose path is clear — before the blocked satellite causes a dropout. This means the percentage and the actual experienced dropout rate can diverge. A dish with 6% obstruction may experience far fewer than 6% of its handoffs as actual user-noticeable drops if beam switching successfully routes around most of them. The practical limit: beam switching helps with minor obstructions by finding alternative satellites. When the obstruction covers a large enough arc that all available satellites are blocked simultaneously, there’s nothing to switch to and drops occur regardless.
Yes — the “Starlink Obstructed” message that appears as a status notification is distinct from the percentage in Statistics. The status message appears when the dish is actively experiencing a connection failure because all currently visible satellites are blocked simultaneously — it’s a real-time alert, not a historical metric. The percentage under Statistics is your 12-hour historical record. The “Obstructed” status notification is a live report of an active obstruction event happening right now. If you see the status notification frequently, your obstruction percentage is high enough to be causing ongoing connection problems. If you only see it occasionally, you have a partial obstruction that occasionally exhausts available satellites in that direction but normally works around it. Checking both — the live status and the historical percentage — gives you the most complete picture of your obstruction situation.
Every percentage range has a distinct real-world impact. Here is exactly what to expect at each level and what the right response is.
What you experience: Virtually no obstruction-related dropouts. Most first-day installs at good locations score here. Video calls are smooth. Streaming plays without quality drops. Gaming performs well for casual and moderate competitive use. The connection behaves like a reliable broadband service with the occasional satellite handoff micro-drop (1–2 seconds, inherent to LEO technology, not obstruction). What to do: Nothing — this is where you want to be. If you’re at 1–2% and contemplating expensive changes to get to 0%, the user experience improvement is not worth the cost.
What you experience: Occasional brief interruptions — typically a few 1–3 second drops per hour — that most users notice but tolerate. Streaming and browsing are largely unaffected. Video calls hold during most of the day but may show a brief freeze or audio drop once or twice per hour. Light gaming works. A 2–5% score is typical of a suburban yard with a few nearby trees or a house with modest roofline intrusion. What to do: If you work from home on video calls all day, look at the obstruction map and identify whether the blockage is in the northern sky arc — if so, even a minor fix (moving the dish a few feet, trimming one branch) may drop you to under 2% and meaningfully improve call quality. If you don’t use real-time video or gaming, this range is unlikely to bother you.
What you experience: Noticeable drops that interrupt real-time use. Video calls freeze and pixelate in ways your other participants can see and comment on. Gaming experiences rubber-banding and occasional match disconnects. Streaming typically holds but may buffer briefly during sustained drop sequences. A study measuring Starlink obstruction effects found that obstructions in this range increase round-trip latency by an average of 4% and packet loss by 0.3% — modest-sounding numbers that translate to meaningfully worse call quality. What to do: This range is worth fixing. Open the map, identify the specific direction and object causing the blockage, and address it — a targeted branch trim ($150–$400), a mount adjustment, or repositioning the dish a few feet frequently drops a 10% score to under 3%.
What you experience: Frequent drops that disrupt most real-time use. Video calls are unreliable enough that most users stop using them over Starlink. Gaming becomes frustrating with repeated disconnects. Streaming quality degrades noticeably and buffers repeatedly. Speed test results may look reasonable between drops, but real-time applications feel the blockages acutely. The Starlink app begins recommending that you consider relocating the dish once you approach this range. What to do: A physical fix is necessary before this connection is usable for work or school. The fix depends on what’s causing the blockage — if it’s trees, a targeted trim or pole height increase; if it’s a roofline, repositioning to the roof peak; if it’s terrain or buildings, a taller mount or finding a clearer location on the property.
What you experience: The connection is effectively unreliable for most purposes. Large portions of the sky are blocked, leaving the dish with no viable satellite path during many intervals. Speed is degraded, latency is erratic, and the “Starlink Obstructed” alert appears regularly. The Starlink app explicitly recommends moving the dish at this level — that recommendation is not optional. What to do: The current mounting location cannot be salvaged without major changes. Walk the entire property with the app’s obstruction check, find a location that scores under 5%, and move the dish there — even if it requires a long cable run. If no location on the property scores acceptably, a tall pole or tower above the obstruction may be the only viable option.
The same obstruction percentage affects different uses very differently. Streaming hides drops better than video calls. Gaming reacts to 2-second drops differently than a web browser. Find your primary use and see what each level actually means.
| Online Activity | Under 2% | 2–5% | 5–15% | 15–30% | 30%+ |
|---|---|---|---|---|---|
| Video calls (Zoom, Teams, FaceTime) | Smooth · rare drop | Good · 1–2 brief freezes/hr | Noticeable · frequent pixelation | Unreliable · unusable for work | Fails · constant disruption |
| 4K / HD Streaming (Netflix, YouTube) | No buffering · full quality | Occasional quality dip | Buffering episodes · quality drops | Frequent buffering · SD only | Unwatchable at HD |
| Casual browsing and email | No perceptible impact | No perceptible impact | Minor page-load pauses | Noticeable delays on large pages | Frustrating · some pages fail |
| Online gaming (casual) | Smooth · normal play | Occasional brief lag spike | Rubber-banding · lag noticeable | Frequent disconnects · unplayable | Cannot hold a match |
| Competitive gaming (FPS, ranked) | Viable · normal latency | Occasional spike ruins moments | Unreliable · not competitive | Unusable for ranked play | Impossible |
| Video uploading and large downloads | Normal speed · no issues | Negligible impact | Slower · TCP retransmissions add time | Noticeably slower · pauses | Very slow · frequent retries |
| Work from home (VPN + cloud apps) | No issues | Minor · tolerable | VPN drops and reconnects | Disruptive · VPN unreliable | Cannot work reliably |
| Voice calls and VoIP | Clear · no drops | Occasional 1–2 sec gap | Choppy · noticeable quality loss | Calls drop · callers complain | Unusable for calls |
Most users misread the obstruction percentage. Understanding exactly what it measures changes how you interpret the number — and what you decide to do about it.
The obstruction number is calculated over the previous 12 hours of the dish’s operation. It reflects the proportion of satellite handoffs — the moments when the dish switched from one passing satellite to the next — that were blocked by a physical object. A 5% score means roughly 5 out of every 100 satellite handoff opportunities in the past 12 hours were blocked. Because Starlink performs handoffs roughly every 15 seconds, 12 hours represents approximately 2,880 handoff events. At 5% obstruction, that’s about 144 blocked handoffs in 12 hours — roughly 12 per hour. Not all of them produce user-noticeable drops (beam switching reroutes many), but the underlying count is what the percentage represents. The number is not a spatial measurement of how much of your sky is covered. It’s a temporal measurement of how often the satellite signal was interrupted.
A common mistake is reading a 2% obstruction score and concluding it means the installation is nearly perfect. In practice, even a 2% score translates to roughly 24 blocked satellite events in 12 hours — about 2 per hour. If those 2 events cluster in a heavily trafficked satellite corridor (the northern sky for U.S. users), they might each cause a noticeable 2–3 second drop. A single branch covering a small patch of the northern sky can cause 20 or more brief dropouts per day — enough to interrupt two or three video calls during a work day. The percentage alone doesn’t tell you whether those 2% of blocked events all fall in the same ten-minute window of your morning meeting or spread across the full 12 hours. The map is where you see the true impact. A 2% score with a clean, distributed map is very different from a 2% score with a concentrated red patch in the northern corridor.
Users often check their Starlink speed test, see 150 Mbps, and conclude obstruction isn’t affecting them. This is a meaningful misread. Speed tests measure bandwidth over several seconds and average out the brief drops caused by obstruction. A 2-second connection gap that drops an entire video call conference frame shows up as barely a ripple in a 10-second speed test. The relationship between obstructions and packet loss is the most actionable metric, not download speed. Testing over 100 video calls on Starlink connections at various obstruction levels, researchers found video quality was consistently good at under 5% obstruction but showed noticeable quality dips at higher levels — even when the underlying speed test showed 100+ Mbps. Reducing sky obstruction from 10% to 1% can drop packet loss from 2–5% to under 0.5%, which transforms video call quality completely even though the speed test number barely changes.
The percentage is a headline number. The map is the story. Two dishes at 4% obstruction in different parts of the sky will have entirely different user experiences — because not all parts of the sky carry equal satellite traffic.
Starlink’s satellites orbit in shells inclined at approximately 53 degrees, which concentrates the densest satellite traffic in the northern portion of the sky for users across the contiguous United States. Your dish naturally tracks north most heavily to catch the most satellites per hour. A 3% obstruction in the northern arc can cause more user-noticeable drops per hour than a 6% obstruction in the southern sky. This is the most important single thing to know when reading your obstruction map. When prioritizing fixes, always address northern sky blockages first. The specific northern direction varies slightly by your latitude, but as a practical rule: if your map shows red anywhere between the 10 o’clock and 2 o’clock positions (assuming north is 12 o’clock), those zones deserve the most urgent attention. A single branch in that corridor causes disproportionate disruption.
On the obstruction map, the center represents directly overhead (zenith) and the edges represent the horizon. Satellites approaching from the horizon cross the edge of the map and work their way toward the center as they climb higher in the sky. An obstruction near the edge of the map — at or near horizon level — intercepts satellites as they enter the dish’s view, catching them at their lowest elevation angle. A roofline or tree at the horizon catches every satellite that needs to cross that arc, creating many blocked events per hour. An obstruction near the center of the map — directly overhead — affects fewer satellite paths because fewer satellites are at zenith position at any given time. This is why a small red arc near the map edge (horizon level) causes more drops than a same-sized red blob near the map center, even though both produce the same few percentage points.
Before trying to reduce your obstruction percentage, look at where the red is concentrated on the map. A small red zone at the 12 o’clock position (north) near the edge of the map is the worst possible obstruction location — it blocks the most satellite passes in the highest-traffic direction at the lowest elevation angle. Removing or clearing that specific obstruction will improve your connection more than reducing an equal-sized red zone at 6 o’clock (south) near the center of the map. Target your energy toward the northern, near-horizon red zones first. Everything else is secondary.
Once you know your percentage and where the blockage sits, the fix becomes a straightforward physical problem. There are exactly four ways to reduce obstruction — which one you need depends on what’s causing the red zones.
The fastest and cheapest way to reduce obstruction is to find a mounting spot where the sky view is naturally clearer. Walk your entire property with the Starlink app running its obstruction check, holding your phone at the height where the dish would actually be mounted — not at standing height. Different spots on the same property regularly produce dramatically different scores. The difference between the worst spot (often where the dish is currently mounted) and the best spot (often an outbuilding, a different roof face, or a backyard clearing) can be 15–20 percentage points. Starlink sells a 150-foot proprietary cable specifically for situations where the best dish position is away from the house. A cable run from a better spot costs $35–$80 and beats $500 in hardware modifications at a bad location.
For tree-caused obstruction, removing the specific branches that cross your red zones is typically the fastest, most cost-effective fix. Screenshot your obstruction map and physically identify — by looking upward from the dish position — which branches correspond to which red areas. Share that map with a licensed arborist and point out the specific branches. A targeted trim of 3–5 upper branches often drops a 15% obstruction score to under 3% for $150–$400. Do not have the whole tree thinned “generally.” That approach produces unpredictable results and costs more. Targeted removal of the identified problem branches is what produces a measurable reduction in the specific areas causing drops. Plan for re-trimming every two to three years as those branches regrow.
Getting the dish higher is the most versatile obstruction fix because additional height reduces the elevation angle to any horizontal obstruction — rooflines, neighboring buildings, and low trees all shrink as a percentage of the sky view when the dish is higher. Moving from a wall mount to the roof peak eliminates most roofline intrusion and costs $35–$80 in mount hardware. A roof peak plus a 2-foot mast extension adds another 5–8 degrees of clearance and costs $50–$150. For tall tree obstruction, a standalone pole mounted in concrete — typically 10–20 feet above the house roofline — gets the dish above most residential tree canopy and can drop a 20% score to under 2%. The pole hardware runs $200–$500 installed, plus lightning grounding (required, not optional). For extreme forest environments, a communication tower adds $2,500–$4,000 but solves obstruction problems no other hardware can.
Before spending a dollar on any physical fix, spend five minutes actually reading the obstruction map. Open the Starlink app → tap Statistics or Visibility → look at the full map rather than just the percentage at the top. Identify the direction of every red zone and compare it to what you can see from the dish position looking upward in that direction. Most of the time, the obstruction causing the biggest problem is a single identifiable object — one branch, one chimney top, one roofline edge — visible to the eye when you know which direction to look. Knowing exactly what’s causing the problem takes a physical fix from “move the dish and hope” to a precise, targeted action. The map is the diagnostic. The percentage is only the alert that a problem exists. Never plan a fix from the number alone — always use the map.
For full-time remote work with regular video calls, under 2% is the target and 2–5% is the practical ceiling where most users can work without their colleagues noticing problems. Above 5%, video calls develop the kind of periodic freezes that interrupt conversations and make you look unreliable on camera — which matters professionally. The critical detail: even a 2% obstruction score is workable if the red zones are in the southern sky rather than the northern sky. Two percent obstruction concentrated in the northern arc (the most active satellite direction for U.S. users) causes more call disruptions than the same percentage spread across less-trafficked directions. Run the obstruction map, look at where the red zones sit, and prioritize northern-sky blockages for removal first. If all your red is in the south and east and your score is under 5%, your connection will likely support professional video call use without embarrassing freezes.
This is the most common Starlink complaint, and it comes from a fundamental difference in how streaming and video calls handle brief connection drops. Streaming platforms like Netflix use adaptive bitrate technology and content buffers — the platform pre-loads 30 seconds of video ahead of what you’re watching, so a 2-second connection drop during a satellite handoff goes entirely unnoticed because the pre-buffered content continues playing. Video calls have no buffer. A 2-second connection drop during a Zoom call appears immediately as a freeze or pixelation for everyone on the call, because real-time video cannot be pre-loaded. At 8% obstruction, you’re experiencing roughly 8–12 brief drops per hour. Your streaming platform hides them. Zoom shows every one. The solution is reducing the obstruction, not finding a different video call platform — all real-time applications will behave the same way at that obstruction level.
For casual gaming — MMOs, strategy games, cooperative shooters, and single-player titles with online features — 4% obstruction is manageable but noticeable. You’ll encounter occasional brief lag spikes or rubber-banding when a satellite handoff coincides with an obstruction event. For most casual games, these are tolerable annoyances rather than game-ending problems. For competitive ranked play in fast-paced FPS titles where a 200-millisecond lag spike means losing a gunfight, 4% is genuinely problematic. The threshold for competitive gaming is closer to under 2% — and even then, Starlink’s inherent satellite handoff micro-outages (separate from obstruction) create occasional unpredictable spikes that dedicated competitive players find frustrating. If competitive gaming is a priority, reducing obstruction to the lowest achievable level and using a wired Ethernet connection to the router (not Wi-Fi) gives the best possible result on satellite internet.
At 18%, the connection is unreliable for real-time use and the Starlink app is likely already suggesting you consider relocating the dish. If physically moving the dish isn’t possible, three options remain. First: targeted branch removal — if even part of the 18% comes from trees, a $150–$400 arborist visit to clear the identified red zones can drop you to 8–10%, which at least makes casual streaming and browsing functional. Second: raising the dish in place with a pole extension above whatever is causing the blockage — even adding 3–4 feet of height to the current mount can reduce roofline-caused obstruction by several percentage points. Third: adding a cellular backup connection that activates when Starlink drops — this doesn’t fix the obstruction but makes the overall connection more usable for the times when real-time needs arise. The honest answer at 18%: the installation needs a physical change to be reliable, and the Starlink app’s recommendation to move the dish exists precisely for this situation.
A score that increases over weeks without any deliberate changes to the installation almost always means one of three things happened: tree growth (most common in spring and summer as deciduous trees leaf out), a new object entering the signal path (a construction project nearby, new equipment on the roof, a branch that fell and lodged in a new position), or seasonal wind behavior moving flexible branches into satellite corridors that were clear when the dish was first installed. Open the obstruction map and compare the red zones now to what they looked like when the score was lower — new red has appeared somewhere specific, and that new area corresponds to whatever changed. The app builds its map dynamically, so the current map is your most up-to-date picture of what’s actually blocking the dish right now. Identify the new red zone, determine what changed in that direction from the dish’s perspective, and address it specifically.
This guide provides general information about Starlink obstruction percentages and their real-world impact on connection quality. Performance at any obstruction level varies depending on the specific location of blockages within the sky view, local satellite density, time of day, weather conditions, and hardware generation. Obstruction thresholds described are based on field data and published satellite network research and represent typical experiences, not guarantees. Always use the Starlink app’s official obstruction map alongside the percentage number when making installation and fix decisions. This content is entirely original and independently written.