Speed matters, but unstable Starlink often shows up as latency spikes, lower ping success, and short events. StarBar keeps those signals visible together on your Mac.
| Signal | What it suggests | Check in StarBar | Next step |
|---|---|---|---|
| High download, bad calls | Bandwidth may be fine while latency, jitter, or packet success is the problem. | Put Latency or Ping Success in the menu bar during the call. | Compare the call window with Events, obstruction, router reachability, and throughput. |
| Router-to-internet and device speed disagree | The official Starlink speed test can separate Starlink/router performance from device or Wi-Fi performance. | Compare local throughput, latency, ping success, and client/router context while testing. | If router performance is good but the device result is poor, debug Wi-Fi, client, VPN, DNS, or local routing. |
| Slow speed on one device | Client, Wi-Fi, VPN, DNS, or app-specific behavior may be responsible. | Check network client context where available and compare another device. | Follow official slow-speed guidance: test without VPN and isolate device/router causes. |
| Low ping success | Packets are failing or timing out; this often feels like stutter more than slowness. | Watch Ping Success with recent Events and obstruction state. | Prioritize stability troubleshooting before chasing higher download numbers. |
| Throughput flat but latency spikes | The path may be congested, obstructed, or briefly interrupted even without active downloads. | Compare Latency, Throughput, Events, and Status in the same time window. | Run a controlled test: same device, no VPN, same location, then repeat after a placement/router change. |
Yes: For downloads, inspect throughput and speed-test context.
No: For calls/games/remote work, prioritize latency, ping success, and events.
Yes: Investigate Starlink/router/obstruction/congestion.
No: Investigate client device, Wi-Fi band, VPN, DNS, or app-specific behavior.
Yes: Use Starlink support with your local evidence.
No: Keep the working configuration and monitor for recurrence.
A Starlink speed test measures transfer rate. Latency measures delay. Ping success helps reveal whether packets are getting through. For real-world stability, you need more than one number.
A connection can test fast between interruptions but still feel bad during calls, games, remote desktops, or uploads. Brief drops and latency spikes can be more disruptive than a lower average download number.
A router-to-internet test answers whether Starlink itself can move traffic from the router outward. A device test adds Wi-Fi, Ethernet, VPN, DNS, adapter, and client load. When those disagree, StarBar's local client/router context helps keep the investigation grounded.
During a call or focused session, keep latency or ping success in the menu bar. If the connection stutters, open StarBar and compare recent events, throughput, obstruction state, and router reachability.
Run a speed test when you need throughput context, but read it alongside the stability signals. StarBar keeps speed-test access and local telemetry near each other.
Remote service outages, internet routing, account state, and official service incidents may require sources outside local telemetry. Use official Starlink support for account and service-side questions.
It depends on the task. Calls, gaming, and remote work are often more sensitive to latency and packet loss than raw download speed.
Ping success is a recent measure of whether test packets are getting through. Drops can explain stutters even when bandwidth looks acceptable.
StarBar includes speed-test context where local Starlink router telemetry supports it, alongside latency, ping, throughput, and event signals.
StarBar puts local Starlink status, latency, ping success, outages, obstructions, throughput, and power draw into a native macOS menu bar app.