Africa's IoT connectivity, country by country: where 4G ends, what LoRaWAN plan applies, who approves the radio.

The network decision is made per site, not per brochure — but the facts that decide it are national: which frequency plan the regulator allows, how far the towers reach past the industrial belt, whose stamp the module needs, and when the cheap 2G tracker stops working. The lookup, nineteen countries deep, for the stack we actually deploy: private LoRaWAN plus 4G.

By Frank Guo · Technology & Product Leadership, addanode

TL;DR — Across Africa the same two-layer design keeps winning: private LoRaWAN for the many low-data sensors on a site you control (coverage you own, batteries for years, no per-device SIM), and 4G — Cat-4 for gateways, Cat-1 for standalone nodes — for backhaul and for the few sites with dependable towers. The national facts change three things. Frequency plan: Southern and Central Africa are listed on the EU863-870 plan; Kenya, Nigeria and Egypt run EU868 in practice; a few East African allocations differ, so the gateway is ordered to the plan, not to a default. Type approval: every country has a regulator whose stamp the module needs — ICASA, CA, NCC, NCA, TCRA, ZICTA, BOCRA, POTRAZ, UCC and their peers. Sunsets: South Africa has stopped activating 2G/3G-only devices and Nigeria's largest operator planned its 2G switch-off; elsewhere the sunset is gradual — but nothing new goes on 2G anywhere. NB-IoT and Sigfox exist in a handful of markets and are compared here, not deployed.

The national facts on one table

Frequency plans are as listed by The Things Network's country table (marked "listed") or as established in practice by the LoRaWAN community where the regulator has not been listed (marked "in practice — confirm"). Coverage statements are our field experience per country page. Cellular IoT and sunset columns are for comparison and planning; they are not part of the stack we deploy.

Country Where 4G is dependable — and where it ends LoRaWAN plan Type approval Cellular IoT / sunset notes (comparison only)
KenyaNairobi–Thika and Nairobi–Mombasa corridors; thin at farms, quarries, boreholesEU868 in practice — confirmCommunications Authority of Kenya (CA)Safaricom has deployed NB-IoT for utility metering programmes; no published 2G sunset date
ZambiaLusaka and the Copperbelt towns; off the line of rail it fadesEU863-870 (listed)ZICTAZESCO eight-hour load-shedding schedules — towers and sites both need buffering
TanzaniaDar es Salaam, Arusha, Mwanza, Dodoma; weak at mines, wellfields, farmsEU863-870 (listed)TCRAGrid-works rolling cuts affect tower uptime regionally
GhanaAccra, Tema, Kumasi, Takoradi; patchier rurallyEU868 in practice — confirmNCALegacy-network retirement expected around 2030 (operator statements)
NigeriaLagos, Ogun and the industrial clusters; dual-SIM failover recommendedEU868 in practice — confirmNCCMTN planned a 2G switch-off for December 2025 — 2G-only trackers are stranded assets
BotswanaGaborone, Francistown and the main roads; hours of nothing betweenEU863-870 (listed)BOCRASatellite backhaul for the truly remote
ZimbabweHarare, Bulawayo and the main corridorsEU863-870 (listed)POTRAZMonths without national load shedding in 2026 — the site, not the tower, is the constraint
UgandaKampala, Jinja, the Namanve park; weaker up-countryRegional allocation differs from EU868 in some listings — confirm with UCC before ordering gatewaysUCCRestoration times ~20 h after the UEDCL handover — buffer accordingly
South AfricaUniversal; 5G growingEU863-870 (listed)ICASA2G/3G-only activations barred since end-2024; shutdown operator-timed (gazette target end-2027); NB-IoT one carrier
AngolaLuanda, Lobito corridor; interruptions are faults and maintenance, not rationingEU863-870 (listed)INACOM
MozambiqueMaputo, Beira, Nacala corridorsEU863-870 (listed)INCMCyclone resilience: solar + local memory as a specification
DR CongoKinshasa, Lubumbashi, the Katanga minesEU863-870 (listed)ARPTCGensets and solar as the default power
MalawiBlantyre, LilongweEU863-870 (listed)MACRANational blackout August 2026 — buffering is the design
Côte d'IvoireAbidjan, Yamoussoukro, San Pedro; comparatively reliable gridEU868 in practice — confirmARTCI
SénégalDakar, Diamniadio, ThièsEU868 in practice — confirmARTP
CamerounDouala, YaoundéEU868 in practice — confirmARTLoad shedding has normalised self-generation
EthiopiaAddis Ababa and the industrial parksNot listed — confirm with ECAECAImport documentation is the slow step, not the network
RwandaKigali and the SEZ; relatively reliable powerNot listed — confirm with RURARURA
EgyptCairo, the new cities and the industrial zonesEU868 in practice — confirmNTRAMetering hardware market saturated; value sits in the telemetry layer

What the frequency plan decides

A LoRaWAN gateway and its sensors are built for one regional plan. Most of the continent sits on the European 863–870 MHz plan (EU868) — either listed by the regulator or adopted in practice — which is why hardware pre-configured in Johannesburg travels well. The exceptions matter exactly once: at ordering time. Where a listing differs or is absent — Uganda, Ethiopia, Rwanda and several West African markets — the plan is confirmed with the regulator before the gateway is specified, because a gateway on the wrong plan is a paperweight with an antenna. The Southern African regulators coordinate allocations through CRASA, which is why the SADC column above is uniform.

What type approval decides

Every radio module operating in a country needs that country's regulator to have approved it — the list above from ICASA to RURA. In practice this shapes the bill of materials more than the network choice does: modules with existing approvals in the target country ship; modules without them wait for a certification cycle. It is the reason our hardware list per country is short and repeatable, and the reason a "cheaper" module found online is rarely cheaper by the time it is legal to switch on.

