Corridors
The operator layer for African IoT
Connectivity that adapts as networks, borders and commercials shift. A guide to the four Southern-African crossings where fleet trackers go dark, and what keeps them reporting through.
Cross-border IoT connectivity is a SIM and network arrangement that keeps a vehicle's devices reporting as it moves between African countries, so a fleet operator running a regional corridor keeps an unbroken trace instead of a gap at every border post.
The gap is the point. A tracker does not usually fail because the hardware is wrong or the platform is misconfigured. It fails because the SIM underneath it is tied to one home network, and at a border that network either ends or hands over to a roaming partner that takes minutes to authenticate. The vehicle keeps moving. The data stops.
Three things shift at a border, not one
Networks. Coverage changes on the far side, and a single-IMSI SIM has to renegotiate from scratch. Cloud Connect multi-IMSI SIMs carry several operator identities on one card and switch between them autonomously, so the device attaches to a local network instead of waiting on a roaming handshake.
Borders. Each crossing has its own failure shape: a queue that parks vehicles in a congested cell, a one-stop post that clears trucks faster than their SIMs reattach, a bridge where four countries' networks overlap. The four guides below cover the crossings we see most.
Commercials. A contract per country is not a fix, it moves the problem into procurement. One agreement covering the profiles on the SIM means adding a country to a route is an operational change rather than a purchasing cycle.
What holds it together
Autonomous multi-IMSI failover across 50+ African countries, on a core network holding 99.8%+ uptime, reaching 650+ MNOs across 180+ countries for the wider footprint. Activation runs under 24 hours, so adding vehicles to a corridor is not a lead-time problem.
Buks Haulage runs this pattern across six SADC countries on a 600+ truck fleet, with no border-swap SIMs and no per-country contracts.
Border posts
Four crossings, four failure shapes
South Africa to Zimbabwe
Beitbridge
The busiest crossing on the north-south corridor, and the one where a tracker most often freezes mid-queue. Multi-IMSI failover keeps the trace continuous through the bottleneck.
Read the guideSouth Africa to Mozambique
Lebombo and Ressano Garcia
Daily Maputo Corridor shuttles lose data twice on a round trip, once eastbound and once westbound. One SIM carrying both countries' profiles removes the second gap as well as the first.
Read the guideBotswana, Zambia, Zimbabwe and Namibia
Kazungula
Four countries meet at the bridge, so a device can cycle through four mobile networks in a single crossing. Autonomous switching handles it without a driver touching the vehicle.
Read the guideZimbabwe to Zambia
Chirundu
One-stop processing clears trucks faster than a single-network SIM can reattach, which is how a Copperbelt run loses fifteen to twenty minutes of visibility at the gate.
Read the guideFAQ
Common questions
Why do fleet trackers stop reporting at African border posts?
A single-network SIM is tied to one home operator. At a border that network either ends or hands over to a roaming partner, and the re-authentication can take minutes while the vehicle keeps moving. The device is working; the connection underneath it is not.
Does one SIM work across multiple African countries?
Yes, if it is multi-IMSI. The SIM carries several operator identities and selects between them by location, automatically, on a single APN. No swap, no depot visit, and one commercial agreement rather than a contract per country.
Which African corridors does CommsCloud cover?
Connectivity reaches 50+ African countries. The four crossings documented here, Beitbridge, Lebombo and Ressano Garcia, Kazungula and Chirundu, are the Southern-African posts where fleet operators most often report losing visibility.
What happens on routes with weak coverage between borders?
The SIM falls back through the available radio technologies and attaches to whichever network is strongest at that point, rather than holding out for one operator. On long-haul SADC routes that fallback is what keeps the thinnest legs reporting.
Running trucks across African borders?
Tell us your corridors, your devices and your volumes, and we will map the connectivity before you commit to anything.