Malaba IoT connectivity for fleets

Malaba IoT connectivity, keeping your fleet visible on the Northern Corridor

Malaba is the busiest freight crossing between Kenya and Uganda, and the gate almost everything moving from Mombasa to Kampala has to clear. It is also where trucks sit for hours in staging yards, and where single-network trackers lose the thread.

Dawn in the Malaba yard

The trailer has been parked in the staging yard since the night before, waiting on paperwork. In Nairobi a controller pulls up the fleet map and finds a truck that should be halfway to Kampala still showing its last position back at the border — hours old. The dashboard says the device is offline. The driver, when he is reached, is fine, in the queue, doing what the queue requires: waiting.

What has actually happened is smaller and more ordinary than an outage. Packed into a yard with hundreds of other vehicles, the tracker is competing for one operator's cell along with every phone around it, and it is holding to that one network because that is all it has. When the truck finally clears and rolls across the line into Uganda, the device has to drop the Kenyan network and authenticate onto a Ugandan one before it can report again. For the stretch in between — the yard, the gate, the first kilometres into Tororo — the load is a guess.

None of this is exotic. It is the routine texture of a busy border, and it is exactly the part a single-SIM device is not built for. The controller is not missing a truck because the technology failed. He is missing it because the connectivity was designed for one network in one country, and Malaba is two.

Why Malaba is the lane that exposes connectivity weakness

Malaba carries the freight of the Northern Corridor — Mombasa port to Nairobi, on to Kampala, and beyond to Rwanda, Burundi, eastern DRC and South Sudan. It operates as a one-stop border post, with Kenyan and Ugandan agencies clearing traffic under one roof, and that helps, but it does not remove the queue. The delays here come mostly from customs and documentation and from cargo-seal and security procedures, and when those tighten the line grows fast: in July 2026 a change to cargo-seal rules pushed a queue roughly 35 km back into Kenya for several days and cut clearance from around 1,500 trucks a day to about 750. On a normal day the wait is measured in hours; during a disruption it runs far longer, and the connectivity has to hold across the whole of it.

Three things move against a connected asset on this corridor. The networks decide whether the device connects at all, on one operator's coverage and one roaming arrangement. The border puts Kenyan networks on one side of Malaba and Ugandan networks on the other, with a river and a queue between them, 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 in the same yard, and any one of them is enough to take the tracker offline.

The pattern is the one the controller saw: a saturated cell in a packed staging yard, coverage that thins at the line, and a roaming handover into Uganda 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 Malaba, 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 Malaba rather than one. On the Kenyan side that includes Safaricom, Airtel Kenya and Telkom Kenya; on the Ugandan side, MTN Uganda, Airtel Uganda and Africell. The SIM holds the strongest available network and switches between them on its own, so the device rides out the saturated cell in the yard and finds a Ugandan network across the line 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 a tracker that goes quiet at the border is a load you can no longer account for. 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 Northern Corridor that means a device stays online through the Malaba yard and the Kenya–Uganda handover and keeps reporting all the way to Kampala and beyond — 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.