Tunduma–Nakonde IoT connectivity for fleets

Tunduma–Nakonde IoT connectivity, keeping your fleet visible on the Dar corridor

Tunduma on the Tanzanian side and Nakonde on the Zambian side sit directly across the border from each other — the main road crossing between the two countries and the gateway from the port of Dar es Salaam to the Zambian and Congolese copperbelts. It is one of the most congested crossings in the region, and a place where single-network trackers go quiet.

The queue at Nakonde

The container has been waiting on the scanner for the best part of two days. Around it, the twin towns of Tunduma and Nakonde are a single unbroken line of trucks, and the queue moves in the small increments that a congested one-stop border allows. In Dar es Salaam a controller checks the fleet map and finds a truck that left port days ago frozen at the border — last seen, no new position, dashboard showing offline.

The device has not failed. It is holding to one operator's cell in a border town where every truck in the queue is doing the same, and it has nowhere else to go, because it is provisioned for one network. When the container finally clears and rolls south into Zambia, the tracker has to drop the Tanzanian network and authenticate onto a Zambian one before it can report. For the days it spent in the queue and the hours it takes to hand over, the load was somewhere in a line that stretches out of sight — and the controller had no way to say where.

This is the ordinary shape of a congested crossing, not an edge case. The truck is where it is meant to be, doing what the border makes it do. The gap is a SIM that could only ever hold one network, at the one place where one network is never enough.

Why Tunduma–Nakonde is the lane that exposes connectivity weakness

Tunduma–Nakonde sits on the Dar es Salaam Corridor — the TANZAM highway and Zambia's Great North Road — which forms the northern leg of the wider North–South Corridor, with the TAZARA railway running alongside it. It has been a one-stop border post since 2019, but the designation has not cleared the queues: days-long waits and cargo-scanning backlogs have been reported, driven in part by an ageing scanner on the Nakonde side that clears traffic slowly. Border and rail upgrades are now underway on both sides, alongside a US$1.4bn revitalisation of the TAZARA line launched in 2025. From Nakonde the road runs south through Kapiri Mposhi to the Zambian copperbelt at Ndola and Kitwe, and on into the DRC — so a device that goes dark here is dark on one of the main routes for Copperbelt and Congolese freight.

Three things move against a connected asset at a crossing like this. The networks decide whether the device connects at all, on one operator's coverage and one roaming arrangement. The border puts Tanzanian networks on one side and Zambian networks on the other, across a single congested line, and every crossing means finding a new network and authenticating onto it. And the commercials shift underneath a long dwell. A single-network device meets all three at once at Tunduma–Nakonde, and any one of them is enough to take the tracker offline.

The pattern is the one the controller saw: a cell saturated by a queue that runs for kilometres, coverage that thins at the line, and a roaming handover into Zambia a single-SIM device cannot pre-empt. It is not the device and it is not the driver. It is a connectivity design that assumed one network would always be there.

What works at Tunduma–Nakonde, and why

CommsCloud is the operator layer for African IoT — the layer that keeps the connection working while networks, borders and commercials shift underneath it. The CloudConnect™ SIM carries several mobile networks on each side of the border rather than one. On the Tanzanian side that includes Vodacom, Airtel and Tigo; on the Zambian side, MTN Zambia, Airtel Zambia and Zamtel. The SIM holds the strongest available network and switches between them on its own, so the device rides out the saturated cell in the queue and finds a Zambian network on the far side without a manual swap.

Underneath the SIM, autonomous multi-IMSI failover moves the device between networks without anyone touching it. Local PGW breakout keeps the data path short instead of routing it back across the continent, which is what keeps a tracker responsive at the edge of coverage. And the OEM Settings Library holds the tested configurations for the devices fleets actually run, so a unit is provisioned to behave correctly on this corridor before it ships.

That is the difference between an asset and a traveller. A traveller's phone roams for convenience; a fleet asset has to stay connected, because the tracker is how you prove where the load is while it sits at the border for days. One SIM. All Borders. No Downtime.

What the numbers look like once you fix it

CommsCloud runs 780+ client deployments across 50+ African countries, with reach across 650+ mobile networks in 180+ countries and 99.8%+ core-network uptime, and activation in under 24 hours. On the Dar es Salaam Corridor that means a device stays online through the Tunduma–Nakonde dwell and the Tanzania–Zambia handover and keeps reporting south to the copperbelt and into the DRC — the same multi-network approach that kept BHL Group's 600 trucks online across six countries and cut its satellite costs by 30%.

What the engineering and operations conversation looks like

Most connectivity problems at a border are read as coverage problems and solved by adding another SIM. The more useful conversation starts a level down: how the device is configured, which data profile it runs, how its firmware handles a network drop, and whether it is set to hunt for a new network or to sit and retry the old one. That is the diagnostic we run before we quote anything, and it is why the OEM Settings Library exists — the fix is usually in how the device and the SIM are set up to behave, not in adding hardware.