A yacht should not choose a connectivity link only by peak speed. The useful question is what each link is good at, what it fails like, and what traffic should still work when the yacht is moving, alongside, at anchor, in a busy marina, or outside preferred coverage.

LEO, VSAT, cellular, and marina Wi-Fi are different tools. LEO can provide strong low-latency broadband when the terminal has a suitable sky view and service plan. VSAT may provide managed maritime service and support arrangements. Cellular can be excellent near shore but depends on roaming, antennas, country rules, and congestion. Marina Wi-Fi can be useful as a local shore link but should usually be treated as untrusted and variable.

Link Comparison

What each link is best for

  • LEO broadband: Guest internet, owner office, crew welfare, cloud services, video calls, and backup to other satellite paths.
  • VSAT or managed satellite: Contracted maritime support, known service provider escalation, and planned offshore connectivity.
  • Cellular LTE/5G: High-throughput coastal operation, yard periods, local SIM/eSIM use, and temporary capacity.
  • Marina Wi-Fi: Short-term berth connectivity, admin work, updates, and low-risk traffic after firewalling.
  • Shore fibre or hardline: Yard/refit periods, large updates, cloud backups, and high-volume transfers where available.

Primary Link Selection

Questions before deciding

  1. Where will the yacht operate? Offshore, coastal, marina-heavy, polar, remote, charter regions, or short owner trips.
  2. What traffic matters most? Guest streaming, owner office, crew welfare, CCTV access, vendor support, monitoring, or business systems.
  3. What are the failure modes? Obstruction, rain fade, roaming block, data cap, congested marina, public IP loss, CGNAT, or account lockout.
  4. Who supports it? Onboard ETO, IT provider, SatCom provider, cellular supplier, marina, manufacturer, or management company.
  5. How is traffic controlled? Firewall policy, SD-WAN rules, DNS, monitoring, VLANs, captive portals, and guest isolation.

Do Not Let Link Count Replace Design

Five WAN links can still produce unreliable service if routing policy is unclear. Define which link carries which traffic, which users have priority, which link is blocked from OT or bridge-adjacent networks, and what the crew should tell guests when service degrades.

Acceptance Record

Minimum evidence should include:

  • Link inventory, serials, account owners, and support contacts.
  • Normal priority order and emergency priority order.
  • Traffic groups for guest, crew, owner, vendor, monitoring, and management systems.
  • Test results for each link and each failover path.
  • Known regional, data, roaming, or service-plan limits.
  • Open defects, accepted limitations, and management decisions.

References