Johannesburg network latency (JNB)
Round-trip measurements between Johannesburg (JNB) and 19 Hats Network PoPs, with route comparisons and downloadable probe data.
Johannesburg (JNB) is the African PoP in this dataset. Its published routes connect it with every other measurement origin.
Measurement round: 2026-08-16T04:07:28Z.
The published round covers 19 outbound routes from Johannesburg. Incoming routes are measured separately; neither direction describes last-mile performance.
Fastest routes from Johannesburg
Average round-trip time Β· lowest first
- London LON158.0 ms
- Amsterdam AMS163.2 ms
- Paris PAR164.4 ms
- Frankfurt FRA166.0 ms
- Marseille MRS172.0 ms
- Berlin BER172.1 ms
- Moscow MOW200.7 ms
- New York NYC221.8 ms
- Ashburn IAD229.0 ms
- Miami MIA259.9 ms
9 more routes
- Seattle SEA281.2 ms
- Los Angeles LAX285.5 ms
- Singapore SIN311.6 ms
- Hong Kong HKG318.0 ms
- SΓ£o Paulo GRU328.7 ms
- Taipei TPE329.8 ms
- Tokyo TYO360.5 ms
- Melbourne MEL406.2 ms
- Sydney SYD412.6 ms
Minimum, maximum and variation
| PoP | Min | Max | Stdev |
|---|---|---|---|
| London | 151.59 | 170.89 | 4.48 |
| Amsterdam | 158.68 | 177.43 | 4.23 |
| Paris | 158.64 | 177.46 | 4.15 |
| Frankfurt | 156.26 | 186.26 | 7.97 |
| Marseille | 168.24 | 182.06 | 3.29 |
| Berlin | 168.33 | 187.75 | 3.76 |
| Moscow | 196.07 | 218.52 | 4.34 |
| New York | 213.14 | 261.72 | 8.43 |
| Ashburn | 223.41 | 246.68 | 5.30 |
| Miami | 252.44 | 275.29 | 5.02 |
| Seattle | 267.91 | 315.60 | 9.73 |
| Los Angeles | 274.60 | 308.95 | 8.74 |
| Singapore | 301.09 | 347.05 | 9.83 |
| Hong Kong | 302.56 | 363.62 | 12.41 |
| SΓ£o Paulo | 319.02 | 366.86 | 9.87 |
| Taipei | 316.93 | 358.31 | 9.77 |
| Tokyo | 339.64 | 427.10 | 16.20 |
| Melbourne | 391.17 | 483.64 | 16.40 |
| Sydney | 391.98 | 456.66 | 16.76 |
Fastest routes into Johannesburg
Average round-trip time Β· lowest first
- Amsterdam AMS171.9 ms
- Berlin BER172.1 ms
- London LON179.6 ms
- Paris PAR180.9 ms
- Frankfurt FRA188.4 ms
- Marseille MRS198.5 ms
- Moscow MOW201.9 ms
- New York NYC221.5 ms
- Ashburn IAD228.3 ms
- Miami MIA259.8 ms
9 more routes
- Seattle SEA282.1 ms
- Los Angeles LAX287.2 ms
- Singapore SIN312.6 ms
- Hong Kong HKG316.7 ms
- Taipei TPE331.0 ms
- SΓ£o Paulo GRU333.8 ms
- Tokyo TYO359.2 ms
- Melbourne MEL405.5 ms
- Sydney SYD412.5 ms
Minimum, maximum and variation
| PoP | Min | Max | Stdev |
|---|---|---|---|
| Amsterdam | 163.56 | 197.47 | 6.53 |
| Berlin | 163.72 | 199.65 | 7.34 |
| London | 171.60 | 203.66 | 5.96 |
| Paris | 176.39 | 195.60 | 3.41 |
| Frankfurt | 182.33 | 218.93 | 6.75 |
| Marseille | 194.33 | 207.86 | 3.18 |
| Moscow | 192.01 | 232.17 | 7.94 |
| New York | 209.09 | 252.44 | 9.18 |
| Ashburn | 216.38 | 264.39 | 10.74 |
| Miami | 252.44 | 277.90 | 6.11 |
| Seattle | 273.42 | 300.55 | 6.90 |
| Los Angeles | 281.06 | 306.43 | 5.36 |
| Singapore | 303.47 | 332.30 | 7.16 |
| Hong Kong | 301.28 | 350.25 | 11.99 |
| Taipei | 322.36 | 356.12 | 6.31 |
| SΓ£o Paulo | 321.14 | 369.06 | 10.62 |
| Tokyo | 339.59 | 411.36 | 15.79 |
| Melbourne | 387.75 | 464.78 | 16.64 |
| Sydney | 399.32 | 451.86 | 12.82 |
RTT and geographic distance
Location
- Location: Johannesburg, South Africa (Africa)
- Region: Africa
- Role: Backbone interconnection point for Hats Network (AS203314)
- Public city reference: GeoNames 993800; -26.20227, 28.04363
- Coverage: RTT measurements to 19 other PoPs across 4 continents
Interconnection
- Facility: JNB1
- Upstream transit: HE Only
Round Summary
| Metric | Value |
|---|---|
| Fastest Route | πΏπ¦ Johannesburg (JNB) β π¬π§ London (LON) (158 ms); Fair |
| Slowest Route | πΏπ¦ Johannesburg (JNB) β π¦πΊ Sydney (SYD) (412.6 ms) |
| Average RTT | 260.1 ms |
| Average Jitter | 2.18 ms |
| Average Packet Loss | 0.06% |
| Best Fiber Efficiency | 57.5% |
| Intra-Region Peers | 0 PoP in Africa |
| Total Routes | 19 outbound / 19 inbound (100% coverage) |
Jitter, packet-loss, percentile, and trend fields are estimated comparative indicators. Read the theoretical fiber latency methodology.
Regional Routes
Johannesburg is Hats Network's only PoP in Africa. The lowest RTT in this round is to London (LON) at 158 ms RTT.
Johannesburg is inland in northeastern South Africa.
Outbound Latency from Johannesburg (JNB)
Round-trip time in milliseconds from Johannesburg to all other backbone PoPs, sorted fastest to slowest.
| Destination | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| π¬π§ London (LON) | 158 | 88.52 ms | 56% | 0.77 ms | 0.12% | Fair |
| π³π± Amsterdam (AMS) | 163.2 | 88.05 ms | 54% | 1.84 ms | 0% | Fair |
| π«π· Paris (PAR) | 164.4 | 85.17 ms | 51.8% | 1.05 ms | 0% | Fair |
| π©πͺ Frankfurt (FRA) | 166 | 84.87 ms | 51.1% | 1.86 ms | 0.11% | Fair |
| π«π· Marseille (MRS) | 172 | 78.71 ms | 45.8% | 1.53 ms | 0% | Fair |
| π©πͺ Berlin (BER) | 172.1 | 86.53 ms | 50.3% | 1.75 ms | 0.11% | Fair |
| π·πΊ Moscow (MOW) | 200.7 | 89.37 ms | 44.5% | 2.17 ms | 0.16% | Fair |
| πΊπΈ New York (NYC) | 221.8 | 125.67 ms | 56.7% | 2.01 ms | 0% | Fair |
| πΊπΈ Ashburn (IAD) | 229 | 128.11 ms | 55.9% | 1.29 ms | 0% | Fair |
| πΊπΈ Miami (MIA) | 259.9 | 126.78 ms | 48.8% | 3.06 ms | 0.1% | High |
| πΊπΈ Seattle (SEA) | 281.2 | 161.61 ms | 57.5% | 1.91 ms | 0.11% | High |
| πΊπΈ Los Angeles (LAX) | 285.5 | 163.35 ms | 57.2% | 2.14 ms | 0.01% | High |
| πΈπ¬ Singapore (SIN) | 311.6 | 84.85 ms | 27.2% | 3.35 ms | 0% | High |
| ππ° Hong Kong (HKG) | 318 | 104.93 ms | 33% | 3.32 ms | 0.19% | High |
| π§π· SΓ£o Paulo (GRU) | 328.7 | 72.88 ms | 22.2% | 2.32 ms | 0.06% | High |
| πΉπΌ Taipei (TPE) | 329.8 | 112.87 ms | 34.2% | 3.33 ms | 0% | High |
| π―π΅ Tokyo (TYO) | 360.5 | 132.57 ms | 36.8% | 2.79 ms | 0.06% | High |
| π¦πΊ Melbourne (MEL) | 406.2 | 101.33 ms | 24.9% | 2.56 ms | 0% | High |
| π¦πΊ Sydney (SYD) | 412.6 | 108.32 ms | 26.3% | 2.3 ms | 0.07% | High |
Fastest Routes to Johannesburg (JNB)
The 10 fastest measured routes to Johannesburg, ranked by average RTT. Min / max / stdev are computed from the same measurement round (50 ICMP echo probes per route, 100 ms interval); routes without a published per-sample round show the measured average RTT only.
| Rank | Source | Avg RTT | Min | Max | Stdev |
|---|---|---|---|---|---|
| 1 | π³π± Amsterdam (AMS) | 171.9 ms | 163.56 ms | 197.47 ms | 6.53 ms |
| 2 | π©πͺ Berlin (BER) | 172.1 ms | 163.72 ms | 199.65 ms | 7.34 ms |
| 3 | π¬π§ London (LON) | 179.6 ms | 171.6 ms | 203.66 ms | 5.96 ms |
| 4 | π«π· Paris (PAR) | 180.9 ms | 176.39 ms | 195.6 ms | 3.41 ms |
| 5 | π©πͺ Frankfurt (FRA) | 188.4 ms | 182.33 ms | 218.93 ms | 6.75 ms |
| 6 | π«π· Marseille (MRS) | 198.5 ms | 194.33 ms | 207.86 ms | 3.18 ms |
| 7 | π·πΊ Moscow (MOW) | 201.9 ms | 192.01 ms | 232.17 ms | 7.94 ms |
| 8 | πΊπΈ New York (NYC) | 221.5 ms | 209.09 ms | 252.44 ms | 9.18 ms |
| 9 | πΊπΈ Ashburn (IAD) | 228.3 ms | 216.38 ms | 264.39 ms | 10.74 ms |
| 10 | πΊπΈ Miami (MIA) | 259.8 ms | 252.44 ms | 277.9 ms | 6.11 ms |
Inbound Latency to Johannesburg (JNB)
Round-trip time in milliseconds from all other PoPs to Johannesburg. The measurement origin matters: inbound and outbound RTT can differ for the same pair.
| Source | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| π³π± Amsterdam (AMS) | 171.9 | 88.05 ms | 51.2% | 1.1 ms | 0.1% | Fair |
| π©πͺ Berlin (BER) | 172.1 | 86.53 ms | 50.3% | 1.56 ms | 0% | Fair |
| π¬π§ London (LON) | 179.6 | 88.52 ms | 49.3% | 0.86 ms | 0% | Fair |
| π«π· Paris (PAR) | 180.9 | 85.17 ms | 47.1% | 0.94 ms | 0.17% | Fair |
| π©πͺ Frankfurt (FRA) | 188.4 | 84.87 ms | 45% | 1.61 ms | 0.1% | Fair |
| π«π· Marseille (MRS) | 198.5 | 78.71 ms | 39.7% | 1.78 ms | 0% | Fair |
| π·πΊ Moscow (MOW) | 201.9 | 89.37 ms | 44.3% | 1.29 ms | 0% | Fair |
| πΊπΈ New York (NYC) | 221.5 | 125.67 ms | 56.7% | 2.09 ms | 0% | Fair |
| πΊπΈ Ashburn (IAD) | 228.3 | 128.11 ms | 56.1% | 1.05 ms | 0.04% | Fair |
| πΊπΈ Miami (MIA) | 259.8 | 126.78 ms | 48.8% | 1.51 ms | 0.19% | High |
| πΊπΈ Seattle (SEA) | 282.1 | 161.61 ms | 57.3% | 1.53 ms | 0.15% | High |
| πΊπΈ Los Angeles (LAX) | 287.2 | 163.35 ms | 56.9% | 1.6 ms | 0.08% | High |
| πΈπ¬ Singapore (SIN) | 312.6 | 84.85 ms | 27.1% | 1.51 ms | 0.19% | High |
| ππ° Hong Kong (HKG) | 316.7 | 104.93 ms | 33.1% | 3.12 ms | 0% | High |
| πΉπΌ Taipei (TPE) | 331 | 112.87 ms | 34.1% | 1.92 ms | 0% | High |
| π§π· SΓ£o Paulo (GRU) | 333.8 | 72.88 ms | 21.8% | 3.1 ms | 0.07% | High |
| π―π΅ Tokyo (TYO) | 359.2 | 132.57 ms | 36.9% | 2.19 ms | 0.05% | High |
| π¦πΊ Melbourne (MEL) | 405.5 | 101.33 ms | 25% | 3.75 ms | 0.06% | High |
| π¦πΊ Sydney (SYD) | 412.5 | 108.32 ms | 26.3% | 3.8 ms | 0% | High |
Questions
What is the fastest route to Johannesburg?
The fastest measured route to Johannesburg (JNB) is Amsterdam (AMS) β Johannesburg (JNB), averaging 171.9 ms RTT (Fair).
What is the fastest route from Johannesburg?
The fastest measured route from Johannesburg (JNB) is Johannesburg (JNB) β London (LON), averaging 158 ms RTT (Fair).
How well connected is Johannesburg to the Hats Network backbone?
Johannesburg (JNB) maintains measured routes to all 19 other PoPs across 4 continents. The slowest route, Johannesburg (JNB) β Sydney (SYD), averages 412.6 ms RTT.
Round published August 16, 2026. All 20 PoPs Β· Dataset and licence.
Tokyo network latency (TYO)
Round-trip measurements between Tokyo (TYO) and 19 Hats Network PoPs, with route comparisons and downloadable probe data.
BGP Communities
Complete reference for BGP community strings for AS203314 traffic engineering. Internal communities for route origin, PoP, region tagging, and control communities for blackhole, propagation, prepending. and path manipulation.