Maritime IoT Connectivity: Why Smart Ships Run Starlink, Iridium, and 4G Simultaneously —and What the SIM Layer Looks Like
June 3, 2026 · 8 min read · Case Studies
A modern commercial vessel generates over 20 GB of sensor data per day. No single network —not Starlink, not VSAT, not 4G —can serve a vessel from port to open ocean and back. The maritime connectivity stack is now multi-orbit by default: LEO for crew and high-throughput ops, GEO VSAT for offshore backbone, L-band (Iridium Certus) for safety and polar coverage, and coastal 4G/5G for cheap bandwidth near shore. The satellite modem does not take a SIM. But the 4G/5G router that handles port calls does — and it needs multi-IMSI profiles for Rotterdam, Singapore, and Houston to avoid roaming charges during 48-hour dock cycles.
TL;DR: Maritime IoT does not use a "maritime SIM." It uses a connectivity stack: LEO (Starlink/OneWeb) for high-throughput crew and ops data, GEO VSAT for stable offshore backbone, L-band (Iridium Certus) for safety and polar backup, coastal 4G/5G for port and near-shore bandwidth. The SIM layer is the terrestrial component of this stack —it handles the 4G/5G near-shore segment, provides backhaul for onboard LoRaWAN sensor networks, and serves as the identity anchor for multi-orbit traffic management. The procurement question is not "which satellite provider?" —it is "who integrates the SIM, the satellite agreements, and the traffic policy into one managed connection?"
The Vessel Connectivity Stack in 2026
The maritime industry has converged on a layered architecture. No single provider wins —the buying decision is about how the layers are orchestrated:
| Layer | Technology | Role | Example Providers |
|---|---|---|---|
| ------- | ----------- | ------ | ------------------ |
| LEO broadband | Starlink, OneWeb | Crew welfare, high-throughput ops, cloud sync | SpaceX, Eutelsat |
| GEO backbone | VSAT (Ka/Ku-band) | Proven offshore backbone, stable coverage | Inmarsat, Intelsat, SES |
| L-band safety | Iridium Certus | GMDSS, polar coverage, bad-weather backup | Iridium |
| Coastal cellular | 4G/5G, private 5G | Cheap bandwidth within 30-50 nm of shore | Local MNOs, port networks |
| Onboard edge | SD-WAN router | Traffic policy, VLAN separation, failover logic | KVH, Marlink, Speedcast |
Maersk's OneWireless rollout across 450 vessels (announced May 2025) exemplifies the scale: an IoT connectivity platform handling real-time cargo tracking, engine telemetry, predictive maintenance data, and supply chain visibility —all routed across this multi-layer stack based on traffic priority and link availability.
Source: MarineLink, "Maersk OneWireless IoT platform rollout", May 2025. Available at https://www.marinelink.com/news/maritime/broadband
The SIM Layer: What Actually Needs a Terrestrial SIM at Sea
Satellite modems do not use terrestrial SIM cards —they use satellite-specific subscriber modules. But every vessel has devices that do: 4G/5G routers for port and coastal connectivity, crew personal devices (when within cellular range, typically 15-50 nm from shore with external antennas), IoT sensors with cellular backup (container trackers, reefer monitors that use cellular at port and satellite at sea), and private 5G/LTE networks on offshore platforms and large vessels.
The SIM requirement for maritime is specific: the SIM must support multiple terrestrial networks (for when the vessel is near different countries' shorelines), seamless handover between cellular and satellite backhaul (the onboard router handles this, but the SIM must support always-on APN and fast re-attach), and data pooling across the fleet (50 vessels, each burning 10-50 GB/month near shore, pooled into a shared data plan).
A multi-IMSI SIM with profiles for the vessel's regular port countries —Rotterdam (KPN/Vodafone NL), Singapore (Singtel), Houston (AT&T/T-Mobile) —provides native-rate connectivity in each port without roaming charges. At sea, the satellite layer takes over; the SIM goes dormant. The router decides which pipe to use based on GPS location, signal quality, and traffic priority.
Iridium Certus: Why L-Band Survives When Everything Else Fails
Iridium's L-band network (1.6 GHz) has a property that no Ku/Ka-band VSAT or LEO constellation can replicate: it works through heavy rain, dense fog, and at the poles —latitudes where GEO satellites drop below the horizon and LEO constellations thin out. Iridium Certus GMDSS (launched late 2024) is now the only global maritime safety service recognized by the IMO for distress and safety communications.
For IoT specifically: Iridium Edge Solar devices provide low-power satellite tracking for autonomous vessels, buoys, and offshore equipment. They use Iridium's L-band link for telemetry (position, battery status, sensor readings) at data rates of 2-40 kbps —not suitable for video or bulk data, but sufficient for 100-byte status messages once per hour. A device transmitting 100 bytes/hour via Iridium consumes approximately $3-8/month in satellite airtime (depending on service plan). Compare to a Starlink maritime plan: $250-5,000/month for unlimited data. The choice is not which is better —it is which layer handles which traffic.
Source: SatCenter.tv, "Why Smart Ships Use Starlink, OneWeb and Traditional Satellite Backups", 2025. Available at https://satcenter.tv/hybrid-maritime-connectivity/
Traffic Policy: Why the Router Matters More Than the Satellite
The often-overlooked component in maritime IoT is the onboard SD-WAN router that sits between the SIM/satellite modems and the vessel's applications. A commercial vessel generates 20+ GB of onboard sensor data daily. Shipping all of it over satellite would cost $500-2,000/day on VSAT or $100-500/day on Starlink. The router segments this traffic:
| Traffic Type | Priority | Pipe | Daily Volume |
|---|---|---|---|
| ------------- | ---------- | ------ | ------------- |
| Engine telemetry, predictive maintenance alerts | Critical | L-band or lowest-latency available | <10 MB |
| Cargo temperature/humidity logs | High | LEO or GEO, queued if offline | 50-200 MB |
| Crew internet, streaming | Low | LEO, throttled if ops need bandwidth | 15-20 GB |
| CCTV / security footage | Low (store-and-forward) | LEO at port, minimal at sea | 2-5 GB (at port only) |
The router's traffic policy determines whether a $250/month Starlink plan is sufficient or a $5,000/month VSAT plan is required. A well-configured router with per-application traffic policies can route crew Netflix over Starlink while reserving Iridium capacity for engine alarms —on the same vessel, simultaneously.
Source: ShipUniverse, "From VSAT to Multi-Orbit: The Connectivity Upgrade Map Maritime Buyers Actually Want", April 2026. Available at https://www.shipuniverse.com/tech/from-vsat-to-multi-orbit-the-connectivity-upgrade-map-maritime-buyers-actually-want/
Coastal 4G/5G: The Cheap Pipe That Maritime Plans Often Miss
The most cost-effective bandwidth in maritime IoT is not satellite —it is terrestrial cellular when the vessel is within 15-50 nautical miles of shore. A 4G router with an external marine-grade antenna (9-12 dBi gain) can maintain usable connectivity up to 30 nm offshore. Private 5G networks at major ports (Rotterdam, Singapore, Houston, Shanghai) extend this to 50+ nm with dedicated maritime coverage.
The SIM procurement implication: a multi-IMSI SIM with profiles for the vessel's regular port countries pays for itself within the first month of port calls. Roaming rates for a Dutch-issued SIM connecting in Singapore are EUR 3-8/GB. A multi-IMSI SIM with a Singtel profile pays EUR 0.50-1.00/GB —a 6-8x cost reduction —for the 20-50 GB that a vessel might transfer while docked for 24-48 hours.