Starlink Maritime Troubleshooting: Fixing Dropouts on Board

Why Starlink Maritime drops out on a moving vessel

Starlink Maritime uses low-earth-orbit satellites, which means the dish is constantly handing your connection off from one satellite to the next as they pass overhead — unlike a traditional VSAT system pointed at a single fixed geostationary satellite. That handoff is usually seamless, but on a boat it's compounded by the vessel's own movement: as the yacht changes heading, rolls in a swell, or turns to enter an anchorage, the dish's clear view of the sky shifts too, and a handoff that would be invisible on land can produce a brief drop at sea.

The other common cause is straightforward physical obstruction — a radar arch, mast, exhaust stack, or even another vessel moored alongside can block the dish's line of sight to a satellite low on the horizon. Weather-related signal fade (heavy rain attenuation) is real but far less common than obstruction or handoff on most cruising grounds. Power issues — a loose PoE injector connection or a breaker that trips after a hard knock in rough seas — are the fourth major cause and are often mistaken for a satellite problem.

Diagnosing the dropout: a quick checklist

Before assuming the worst, run through this in order:

• Check the Starlink app's obstruction map. It logs exactly where the dish's view was blocked, which tells you immediately if it's a mounting/obstruction issue rather than a satellite-side problem.
• Check the dish's physical mounting. After rough seas, brackets can shift a few degrees, which is enough to change what the dish can see even if nothing looks obviously wrong.
• Confirm the Roaming/Mobile priority service plan is active, not a fixed/residential plan — using the wrong service tier on a moving vessel causes far more dropouts than hardware ever does.
• Check the PoE injector and cabling for corrosion or a loose connection, especially after washdown or heavy spray — this is one of the most common yacht-specific failure points.
• Note whether the vessel was underway or at anchor when it dropped — underway dropouts from beam handoff are usually brief and self-resolve; persistent drops at a fixed anchorage point to obstruction or hardware.

Router and mesh reconfiguration after a dropout

On most yachts, the Starlink router isn't the only router in play — it's usually set to bypass mode and feeding a third-party multi-WAN router (Peplink and similar brands are common) or a mesh system that distributes WiFi across the vessel's decks. After a dropout, the fix often isn't the dish at all; it's that the downstream router or mesh nodes didn't re-establish DHCP cleanly, leaving crew devices holding an old IP address and gateway that no longer resolves.

The reliable fix is a reboot in the correct order: power down the mesh nodes and downstream router first, then the Starlink router/dish, wait for the dish to fully re-acquire signal (the Starlink app will show "Connected"), then bring the downstream router back up, and finally the mesh nodes. Rebooting everything simultaneously — the instinct most crew have — often just recreates the same DHCP conflict. Devices with a manually assigned static IP are the most common casualty and may need their network settings reset by hand afterward.

Failover: cellular and port WiFi as a backup layer

Any yacht that depends on connectivity for charter guests or crew communication should have a failover layer that doesn't depend on the dish at all. The most common setup is a multi-SIM cellular router (Peplink MAX and similar) carrying local SIMs for whatever country the vessel is currently in, which automatically takes over WAN traffic if Starlink drops. A simpler backup, used widely by smaller crews, is a dedicated MiFi hotspot device or a crew member's personal phone set to hotspot mode.

The practical habit worth building: keep at least one local SIM active and topped up per cruising region, and know in advance which crew phone plan has international roaming enabled. That five-minute setup, done once at the start of a season, is the difference between a dropout being a non-event and it being a genuine emergency.

The catch-22: getting help when the connection is what's broken

The obvious problem with a connectivity issue is that it can make it hard to reach anyone for help — but it rarely makes it impossible. A crew member's cellular data (even a slow 3G/4G signal in a remote anchorage), port WiFi if you're near enough to shore, or a MiFi backup device is almost always enough bandwidth to place a phone call to +1 (888) 711-9428 or open a lightweight remote screen-sharing session on one laptop, even while the main satellite link and the rest of the onboard network are down.

That's the practical answer to "how do you fix the internet if the internet is broken": you don't need the full onboard network working, you need one device with any connection at all, tethered to a phone if necessary, so a RemoteFix 24/7 technician can walk you through resetting the router that's serving everyone else. This is exactly the kind of problem covered in our broader yacht crew tech support guide.

Underway vs. at anchor: different dropout patterns

It's worth separating two very different situations. Underway — especially on a fast passage or a Mediterranean crossing with frequent heading changes — brief, repeated dropouts from beam handoff are normal and rarely fixable, since they're inherent to how the satellite constellation works relative to a vessel in motion. These usually aren't worth troubleshooting beyond confirming the Roaming plan is active.

At a fixed anchorage, by contrast, a dropout that persists for more than a few minutes is almost never beam handoff — it's obstruction (check what's now between the dish and open sky after the vessel swung on its anchor), a mounting issue, or the router/mesh problem covered above. Knowing which situation you're in narrows the fix considerably before you even open a support ticket.