The most-installed maritime comms package on new Singapore-managed vessels in 2026 is not a single satellite service. It is two LEO networks — Starlink Maritime and OneWeb Maritime — bonded together on a Peplink B One router. This post explains why, how it works, and what the setup looks like on a real vessel.
This guide covers bonding, where Starlink and OneWeb carry traffic at the same time for maximum speed. If you want OneWeb only as a standby backup to keep data costs low, see Starlink and OneWeb failover on a Peplink router.
Why bond two LEO networks
A single satellite service, no matter how good, has failure modes. Starlink outages have happened. Constellation-wide software rollouts cause 30-minute blips. Localised interference. Weather effects during heavy rain. Individual antenna hardware faults.
A single-service maritime comms design accepts these blips as unavoidable. A bonded two-network design treats them as failovers. If Starlink drops for 90 seconds, OneWeb carries the packets during that window. The vessel never notices.
The second benefit is bandwidth: under normal conditions both networks run in parallel and the Peplink balances load across them. Effective throughput is higher than either service alone. On a well-configured vessel we routinely measure 200-300 Mbps down when both LEO networks are healthy.
The third benefit is contractual: OneWeb Maritime has a proper SLA. If a charter contract or a flag state requires committed availability, OneWeb underwrites that, while Starlink handles the bandwidth-hungry crew and ops traffic.
What the Peplink B One does
The Peplink B One is a compact rugged edge router designed for vessel bridge decks. In this design it does five things:
- Accepts both LEO uplinks (Starlink WAN, OneWeb WAN) and any 4G/5G cellular WAN as inputs
- Runs Peplink’s SpeedFusion bonding — packet-level distribution across the WANs
- Provides sub-second failover when one WAN degrades
- Segments the vessel network into ops, crew, and guest VLANs
- Reports usage per WAN and per VLAN into a single management portal (InControl 2)
Physical size fits a bulkhead mount. Power draw sits under 20W. Runs on 12V or 24V DC directly — no inverter needed.
Failover logic explained
The Peplink measures the health of each WAN every few seconds:
- Loss rate (dropped packets)
- Latency (round trip)
- Jitter (latency variability)
When Starlink degrades — say a rain fade adds 40ms of latency and 3% packet loss — the Peplink shifts sensitive traffic (VoIP, video calls, control channels) to OneWeb within a second or two, while keeping bulk data on Starlink if it is still delivering enough bandwidth. When Starlink recovers, traffic drifts back.
The bonding is transparent to applications. A crew video call does not drop. A crane control feed keeps flowing. This is the difference between “the vessel had an outage” and “the vessel had a bandwidth blip nobody noticed.”
Crew vs ops network separation
On the same physical hardware the Peplink creates isolated VLANs. Typical setup on a Singapore OSV:
- VLAN 10 — Ops: bridge systems, ECDIS updates, engine telemetry, remote support sessions. Priority traffic. QoS reserved. Limited to specific mac addresses.
- VLAN 20 — Crew: crew WiFi. Separate SSID. Bandwidth capped per crew member to keep one heavy user from crushing the pipe. Content filtering optional.
- VLAN 30 — Guest: charter clients or visitors. Fully isolated from ops.
Crew video calls no longer starve the ops network. Ops downtime no longer means the crew loses WiFi.
Not sure what connectivity set-up is right for your vessels?
Send us your vessel type, route and current bill. We will tell you where you can save and where you are exposed.
What the install looks like on a vessel
Real timeline from a Singapore OSV job we ran last year:
- Day 0 morning: vessel arrives Sembawang, engineers board
- Day 0 hour 1-2: Starlink flat HP mounted on monkey island, cable routed to bridge
- Day 0 hour 3-4: OneWeb flat panel mounted, cabling
- Day 0 hour 5-6: Peplink B One installed at bridge chart table, both LEO uplinks connected, VLANs configured
- Day 0 hour 7: crew WiFi SSID up, ops network segmented, both satellite services online
- Day 0 hour 8: baseline speed test, handover to master
Total: one working day, no dry dock, no crane, no radome. Vessel departs next morning with full bonded connectivity.
Real-world performance numbers
Numbers we measure on a properly-installed bonded setup in SE Asia waters:
- Combined download throughput: 200-300 Mbps typical, peaks over 400 Mbps
- Upload throughput: 30-60 Mbps combined
- Latency: 40-70ms to Singapore internet exchange, 90-120ms to European endpoints
- Failover time when Starlink drops: sub-second for latency-sensitive traffic, 2-4s for bulk
- Uptime measured over 60 days: 99.7%+
Compare that to a typical VSAT run: 4-10 Mbps down, 200-400ms latency, weekly 5-30 minute outages.
What it costs
Indicative Singapore pricing, subject to updates:
| Item | Cost (SGD) |
|---|---|
| Starlink Maritime flat HP kit | 4,500-5,500 |
| OneWeb Maritime kit | 3,500-4,500 |
| Peplink B One + install kit | 1,500-2,000 |
| Install labour | 1,500 (one day) |
| Starlink airtime (Local Priority) | from 320/mo |
| OneWeb airtime | from 900/mo |
| Peplink InControl 2 (mgmt) | 200/year |
Total hardware and install: around SGD 12,000. Total monthly: around SGD 1,200-1,500 depending on airtime tier.
Related reading
- Starlink Maritime vs VSAT 3-year TCO for Singapore OSV
- OneWeb vs Starlink Maritime
- Maritime IoT buyer’s guide
Get a quote
If you are speccing a new build, a fleet-wide comms refresh, or a single-vessel upgrade — we can send a bonded-stack quote for your specific vessel within one working day. Sales at Envisiondata Pte Ltd — sales@envisiondatasg.com — or WhatsApp Steve directly on +65 9088 4899.
How we can help
The right connectivity depends on your vessels, routes and budget, not on a product brochure. We design, install and support set-ups that keep you online at a sensible monthly cost.
- Free review of your current connectivity and bills
- Starlink, OneWeb, VSAT and 4G/5G options compared for your route
- Automatic failover so crews stay online when a network drops
- Installation and 24/7 monitoring across Singapore and SE Asia
What happens when you contact us
- Short call or meeting — we listen to how your vessels operate.
- Vessel and route review — we check equipment, space, power, contracts and licensing.
- Clear recommendation — a written proposal and SGD quote, with options.
- Install and support — commissioning, testing and ongoing support.
Related: Dual-LEO Resilience bundle (Starlink + OneWeb)
Book a free connectivity review
There is no obligation. If your current set-up is already the right one, we will tell you.
About the author
Steve leads Envisiondata Pte Ltd in Singapore. He has more than 20 years in cables, telecom infrastructure and satellite communications across ASEAN. He designs and supports connectivity for tugs, OSVs, harbour craft and commercial fleets across the region.
Written by Steve
Steve has over 20 years of experience in cables, telecom infrastructure and satellite communications across ASEAN. He founded Envision Data to help Singapore and SE Asia vessel operators choose and run the right maritime connectivity, from Starlink and OneWeb to Iridium, Inmarsat and GMDSS.
Leave a Reply