What changed

Rates and plan structures are set by SpaceX and change without notice. Confirm current pricing against your own Starlink account before making a purchasing decision.

What Ocean Mode Actually Bills

Ocean Mode is the setting that lets a Starlink terminal work away from land. Without it, coverage stops at the coastal boundary. With it, the terminal keeps working offshore and bills by the gigabyte rather than drawing on an included allowance.

The rate change matters less than the billing behaviour, which is the part that catches operators out. Ocean Mode is not a geographic switch that activates when you cross a line. It is a toggle on the account, and while it is on, the per-gigabyte rate applies to every gigabyte the terminal consumes — regardless of where the vessel actually is.

Leave it enabled alongside the dock and the crew streaming in the mess is billed at the offshore rate. Leave it enabled through a week of yard work and the vessel pays ocean prices for shoreside internet. The terminal does not warn anyone, and the bill arrives a month later.

At $2/GB that was an expensive oversight. At $6/GB it is three times as expensive, and the underlying problem is unchanged: the cost of a link is decided by settings and behaviour that nobody onboard can see.

What It Costs in Practice

The arithmetic is unforgiving because crew traffic is not small. A single crew member streaming standard-definition video uses about 1.5 GB an hour, and roughly 3 GB an hour in HD. At $6/GB, an evening of HD streaming by one person costs more than many shoreside broadband contracts cost in a month.

Meanwhile the traffic that actually justifies the connection — chart updates, weather routing, VMS reporting, safety communications, shore-side management access — is typically a small fraction of the total. The operational systems the vessel genuinely needs are rarely the ones driving the bill.

That gap between what costs money and what matters is the whole problem, and buying a larger plan does not close it. It is closed by being able to see which traffic is which, and to act on it from the bridge rather than through a support ticket.

Where This Sits Against Priority Data

Two different cost models now run side by side, and a mixed fleet may be exposed to both:

A superyacht on a commercial allocation, with tenders, chase boats or an owner's own vessel on Roam, is running both at once — and only one of them punishes a setting nobody checked.

Why This Needs a Control Layer, Not a Bigger Plan

A Peplink router already has the technical capability to manage this. It can hold multiple WAN links, prioritise traffic, cap devices and fail over between connections. The capability is not the gap.

The gap is that all of it lives behind an administrator interface built for network engineers, while the people who need to act on a tripled data rate are the captain, the ETO and the shore-side manager — none of whom should be handed the router's admin password. So the expensive setting stays on, and the first anyone hears of it is the invoice.

NCoDE Peplink exists for that gap. It sits in front of the router and exposes the decisions that matter without exposing the router itself:

None of this makes Starlink cheaper. It makes the spend deliberate, which is a different and more achievable goal.

What to Check on Your Own Fleet

The vessels that get surprised by a connectivity invoice are consistently the ones where nobody can answer the first two questions on that list without making a phone call.