Troubleshooting

Starlink not working? Start with the local signals.

When Starlink feels broken, the fastest first move is to separate local symptoms from account or network-wide issues. StarBar helps Mac users inspect reachable local telemetry before guessing.

StarBar events screen showing recent local Starlink interruptions on macOS
Status Obstructed local state
Ping 93.4% recent success
Events 3 recent interruptions
Latency 21 ms round trip

What to check, what it means, what to do next.

Signal What it suggests Check in StarBar Next step
Router unreachable from the Mac The problem may be Wi-Fi, Ethernet, third-party router routing, or the Mac being on the wrong network before it is a dish issue. Look for missing router/client fields, partial telemetry, or no local Starlink hardware context. Confirm the Mac network, then check router light state and third-party router/static route setup if applicable.
Official app says offline, booting, searching, or disconnected The terminal/router may be in a known local fault state rather than a Mac-only browser or app issue. Check whether StarBar can still see local status, events, obstruction, ping, and router context. Use Starlink's offline troubleshooting path, then correlate any recovery with StarBar event timing.
Recent events increased The terminal is reporting local interruptions rather than a purely browser/app issue. Open Events and compare count, duration, reason, and timing against when the failure happened. If events cluster around obstruction or reachability, inspect placement, cable/power, and official app status.
Low ping success with normal throughput The connection may be unstable in short bursts even when a speed test looks acceptable. Put ping success or latency in the menu bar during the next call/session. Compare ping drops with obstruction, events, and local router/client changes.
Official status reports an incident Local troubleshooting may not resolve the root cause if Starlink is experiencing a broader event. Use StarBar to document local symptoms, but do not treat it as the source of global status. Follow official Starlink status/support guidance and avoid unnecessary hardware changes.

Run this local check.

  1. Set the menu bar mode to Status, Latency, or Ping Success before changing hardware.
  2. Open the Events screen and note the time, reason, duration, and severity of recent interruptions.
  3. Check whether router, terminal, and client details are present or marked partial.
  4. Compare obstruction state with the exact time the user-visible failure happened.
  5. If only one Mac/app is affected, inspect client/router context before moving the dish.

Use the signal, then branch.

Can your Mac reach local Starlink telemetry?

Yes: Inspect status, events, latency, ping success, obstruction, and router/client data.

No: Treat this as a local network path problem first: Wi-Fi, Ethernet, bypass mode, router route, or power.

Do recent events line up with the outage window?

Yes: Use the event reason and obstruction/power/router context to narrow the local cause.

No: Check official Starlink status and whether the issue is limited to one client or service.

Is the official Starlink app reporting an account or activation issue?

Yes: Use Starlink support; StarBar cannot repair account-side state.

No: Continue with local telemetry and physical/network checks.

Short answer

If Starlink is not working, check whether your Mac can still reach the Starlink router or terminal, whether local telemetry reports obstruction or recent events, whether ping success dropped, and whether official Starlink sources show a wider incident.

Local checklist

Start with signals you can observe from your own setup before changing hardware or support settings.

  • Confirm your Mac is on the Starlink network you expect.
  • Check StarBar status, latency, ping success, and recent events.
  • Compare the official app's state labels with StarBar's reachable local telemetry.
  • Look for obstruction or alignment state changes.
  • Compare Wi-Fi/router reachability with terminal telemetry.
  • Open the official Starlink app for account, activation, billing, and official support checks.

What StarBar adds

StarBar keeps local Starlink telemetry close to the Mac menu bar. That makes it easier to notice whether the failure looks like no local reachability, recurring packet loss, obstruction, power behavior, or a short interruption pattern.

What StarBar cannot confirm

StarBar is not an official outage page and cannot verify billing, activation, plan state, or network-wide Starlink incidents beyond what your local hardware reports. Use official Starlink support for account and service-side issues.

When to stop debugging locally

If multiple devices are offline, the official app cannot reach the terminal, or official Starlink sources report an incident, local Mac telemetry may only confirm the symptom. At that point, account/support workflows matter more than additional local checks.

Quick answers.

Can StarBar fix Starlink when it is not working?

No. StarBar is a diagnostic utility. It helps you inspect local telemetry, but it does not change Starlink account, billing, activation, or network-side service state.

Why does Starlink work on one device but not another?

That can point to Wi-Fi, router, DNS, client-device, or network setup issues rather than the dish itself. StarBar can help inspect local router/client context when those fields are available.

Should I use the official Starlink app too?

Yes. Use the official Starlink app and Starlink support for setup, account, billing, activation, and official status or support workflows.

Keep Starlink visible from your Mac.

StarBar puts local Starlink status, latency, ping success, outages, obstructions, throughput, and power draw into a native macOS menu bar app.