Connectivity· 6 min read

Starlink Updates Itself. Do You Know When?

Starlink keeps its dishes current by installing software on its own schedule. Where the dish is the only link to an operation, every install is a reboot and a short outage, and you want a record of each one.

It Updates on Its Own Schedule

Starlink pushes new software to every dish, and the dish installs it by rebooting. The dish first reports that an install is pending, and some hours later it restarts, usually in the small hours. You do not pick the night, and nothing where the dish is mounted tells you it happened.

Below is a week of history from a Starlink Mini on one of our own test sites. Twice in five days the dish reported “Software install pending”, and each time it rebooted early the next morning: 40 seconds of outage on 6 November and 39 seconds on 10 November, each followed by a new firmware version.

A week of dish history: each software update, the reboot it caused and the outage that followed.

Forty seconds rarely matters on its own. What matters is knowing it was the dish updating, and not your power, your network or your equipment, when someone asks why the data has a gap at a quarter to three in the morning.

Handovers Are Not Outages

A dish also drops for a second or less each time it switches from one satellite to the next. Counted as outages, these would bury the real ones. Powoflow groups them per day — “7 brief dropouts during satellite handovers, 5.6 s in total” — so restarts and genuine outages stand out.

One Number for the Link

Powoflow scores the link from 0 to 100 over the last hour. The score is built from three parts: availability (seconds of outage), latency and packet loss. When it drops — to 87 after a 39-second restart, for example — the drop appears in the dish history with its reason.

Over longer windows, Powoflow tracks 30-day availability, a worst case that counts gaps in its own telemetry as downtime, the number of failures and reboots, the mean time between failures and the mean time to recover.

A Starlink dish: health, software update state, 30-day availability and the 0–100 link-quality score.

What Else to Watch

  • The view of the sky — an obstruction map of where the dish's view is blocked, and a trend that shows whether it is getting worse as trees grow or equipment moves.
  • Data use — download and upload per month, with a projection for the current month, so a data cap does not catch you out.
  • Performance — throughput and latency over time, signal and alignment, and the dish's power draw.
  • Data Explorer — any two readings on one chart, such as latency against power draw.
Data used each month with a projection for this one, and where the sky is blocked.
Data Explorer: any two readings on one chart, here latency against power draw.

Act From the Dashboard

When the dish needs a nudge, you can stow it, unstow it, reboot it or run a speed test from Powoflow, without driving out to it.

Throughput and latency over time, signal and obstruction, alignment, and the dish controls.

Why It Matters

At a remote operation, the Starlink dish is equipment you depend on like any other. Powoflow reads it over the local network through Powoflow Sense Mesa, next to your sensors and equipment, and Mesa keeps a local copy of every reading while the link is down. When the dish updates itself, you see when it happened, how long it took, and how the link has done since.

See your Starlink next to everything else

Updates, reboots, outages and link quality, in the same place as the operation it connects.