Shipping Container Tracking: Why Cellular Dies at Sea and What Actually Works
Your container left Long Beach six days ago. The last data point you have is a cellular ping from the port terminal. Since then: nothing. No position, no temperature reading, no door-open alert. For the next 15 days, that $400,000 in cargo is a ghost. You’ll “see” it again when it pings a tower approaching Shanghai, assuming it wasn’t rerouted to a transshipment port you didn’t authorize, assuming the reefer didn’t fail on day three, and assuming it’s still on the vessel your TMS says it’s on.
This isn’t an edge case. This is the default experience for most companies shipping goods across oceans. The industry loses an estimated $25 billion annually in demurrage and detention charges alone, according to Drewry, and those costs compound when you can’t see what’s happening to your cargo in transit. Add spoilage from undetected reefer failures, inflated safety stock buffers against ETA uncertainty, and insurance claims filed with zero supporting telemetry, and you start to understand the real price of the ocean-leg black hole.
Here’s the thing: the problem isn’t that tracking technology doesn’t exist. The problem is that the most widely deployed technology, cellular, is physically incapable of working where it matters most. And no firmware update is going to fix physics.
Why Cellular Trackers Go Silent After Port Departure
Cellular networks are tower-based systems. A cell tower’s effective range depends on antenna height, frequency band, and line-of-sight conditions, but in practical terms, you’re looking at roughly 35 km (about 20 nautical miles) of usable range from shore. Under ideal conditions, some LTE signals might stretch to 50 nautical miles. After that, there is no signal. There is no tower. There is ocean.
This applies to every cellular variant currently marketed for IoT: LTE-M, NB-IoT, Cat-1, Cat-4. These are terrestrial technologies. NB-IoT and LTE-M are often pitched as “optimized for IoT,” and they are, for IoT devices that stay on land. They offer better building penetration, lower power consumption, and wider carrier support. None of that matters 500 nautical miles from the nearest coastline.
To be clear, this isn’t an anti-cellular argument. Cellular is excellent for drayage legs, inland rail, and port-area tracking. It’s cheap, well-supported, and energy-efficient. But if you’re evaluating a shipping container GPS tracker and the spec sheet only lists cellular connectivity, you need to understand what you’re actually buying: land-leg visibility with a multi-week gap in the middle.
LAND PORT OCEAN (14-45 days) PORT LAND
─────────────┤ ├─────────────────────────────────┤ ├──────────────
██████████████ [NO SIGNAL] ██████████████
Cellular ✓ Cellular ✓
◄──── The Expensive Black Hole ────►That gap is where the money burns.
The Ocean Leg Is Where the Highest-Value Risks Concentrate
Consider what you’re not seeing during those 14 to 45 days of silence. The ocean leg isn’t just the longest segment; it’s where risk concentrates most densely.
Route deviations and transshipment exposure. Containers get rerouted. They get offloaded at transshipment hubs you weren’t informed about. At those hubs, they sit on docks, exposed to theft, tampering, and handling damage. Without container-level positioning, you find out after the fact, if at all.
Temperature and condition excursions. Industry data from the World Shipping Council and Carrier Transicold suggests that 5–10% of reefer containers experience temperature deviations on any given voyage. A reefer failure on day two of a Pacific crossing means 18+ days of uncontrolled temperature before anyone knows. By arrival, the claim is six figures and the evidence is a temperature log showing when the failure started, but nothing about what happened during transit, because your tracker had no way to report it.
ETA erosion. Without positional data, your ETA is derived from the vessel’s published schedule. Post-2020, global vessel schedule reliability has hovered between 40% and 60%, according to Sea-Intelligence’s quarterly reports. Your “ETA” is a guess informed by a schedule that’s wrong half the time, with no mid-ocean correction possible.
Insurance blind spots. Marine cargo insurers are moving toward parametric and usage-based policies that require continuous telemetry. No ocean data means no discount on premiums, and weaker substantiation if you need to file a claim. Subrogation becomes nearly impossible when you can’t prove where or when the damage occurred.
The Satellite Landscape: What Actually Works and What It Costs You
Once you accept that cellular can’t solve the ocean leg, satellite is the only remaining category. But “satellite” is not one thing. The differences between satellite approaches are as significant as the difference between cellular and satellite itself.
┌────────────────────┬────────────┬───────────┬──────────┬──────────────┐
│ Technology │ Coverage │ Power │ Cost per │ Update Freq │
│ │ │ Draw │ Message │ (typical) │
├────────────────────┼────────────┼───────────┼──────────┼──────────────┤
│ GEO Satellite │ ±70° lat │ High │ High │ Hours │
│ (Inmarsat, etc.) │ │ │ │ │
├────────────────────┼────────────┼───────────┼──────────┼──────────────┤
│ Legacy LEO/MEO │ Global* │ Medium │ Medium │ 1-6 hrs │
│ (Orbcomm, Iridium) │ │ │ │ │
├────────────────────┼────────────┼───────────┼──────────┼──────────────┤
│ New LEO Satellite │ Full global│ Low │ Low │ Minutes │
│ (Hubble, etc.) │ incl polar │ │ │ to near-RT │
├────────────────────┼────────────┼───────────┼──────────┼──────────────┤
│ AIS (vessel-level) │ Varies │ N/A │ N/A │ Variable │
│ — NOT container │ │ │ │ │
│ level tracking │ │ │ │ │
└────────────────────┴────────────┴───────────┴──────────┴──────────────┘
*Some coverage gaps at extreme latitudesGEO satellites (Inmarsat and similar) orbit at approximately 36,000 km. That distance means devices need significant transmission power and larger antennas to maintain a link. Hardware is bulky, expensive, and power-hungry, a poor fit for a battery-powered device bolted to a container. Coverage also stops around ±70° latitude, which matters as Arctic shipping routes see increasing traffic. Update frequency is typically measured in hours.
Legacy LEO constellations (Orbcomm first-gen, Globalstar, Iridium-based solutions) represent a meaningful improvement. Lower orbits mean lower power requirements and better latency. Orbcomm has a long history in container tracking, particularly with major shipping lines. Iridium offers genuine global coverage, including polar regions. But these are aging constellations designed in the 1990s and early 2000s. Per-message costs remain relatively high when you want frequent updates, and some hardware form factors, particularly those requiring large ground planes, don’t fit cleanly on standard container mounting points. Iridium-based solutions offer strong coverage but at a cost and power profile that limits update frequency for multi-year battery life targets.
New-generation LEO constellations, including Hubble, represent a different design philosophy. These networks were purpose-built for IoT, not adapted from voice or broadband infrastructure. Lower orbits (under 600 km in many cases) mean dramatically lower power requirements, which means smaller devices, longer battery life, and lower cost per message. The economics shift enough to support updates every few minutes rather than every few hours. Hubble’s network was designed around asset tracking use cases like container tracking satellite connectivity, with global coverage that includes polar routes and doesn’t drop out at high latitudes.
AIS-based platforms (FourKites ocean visibility, project44 ocean modules, and similar) deserve an honest mention. These platforms infer container position from vessel-level AIS data. There’s no hardware on the container; the system knows which vessel your container was loaded onto and tracks the vessel. This is low-cost and provides a rough sense of where your cargo is. For many shippers, it’s a reasonable starting point. But it’s not container-level tracking. It can’t tell you if your container was offloaded at a transshipment port. It can’t detect a reefer failure. It doesn’t know if your container door was opened. For high-value, perishable, or heavily insured cargo, vessel-level inference isn’t a container visibility solution. It’s a vessel visibility solution with an assumption layered on top.
The Continuity Problem That Nobody Wants to Talk About
Solving the ocean leg alone isn’t enough. The full intermodal journey, from dray to port, port dwell, ocean transit, destination port, and rail or dray to final delivery, needs continuous visibility. This is where most tracking deployments quietly fall apart.
The common setup: a cellular tracker for land legs, a separate satellite device for ocean (if you have one at all), vessel AIS data stitched into a TMS, and maybe a port community system feeding dwell times. Three or four data sources, multiple vendor integrations, and no single view of the container’s journey from origin to destination. When something goes wrong, you’re cross-referencing timestamps across systems to reconstruct what happened.
The ideal for intermodal container tracking is a single device that works across every leg without human intervention: no swapping hardware at port, no mode-switching, no stitching. This either requires a tracker with both cellular and satellite radios, or a satellite-native device with sufficient update frequency that cellular becomes unnecessary even on land.
This is where new LEO satellite IoT changes the equation in a way older technology couldn’t. If the satellite link works everywhere, on land, at port, and at sea, with update intervals measured in minutes and at costs competitive with cellular, the argument for a separate cellular radio weakens considerably. One device, one data stream, one platform across all legs. Hubble’s approach supports exactly this continuous-visibility model, eliminating the patchwork.
Building This Into Your Evaluation Criteria
If you’re evaluating global shipping container tracking solutions, or re-evaluating what you already have, here’s a practical checklist. Every item addresses a failure mode that real logistics teams have hit.
EVALUATION CHECKLIST
─────────────────────────────────────
[ ] True container-level, not vessel-inferred
[ ] Works mid-ocean (satellite, not cellular)
[ ] Coverage at ALL latitudes your routes touch
[ ] Update frequency ≤ 15 min for meaningful ETA
[ ] Battery life ≥ 3 years (no mid-voyage recharge)
[ ] Form factor fits standard container mounting
[ ] Sensor integration (temp, humidity, shock, door)
[ ] Single platform across all transport legs
[ ] API/webhook for TMS/ERP/insurance integration
[ ] Total cost of ownership, not just hardware price
─────────────────────────────────────A few items worth emphasizing. Update frequency matters more than people realize. A position report every six hours means your ETA calculation can be off by hundreds of nautical miles. At 15-minute intervals, you can detect route deviations, slow steaming, and port approach timing with enough lead time to act on it. Battery life is a hard constraint. A device that needs recharging or replacement mid-deployment defeats the purpose. Three-year battery life at your required update frequency: verify both numbers together, because vendors love to quote battery life at the lowest update rate. Total cost of ownership includes hardware, connectivity fees per message or per month, platform access, installation labor, and recovery/refurbishment. A $50 device with $15/month connectivity costs more over three years than a $150 device with $5/month connectivity. Do the math on your fleet size.
The Ocean Leg Shouldn’t Be Your Weakest Link
The most critical, highest-risk, longest-duration segment of the global supply chain has historically been the least visible. That was an acceptable trade-off when the only satellite options cost $20 per message and required a device the size of a brick. It’s not acceptable now.
LEO satellite IoT, from Hubble and the broader new-generation constellation category, is closing this gap in a way that wasn’t economically or technically feasible five years ago. The hardware is smaller. The connectivity is cheaper. The coverage is genuinely global. And the update frequency is fast enough to be actionable, not just historical.
Look at your current tracking stack. Map it against your actual routes. If your visibility has a hole shaped like the Pacific or the Atlantic, the technology to fill it exists today. The question is how much longer you’re willing to fly blind.
Hubble Network enables continuous container tracking across open ocean without satellite hardware costs or connectivity gaps. See how it works →