Obstruction can turn a connection that looks fine most of the time into one that drops at the worst moment. StarBar helps keep local obstruction and event context close on macOS.
| Signal | What it suggests | Check in StarBar | Next step |
|---|---|---|---|
| Obstructed status appears | The terminal sees sky blockage or obstruction-related connection impact. | Compare Status, obstruction percentage, Events, and latency/ping behavior. | Use the official app obstruction tool for placement decisions and check whether events line up. |
| Events happen at repeat intervals | A fixed obstruction may be affecting recurring satellite paths. | Look at recent event timing and whether ping success drops during the same windows. | Try a cleaner view of sky and allow the obstruction map to refresh over time. |
| Blank or partial obstruction data | The local field may not be exposed yet, or the map may still be building. | Look for partial telemetry and whether dish/router fields are reachable. | Use official app guidance and give the terminal time online before trusting the map. |
| Map shows clear, blocked, or unmapped regions | The map is a diagnostic view of observed sky visibility, not just a decorative heatmap. | Use StarBar to compare obstruction state with real connection symptoms like events and ping success. | Interpret the official map colors, then test a placement change if blocked regions match interruptions. |
| Obstruction looks minor but calls drop | Small or directional obstructions can still matter for real-time work. | Compare obstruction with latency, ping success, events, and throughput during calls. | Prioritize stability signals over a single percentage. |
Yes: Treat obstruction as a likely local cause and test a clearer placement.
No: Check router/client reachability, Wi-Fi, power, and service-side status.
Yes: Re-check alignment and let the obstruction map rebuild after uptime.
No: Look for environmental changes: foliage, parking angle, weather, temporary blockage, or mount movement.
Yes: Prioritize physical placement and sky view.
No: Investigate other instability causes like router path, VPN, congestion, or remote service issues.
The Starlink obstruction map helps show whether nearby trees, buildings, terrain, vehicle placement, or dish orientation are interfering with sky visibility. StarBar adds Mac-side context around obstruction state and recent events.
Do not read obstruction alone. Compare obstruction state with recent events, latency, ping success, throughput, dish alignment, and whether the symptom happens at repeatable intervals.
The official map can show clear sky, obstructed regions, unmapped regions, and areas Starlink excludes from normal satellite service. Early or partial maps should be read with caution; compare them with real events before making installation decisions.
StarBar keeps obstruction and outage context in the same diagnostic surface as latency and ping success. That makes it easier to notice whether a choppy meeting coincided with obstruction-related local events.
Use the official Starlink app for setup flows, official obstruction scanning, installation guidance, and Starlink support. StarBar is an independent companion for local telemetry once your Mac can reach the setup.
RV, van, boat, cabin, and Starlink Mini placements can change frequently. A spot that worked yesterday may have a new obstruction after parking orientation, tree cover, weather, or dish position changes.
No. Use the official Starlink app for setup and scanning workflows. StarBar helps show local obstruction-related telemetry from your Mac when available.
Yes. Even intermittent obstruction can cause short drops or quality changes. Read obstruction together with events, latency, and ping success.
Obstruction telemetry can vary by hardware, firmware, dish state, setup, and local reachability. StarBar labels partial states when fields are not exposed.
StarBar puts local Starlink status, latency, ping success, outages, obstructions, throughput, and power draw into a native macOS menu bar app.