🇿🇦 Johannesburg Ping & Network Latency (JNB) | AS203314
Johannesburg (JNB) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.
🇿🇦 Johannesburg (JNB)
Johannesburg anchors Hats Network's African footprint, connecting Southern Africa to the global backbone via the Europe–Africa corridors through London, Marseille and Frankfurt.
This page provides round-trip time (RTT) latency metrics between the Johannesburg (JNB) PoP and every other node on the Hats Network (AS203314) global backbone.
Average RTT from Johannesburg to every other PoP
Round average of 19 measured routes, sorted slowest first · whiskers mark ±1 standard deviation within each round
How to read this chart
Each bar is the average round-trip time of one 50-probe ICMP echo round from Johannesburg (JNB) to the destination PoP. The whisker at the end of each bar spans the average ± one standard deviation of that round — long whiskers mark jittery routes, short whiskers mark stable ones.
Full 19-destination dataset
| Destination | Avg RTT (ms) | Stdev (ms) | Distance (km) |
|---|---|---|---|
| Sydney (SYD) | 411.60 | 19.69 | 11,061 |
| Melbourne (MEL) | 405.80 | 7.97 | 10,347 |
| Tokyo (TYO) | 362.70 | 9.43 | 13,538 |
| Taipei (TPE) | 333.00 | 6.41 | 11,525 |
| São Paulo (GRU) | 329.70 | 10.65 | 7,442 |
| Hong Kong (HKG) | 318.40 | 9.95 | 10,716 |
| Singapore (SIN) | 309.50 | 10.36 | 8,664 |
| Los Angeles (LAX) | 284.40 | 9.54 | 16,680 |
| Seattle (SEA) | 280.30 | 6.85 | 16,503 |
| Miami (MIA) | 259.30 | 4.41 | 12,946 |
| Ashburn (IAD) | 228.50 | 7.26 | 13,082 |
| New York (NYC) | 221.60 | 5.41 | 12,833 |
| Moscow (MOW) | 201.70 | 5.43 | 9,126 |
| Berlin (BER) | 172.10 | 4.79 | 8,837 |
| Marseille (MRS) | 172.00 | 3.19 | 8,037 |
| Frankfurt (FRA) | 166.00 | 3.33 | 8,667 |
| Paris (PAR) | 164.40 | 4.82 | 8,697 |
| Amsterdam (AMS) | 163.20 | 7.89 | 8,992 |
| London (LON) | 158.00 | 7.54 | 9,039 |
RTT vs. distance from Johannesburg
Average RTT against great-circle distance for the same 19 routes · shaded bands mark latency tiers · points are colored by continent
How to read this chart
Each point is one destination PoP: the horizontal axis is the measured average RTT, the vertical axis is the WGS-84 great-circle distance from Johannesburg. Points close to the bottom-left are routes that run near the physical fiber limit; points drifting upward-right follow longer paths. The shaded vertical bands mark the latency tiers (Ultra-Low <30 ms, Low 30–80 ms, Mid 80–150 ms, High >150 ms).
Underlying measurements
| Destination | Avg RTT (ms) | Distance (km) |
|---|---|---|
| Sydney (SYD) | 411.60 | 11,061 |
| Melbourne (MEL) | 405.80 | 10,347 |
| Tokyo (TYO) | 362.70 | 13,538 |
| Taipei (TPE) | 333.00 | 11,525 |
| São Paulo (GRU) | 329.70 | 7,442 |
| Hong Kong (HKG) | 318.40 | 10,716 |
| Singapore (SIN) | 309.50 | 8,664 |
| Los Angeles (LAX) | 284.40 | 16,680 |
| Seattle (SEA) | 280.30 | 16,503 |
| Miami (MIA) | 259.30 | 12,946 |
| Ashburn (IAD) | 228.50 | 13,082 |
| New York (NYC) | 221.60 | 12,833 |
| Moscow (MOW) | 201.70 | 9,126 |
| Berlin (BER) | 172.10 | 8,837 |
| Marseille (MRS) | 172.00 | 8,037 |
| Frankfurt (FRA) | 166.00 | 8,667 |
| Paris (PAR) | 164.40 | 8,697 |
| Amsterdam (AMS) | 163.20 | 8,992 |
| London (LON) | 158.00 | 9,039 |
Fastest routes into Johannesburg
Measured RTT from 19 other PoPs into Johannesburg (JNB), sorted fastest first · each row spans min–max with a dot at the average
How to read this chart
Each row is one 50-probe ICMP echo round from another PoP into Johannesburg (JNB): the line spans the minimum to maximum round-trip time observed, and the dot marks the average. Short rows are stable routes; rows sitting far right are slow ones. RTT is not symmetric — the path back into Johannesburg can differ from the outbound path shown in the charts above.
Full 19-source dataset
| Source | Avg RTT (ms) | Min (ms) | Max (ms) | Distance (km) |
|---|---|---|---|---|
| Amsterdam (AMS) | 171.90 | 161.36 | 195.12 | 8,992 |
| Berlin (BER) | 172.10 | 168.43 | 190.03 | 8,837 |
| London (LON) | 179.80 | 168.72 | 213.58 | 9,039 |
| Paris (PAR) | 180.90 | 175.49 | 194.96 | 8,697 |
| Frankfurt (FRA) | 188.90 | 177.16 | 223.52 | 8,667 |
| Marseille (MRS) | 198.90 | 191.78 | 215.05 | 8,037 |
| Moscow (MOW) | 201.10 | 196.79 | 210.00 | 9,126 |
| New York (NYC) | 221.80 | 212.01 | 253.24 | 12,833 |
| Ashburn (IAD) | 228.30 | 223.49 | 249.10 | 13,082 |
| Miami (MIA) | 259.40 | 254.03 | 274.66 | 12,946 |
| Seattle (SEA) | 282.70 | 274.28 | 295.43 | 16,503 |
| Los Angeles (LAX) | 284.30 | 270.58 | 321.00 | 16,680 |
| Singapore (SIN) | 310.50 | 301.47 | 325.58 | 8,664 |
| Hong Kong (HKG) | 316.90 | 298.36 | 350.82 | 10,716 |
| Taipei (TPE) | 330.90 | 322.14 | 348.94 | 11,525 |
| São Paulo (GRU) | 333.40 | 325.13 | 356.59 | 7,442 |
| Tokyo (TYO) | 360.50 | 354.61 | 378.53 | 13,538 |
| Melbourne (MEL) | 405.00 | 389.14 | 467.50 | 10,347 |
| Sydney (SYD) | 411.30 | 403.78 | 428.44 | 11,061 |
PoP Highlights
- 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
Facility & Interconnection
- Facility: JNB1
- Upstream transit: HE Only
Latency Summary
| Metric | Value |
|---|---|
| Fastest Route | 🇿🇦 Johannesburg (JNB) → 🇬🇧 London (LON) (158 ms) — Fair |
| Slowest Route | 🇿🇦 Johannesburg (JNB) → 🇦🇺 Sydney (SYD) (411.6 ms) |
| Average RTT | 260.1 ms |
| Average Jitter | 2.24 ms |
| Average Packet Loss | 0.07% |
| Best Fiber Efficiency | 57.7% |
| 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.
Geographic & Network Position
Johannesburg is Hats Network's only PoP in Africa. The nearest measured backbone PoP is London (LON) at 158 ms RTT.
Johannesburg is Hats Network's African anchor, connecting Southern Africa to Europe and Asia via the continent's coastal submarine landings.
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% | 1.52 ms | 0% | Fair |
| 🇳🇱 Amsterdam (AMS) | 163.2 | 88.05 ms | 54% | 1.79 ms | 0.04% | Fair |
| 🇫🇷 Paris (PAR) | 164.4 | 85.17 ms | 51.8% | 1.71 ms | 0.11% | Fair |
| 🇩🇪 Frankfurt (FRA) | 166 | 84.87 ms | 51.1% | 1.52 ms | 0% | Fair |
| 🇫🇷 Marseille (MRS) | 172 | 78.71 ms | 45.8% | 1.45 ms | 0.09% | Fair |
| 🇩🇪 Berlin (BER) | 172.1 | 86.53 ms | 50.3% | 0.9 ms | 0% | Fair |
| 🇷🇺 Moscow (MOW) | 201.7 | 89.37 ms | 44.3% | 2.04 ms | 0.12% | Fair |
| 🇺🇸 New York (NYC) | 221.6 | 125.67 ms | 56.7% | 2.28 ms | 0.08% | Fair |
| 🇺🇸 Ashburn (IAD) | 228.5 | 128.11 ms | 56.1% | 2.02 ms | 0% | Fair |
| 🇺🇸 Miami (MIA) | 259.3 | 126.78 ms | 48.9% | 1.77 ms | 0.16% | High |
| 🇺🇸 Seattle (SEA) | 280.3 | 161.61 ms | 57.7% | 3.03 ms | 0.1% | High |
| 🇺🇸 Los Angeles (LAX) | 284.4 | 163.35 ms | 57.4% | 3.35 ms | 0.08% | High |
| 🇸🇬 Singapore (SIN) | 309.5 | 84.85 ms | 27.4% | 2.85 ms | 0.12% | High |
| 🇭🇰 Hong Kong (HKG) | 318.4 | 104.93 ms | 33% | 1.96 ms | 0.08% | High |
| 🇧🇷 São Paulo (GRU) | 329.7 | 72.88 ms | 22.1% | 1.83 ms | 0% | High |
| 🇹🇼 Taipei (TPE) | 333 | 112.87 ms | 33.9% | 2.19 ms | 0.17% | High |
| 🇯🇵 Tokyo (TYO) | 362.7 | 132.57 ms | 36.6% | 3.8 ms | 0% | High |
| 🇦🇺 Melbourne (MEL) | 405.8 | 101.33 ms | 25% | 3.4 ms | 0% | High |
| 🇦🇺 Sydney (SYD) | 411.6 | 108.32 ms | 26.3% | 3.15 ms | 0.15% | 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 | 161.36 ms | 195.12 ms | 7.13 ms |
| 2 | 🇩🇪 Berlin (BER) | 172.1 ms | 168.43 ms | 190.03 ms | 3.66 ms |
| 3 | 🇬🇧 London (LON) | 179.8 ms | 168.72 ms | 213.58 ms | 8.97 ms |
| 4 | 🇫🇷 Paris (PAR) | 180.9 ms | 175.49 ms | 194.96 ms | 4.67 ms |
| 5 | 🇩🇪 Frankfurt (FRA) | 188.9 ms | 177.16 ms | 223.52 ms | 8.45 ms |
| 6 | 🇫🇷 Marseille (MRS) | 198.9 ms | 191.78 ms | 215.05 ms | 5.46 ms |
| 7 | 🇷🇺 Moscow (MOW) | 201.1 ms | 196.79 ms | 210 ms | 3.15 ms |
| 8 | 🇺🇸 New York (NYC) | 221.8 ms | 212.01 ms | 253.24 ms | 8.25 ms |
| 9 | 🇺🇸 Ashburn (IAD) | 228.3 ms | 223.49 ms | 249.1 ms | 4.95 ms |
| 10 | 🇺🇸 Miami (MIA) | 259.4 ms | 254.03 ms | 274.66 ms | 4.36 ms |
Inbound Latency to Johannesburg (JNB)
Round-trip time in milliseconds from all other PoPs to Johannesburg. Network paths may be asymmetric — inbound and outbound RTT can differ for the same city pair.
| Source | RTT (ms) | Fiber Floor | Efficiency | Jitter | Loss | Tier |
|---|---|---|---|---|---|---|
| 🇳🇱 Amsterdam (AMS) | 171.9 | 88.05 ms | 51.2% | 1.6 ms | 0.15% | Fair |
| 🇩🇪 Berlin (BER) | 172.1 | 86.53 ms | 50.3% | 0.82 ms | 0.06% | Fair |
| 🇬🇧 London (LON) | 179.8 | 88.52 ms | 49.2% | 2.06 ms | 0% | Fair |
| 🇫🇷 Paris (PAR) | 180.9 | 85.17 ms | 47.1% | 0.93 ms | 0.07% | Fair |
| 🇩🇪 Frankfurt (FRA) | 188.9 | 84.87 ms | 44.9% | 2.11 ms | 0% | Fair |
| 🇫🇷 Marseille (MRS) | 198.9 | 78.71 ms | 39.6% | 1.65 ms | 0.16% | Fair |
| 🇷🇺 Moscow (MOW) | 201.1 | 89.37 ms | 44.4% | 2.38 ms | 0% | Fair |
| 🇺🇸 New York (NYC) | 221.8 | 125.67 ms | 56.7% | 2.56 ms | 0.01% | Fair |
| 🇺🇸 Ashburn (IAD) | 228.3 | 128.11 ms | 56.1% | 2.29 ms | 0.08% | Fair |
| 🇺🇸 Miami (MIA) | 259.4 | 126.78 ms | 48.9% | 1.78 ms | 0.07% | High |
| 🇺🇸 Seattle (SEA) | 282.7 | 161.61 ms | 57.2% | 3.13 ms | 0.01% | High |
| 🇺🇸 Los Angeles (LAX) | 284.3 | 163.35 ms | 57.5% | 2.19 ms | 0% | High |
| 🇸🇬 Singapore (SIN) | 310.5 | 84.85 ms | 27.3% | 1.81 ms | 0% | High |
| 🇭🇰 Hong Kong (HKG) | 316.9 | 104.93 ms | 33.1% | 2.55 ms | 0.05% | High |
| 🇹🇼 Taipei (TPE) | 330.9 | 112.87 ms | 34.1% | 2.55 ms | 0.13% | High |
| 🇧🇷 São Paulo (GRU) | 333.4 | 72.88 ms | 21.9% | 2.36 ms | 0.1% | High |
| 🇯🇵 Tokyo (TYO) | 360.5 | 132.57 ms | 36.8% | 3.64 ms | 0% | High |
| 🇦🇺 Melbourne (MEL) | 405 | 101.33 ms | 25% | 3.65 ms | 0.19% | High |
| 🇦🇺 Sydney (SYD) | 411.3 | 108.32 ms | 26.3% | 2.55 ms | 0.18% | High |
Frequently Asked 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 411.6 ms RTT.
Open Data
Measured latency data for Johannesburg (JNB) is published daily under CC BY 4.0 as part of the Hats Network open latency dataset:
- Per-route files — every directed route from Johannesburg is published as
jnb-<destination>.pings.{csv,json,yaml}under/opendata/latency/latest/pairs/— for example jnb-lon.pings.csv, the 50-probe ICMP echo round for Johannesburg (JNB) → London (LON). - Dataset documentation — /opendata/latency/ covers file formats, versioning, checksums, and the aggregated full-matrix releases.
Data auto-generated on August 10, 2026. Explore the full interactive latency matrix for side-by-side comparison across all 20 PoPs.
🇯🇵 Tokyo Ping & Network Latency (TYO) | AS203314
Tokyo (TYO) ping, RTT, jitter and packet loss, theoretical fiber floor, and route efficiency to 19 Hats Network (AS203314) backbone PoPs.
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.