Lisbon vs Johannesburg: Choosing the Right Data Centre for Your Market
Published: · Updated: · 5 min read · By Oluniyi D. Ajao
AFRICLOUD operates from two data centres: Lisbon, Portugal and Johannesburg, South Africa. The right choice depends on where your users are. This guide uses measured latency data from 39 countries to help you decide.
The Short Answer
If your users are in North Africa, West Africa, Europe or Brazil, choose Lisbon. If they are in Southern Africa, East Africa or the Indian Ocean region, choose Johannesburg. The table below shows the headline latency from each data centre to every country we serve.
Latency Overview: All 39 Countries
Latency is measured in milliseconds (ms). Lower is better. The Best column shows which data centre we recommend based on the lowest measured RTT to each country's capital or main city.
Data measured 2026-04-24 from our looking glass servers in Lisbon and Johannesburg. Each value is the minimum round-trip time across multiple ICMP samples to validated in-country IP prefixes. Where no value is shown, no validated targets responded from that vantage at the time of measurement.
| Country | Capital / Main City | Lisbon (ms) | Johannesburg (ms) | Best |
|---|---|---|---|---|
| Morocco | Casablanca | 11 | 196 | Lisbon |
| Tunisia | Tunis | 40 | 192 | Lisbon |
| Algeria | Algiers | 33 | 199 | Lisbon |
| Cape Verde | Praia | 36 | 175 | Lisbon |
| Mauritania | Nouakchott | 54 | Lisbon | |
| Libya | Tripoli | 47 | 199 | Lisbon |
| Gambia | Banjul | 47 | 234 | Lisbon |
| Senegal | Dakar | 42 | 181 | Lisbon |
| Guinea | Conakry | 91 | 242 | Lisbon |
| Egypt | Cairo | 56 | 209 | Lisbon |
| Togo | Lomé | 72 | 191 | Lisbon |
| Benin | Cotonou | 130 | 187 | Lisbon |
| Ivory Coast | Abidjan | 66 | 219 | Lisbon |
| Guinea-Bissau | Bissau | 86 | Lisbon | |
| Equatorial Guinea | Bata | 100 | Lisbon | |
| Sierra Leone | Freetown | 81 | 163 | Lisbon |
| Liberia | Monrovia | 79 | Lisbon | |
| Cameroon | Douala | 179 | 198 | Lisbon |
| Botswana | Gaborone | 127 | 5 | Johannesburg |
| Eswatini | Mbabane | 139 | 6 | Johannesburg |
| Mozambique | Maputo | 158 | 7 | Johannesburg |
| Lesotho | Maseru | 145 | 8 | Johannesburg |
| Zimbabwe | Harare | 127 | 17 | Johannesburg |
| Zambia | Lusaka | 144 | 22 | Johannesburg |
| Namibia | Windhoek | 122 | 34 | Johannesburg |
| Madagascar | Antananarivo | 159 | 28 | Johannesburg |
| Tanzania | Dar es Salaam | 157 | 45 | Johannesburg |
| Malawi | Lilongwe | 158 | 112 | Johannesburg |
| Mauritius | Port Louis | 170 | 39 | Johannesburg |
| Rwanda | Kigali | 174 | 71 | Johannesburg |
| Angola | Luanda | 100 | 52 | Johannesburg |
| Ethiopia | Addis Ababa | 99 | 71 | Johannesburg |
| Uganda | Kampala | 205 | 78 | Johannesburg |
| São Tomé | São Tomé | 152 | 60 | Johannesburg |
| DR Congo | Kinshasa | 124 | 30 | Johannesburg |
| Rep. of Congo | Brazzaville | 157 | Lisbon | |
| Burundi | Bujumbura | 177 | 71 | Johannesburg |
| Seychelles | Victoria | 126 | 77 | Johannesburg |
| Sudan | Khartoum | 91 | 231 | Lisbon |
Lisbon: Best for North and West Africa
The Lisbon data centre connects to DE-CIX Lisbon and multiple submarine cable systems serving the African west coast and Mediterranean. It delivers the lowest latency to 18 countries, with particularly strong performance for the Maghreb region.
Where Lisbon excels
- Under 15ms: Morocco (11ms)
- Under 40ms: Algeria, Cape Verde
- Under 65ms: Tunisia, Senegal, Gambia, Libya, Mauritania, Egypt
- Under 100ms: Ivory Coast, Togo, Liberia, Sierra Leone, Guinea-Bissau, Guinea, Sudan
- Under 200ms: Equatorial Guinea, Benin, Rep. of Congo, Cameroon
Lisbon also connects to South America via the EllaLink cable, making it a strong choice for serving Brazil and Portuguese-speaking markets on both sides of the Atlantic.
For per-city Brazil latency benchmarks (Fortaleza 73 ms, Recife 87 ms, São Paulo 107 ms), see our Lisbon-Brazil low-latency VPS guide.
Johannesburg: Best for Southern and East Africa
The Johannesburg data centre is located at Teraco Isando with direct peering at NAPAfrica IX, Africa's largest internet exchange with over 375 connected networks. It delivers the lowest latency to 20 countries, with single-digit millisecond response times across the SADC region.
Where Johannesburg excels
- Under 10ms: Botswana (5ms), Eswatini (6ms), Mozambique (7ms), Lesotho (8ms)
- Under 20ms: Zimbabwe (17ms)
- Under 45ms: Zambia, Madagascar, DR Congo, Namibia, Mauritius, Tanzania
- Under 80ms: Angola, São Tomé, Ethiopia, Rwanda, Burundi, Seychelles, Uganda
The sub-10ms latency to SADC countries is noteworthy. For applications that require near-real-time response: VoIP, financial platforms, gaming: Johannesburg effectively functions as a local data centre for the Southern African region.
Edge Cases: When the Choice Is Not Obvious
Angola
Angola is geographically closer to Johannesburg (51ms to Luanda) than to Lisbon (99ms). However, Angola has strong linguistic and business ties to Portugal, and many Angolan businesses already use European infrastructure. Both options work, but if latency is your priority, Johannesburg is the better choice. See the Angola country page for latency data to six Angolan cities from both data centres.
Sudan
Sudan was an edge case in earlier rounds (effectively a tie at 79–85ms), but our 2026-04-24 scan shows Khartoum reaching Lisbon in 91ms vs 231ms from Johannesburg: a 140ms gap. Sudanese users should deploy in Lisbon for the lowest latency. We cite the previous tie here for transparency: routing across submarine cable systems can shift between rounds.
Central Africa (DR Congo, Rep. of Congo, São Tomé)
Central African countries are closer to Johannesburg: DR Congo (Kinshasa) at 30ms vs 124ms from Lisbon, and São Tomé at 60ms vs 152ms. Rep. of Congo (Brazzaville) had only Lisbon-side validated targets in our 2026-04-24 scan (157ms), so we cannot confirm a Johannesburg figure for that destination. If your audience spans Central and West Africa, Lisbon may still be the right single-location choice since it serves West Africa well while Central Africa gets 120–160ms. Johannesburg serves Central Africa at 30–60ms but West Africa at 180–240ms.
Multi-Region Deployments
If your audience spans the entire continent, consider deploying in both data centres. A typical multi-region setup:
- Lisbon: serves North Africa, West Africa, Europe and Brazil
- Johannesburg: serves Southern Africa, East Africa, Indian Ocean and Central Africa
Use DNS-based routing (GeoDNS) or a CDN to direct users to their nearest server. This ensures no user on the continent is more than approximately 100ms from your application.
What Affects Latency Beyond Distance
Physical distance is the primary factor, but three other variables matter:
- Submarine cable routes: Traffic from West Africa to Lisbon follows cables along the African west coast (WACS, MainOne, ACE). Traffic from East Africa to Johannesburg uses cables landing at the south-eastern coast (SEACOM, 2Africa). These fixed routes determine actual latency more than straight-line distance.
- Peering quality: Johannesburg's NAPAfrica IX (375+ networks) and Lisbon's DE-CIX ensure traffic stays on short, direct paths rather than transiting through distant exchanges.
- Last-mile infrastructure: Latency from our data centre to a country's major city reflects backbone connectivity. Actual user experience also depends on local ISP quality, which varies significantly across Africa.
Test Before You Commit
The latency figures in this article are measured averages. Your actual experience may differ based on your ISP, time of day and network conditions. We provide a free tool to test for yourself:
- AFRICLOUD Looking Glass: Run ping, traceroute and MTR tests from both Lisbon and Johannesburg to any IP address or hostname.
Run tests from both locations to your target market and compare. The numbers do not lie.
Ready to Deploy?
Choose your data centre and deploy a VPS in under two minutes. All plans include the same hardware (AMD EPYC, NVMe storage), DDoS protection and full root access at both locations.