What the sunsets decide

Africa's 2G and 3G networks are retiring gradually and selectively rather than on one date, but the direction is set: South Africa has barred new 2G/3G-only activations, Nigeria's largest operator planned its 2G switch-off, Ghana's operators talk about the end of the decade. The buying rule is the same everywhere — nothing new goes on 2G. A fleet of cheap GSM trackers bought this year is an asset with a shutdown date somebody else controls; Cat-1 and Cat-1bis modules attach to every LTE network in the table and need no special carrier support. Our LTE category guide unpacks which "4G" a device should be.

Which site gets which network

Site Sensor link Backhaul Power and buffering
Factory in the industrial belt (Tema, Thika, Lusaka, Ogun)Wired or private LoRaWAN to an edge gatewayCat-4 4G, dual-SIM where carriers competeMains + genset logged; gateway on UPS, buffers through outages
Utility network (DMAs, reservoirs)Private LoRaWAN from reservoir-sited gateways4G per gatewaySolar nodes; store-and-forward
Borehole or pump station off the corridorLoRaWAN to the nearest gateway; Cat-1 node if solitary4G where present; otherwise the LoRaWAN hopSolar; months between visits
Mine property (Copperbelt, Guinea corridors, gold belt)Private LoRaWAN across the property; site LTE where it existsFibre or 4G to the mine networkBuffering sized for eight-hour outages; IS-certified hardware where required
Cold-chain vehicle, reeferCat-1 logger on board4G, store-and-forward between signalVehicle power; logger battery
Village scheme, standpipe, kioskLoRaWAN if a scheme gateway exists; else a Cat-1 node4G where present; satellite for the truly remote (Botswana)Solar; heartbeat as the first signal
Scattered national estate (bank branches, fuel stations, telecom shelters)Cat-1 node per site4G with carrier failoverSite genset is the monitored asset

Three rules that hold in every country

  • Own the coverage where the sensors are; rent it where the gateway is. LoRaWAN across the site, 4G out of it. The per-site question is only which hop the sensor takes.
  • Order the gateway to the plan, the module to the regulator. Frequency plan and type approval are national facts that decide the bill of materials before any coverage map does.
  • The record has to survive the grid — and the tower's grid. Load shedding takes towers down as well as sites; local buffering at every node is what keeps a compliance or production record continuous.

How we deliver: hardware pre-configured in Johannesburg to the country's plan and approvals, installation by your technicians or a local partner under live remote guidance, LoRaWAN plus 4G per site, local buffering everywhere. Country detail on the industrial-IoT pages: Kenya · Zambia · Tanzania · Ghana · Nigeria · Botswana · Zimbabwe · Uganda.

FAQ

IoT connectivity across Africa — common questions

Which LoRaWAN frequency plan is used in Africa?

Most of the continent uses the European 863–870 MHz plan (EU868). Southern and Central African countries — South Africa, Zambia, Tanzania, Botswana, Zimbabwe, Angola, Mozambique, DR Congo, Malawi — are listed on it; Kenya, Nigeria, Egypt and much of West Africa run it in practice. A few allocations differ or are unlisted (Uganda, Ethiopia, Rwanda), so the plan is confirmed with the regulator before gateways are ordered.

Is 4G reliable enough for IoT in Africa?

In the industrial belts and along the corridors, yes — Nairobi–Thika, Accra–Tema, Lagos–Ogun, Lusaka and the Copperbelt towns, Dar es Salaam. It fades at farms, wellfields, mines and villages, which is where private LoRaWAN takes over. The second constraint is power: load shedding takes towers down as well as sites, so every node buffers locally regardless of the link.

Do IoT devices need type approval in each African country?

Yes. Every radio module needs the national regulator's approval — ICASA in South Africa, the Communications Authority in Kenya, NCC in Nigeria, NCA in Ghana, TCRA in Tanzania, ZICTA in Zambia, BOCRA in Botswana, POTRAZ in Zimbabwe, UCC in Uganda, and their peers. Approved modules ship; unapproved ones wait for a certification cycle, which is why a short, repeatable hardware list per country matters.

Is NB-IoT available in Africa?

In a handful of markets: Vodacom in South Africa commercially, Safaricom in Kenya for utility programmes, and trials elsewhere. It needs carrier deployment site by site, handles mobility poorly, and — like Sigfox — is a comparison point rather than part of the stack we deploy. Private LoRaWAN covers the battery-sensor role without depending on a carrier's rollout map.

When are 2G and 3G being switched off in Africa?

Gradually and by operator rather than on one continental date. South Africa barred new 2G/3G-only activations from the end of 2024 with a gazetted end-2027 target now left to operator timing; Nigeria's largest operator planned its 2G switch-off for December 2025; Ghana's operators point to around 2030. The practical rule everywhere: nothing new goes on 2G.

How do you connect a site in a country where you have no office?

Remote assessment; gateway and nodes pre-configured in Johannesburg to the country's frequency plan and type approvals; installation by your electricians or a local partner under live remote guidance; commissioning over the link. Private LoRaWAN where the sensors are, 4G where the gateway is, and local buffering so the record survives both the site's outages and the tower's.

Primary sources

Coverage statements are field experience as of September 2026 and are refreshed with the country pages; frequency-plan and sunset statements are refreshed when a regulator publishes a change. Plans marked "confirm" are verified per project before hardware is ordered.

Tell us the country and the site. We'll pick the hop.

Frequency plan, type approval, coverage and buffering — settled before hardware ships from Johannesburg.