# 🇿🇦 Johannesburg Ping & Network Latency (JNB) | AS203314

## 🇿🇦 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.

### PoP Highlights

* **Location:** Johannesburg, South Africa (Africa)
* **Region:** Africa
* **Role:** Backbone interconnection point for Hats Network (AS203314)
* **Public city reference:** [GeoNames 993800](https://www.geonames.org/993800) — -26.20227, 28.04363
* **Coverage:** RTT measurements to 19 other PoPs across 4 continents

### Facility & Interconnection

* **Facility:** JNB1
* **Upstream transit:** HE Only

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                      |
| --------------------- | ---------------------------------------------------------------------------------------------------------- |
| Fastest Route         | [🇿🇦 Johannesburg (JNB) → 🇬🇧 London (LON)](/docs/network/latency/pairs/jnb-lon-rtt) (**158 ms**) — Fair |
| Slowest Route         | [🇿🇦 Johannesburg (JNB) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/jnb-syd-rtt) (**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](/docs/network/latency/theoretical-fiber-latency).

## 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](/docs/network/latency/pairs/jnb-lon-rtt)**   | 88.52 ms    | 56%        | 1.52 ms | 0%    | Fair |
| 🇳🇱 Amsterdam (AMS)   | **[163.2](/docs/network/latency/pairs/jnb-ams-rtt)** | 88.05 ms    | 54%        | 1.79 ms | 0.04% | Fair |
| 🇫🇷 Paris (PAR)       | **[164.4](/docs/network/latency/pairs/jnb-par-rtt)** | 85.17 ms    | 51.8%      | 1.71 ms | 0.11% | Fair |
| 🇩🇪 Frankfurt (FRA)   | **[166](/docs/network/latency/pairs/jnb-fra-rtt)**   | 84.87 ms    | 51.1%      | 1.52 ms | 0%    | Fair |
| 🇫🇷 Marseille (MRS)   | **[172](/docs/network/latency/pairs/jnb-mrs-rtt)**   | 78.71 ms    | 45.8%      | 1.45 ms | 0.09% | Fair |
| 🇩🇪 Berlin (BER)      | **[172.1](/docs/network/latency/pairs/jnb-ber-rtt)** | 86.53 ms    | 50.3%      | 0.9 ms  | 0%    | Fair |
| 🇷🇺 Moscow (MOW)      | **[201.7](/docs/network/latency/pairs/jnb-mow-rtt)** | 89.37 ms    | 44.3%      | 2.04 ms | 0.12% | Fair |
| 🇺🇸 New York (NYC)    | **[221.6](/docs/network/latency/pairs/jnb-nyc-rtt)** | 125.67 ms   | 56.7%      | 2.28 ms | 0.08% | Fair |
| 🇺🇸 Ashburn (IAD)     | **[228.5](/docs/network/latency/pairs/jnb-iad-rtt)** | 128.11 ms   | 56.1%      | 2.02 ms | 0%    | Fair |
| 🇺🇸 Miami (MIA)       | **[259.3](/docs/network/latency/pairs/jnb-mia-rtt)** | 126.78 ms   | 48.9%      | 1.77 ms | 0.16% | High |
| 🇺🇸 Seattle (SEA)     | **[280.3](/docs/network/latency/pairs/jnb-sea-rtt)** | 161.61 ms   | 57.7%      | 3.03 ms | 0.1%  | High |
| 🇺🇸 Los Angeles (LAX) | **[284.4](/docs/network/latency/pairs/jnb-lax-rtt)** | 163.35 ms   | 57.4%      | 3.35 ms | 0.08% | High |
| 🇸🇬 Singapore (SIN)   | **[309.5](/docs/network/latency/pairs/jnb-sin-rtt)** | 84.85 ms    | 27.4%      | 2.85 ms | 0.12% | High |
| 🇭🇰 Hong Kong (HKG)   | **[318.4](/docs/network/latency/pairs/jnb-hkg-rtt)** | 104.93 ms   | 33%        | 1.96 ms | 0.08% | High |
| 🇧🇷 São Paulo (GRU)   | **[329.7](/docs/network/latency/pairs/jnb-gru-rtt)** | 72.88 ms    | 22.1%      | 1.83 ms | 0%    | High |
| 🇹🇼 Taipei (TPE)      | **[333](/docs/network/latency/pairs/jnb-tpe-rtt)**   | 112.87 ms   | 33.9%      | 2.19 ms | 0.17% | High |
| 🇯🇵 Tokyo (TYO)       | **[362.7](/docs/network/latency/pairs/jnb-tyo-rtt)** | 132.57 ms   | 36.6%      | 3.8 ms  | 0%    | High |
| 🇦🇺 Melbourne (MEL)   | **[405.8](/docs/network/latency/pairs/jnb-mel-rtt)** | 101.33 ms   | 25%        | 3.4 ms  | 0%    | High |
| 🇦🇺 Sydney (SYD)      | **[411.6](/docs/network/latency/pairs/jnb-syd-rtt)** | 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](/docs/network/latency/pairs/ams-jnb-rtt)** | 161.36 ms | 195.12 ms | 7.13 ms |
| 2    | 🇩🇪 Berlin (BER)    | **[172.1 ms](/docs/network/latency/pairs/ber-jnb-rtt)** | 168.43 ms | 190.03 ms | 3.66 ms |
| 3    | 🇬🇧 London (LON)    | **[179.8 ms](/docs/network/latency/pairs/lon-jnb-rtt)** | 168.72 ms | 213.58 ms | 8.97 ms |
| 4    | 🇫🇷 Paris (PAR)     | **[180.9 ms](/docs/network/latency/pairs/par-jnb-rtt)** | 175.49 ms | 194.96 ms | 4.67 ms |
| 5    | 🇩🇪 Frankfurt (FRA) | **[188.9 ms](/docs/network/latency/pairs/fra-jnb-rtt)** | 177.16 ms | 223.52 ms | 8.45 ms |
| 6    | 🇫🇷 Marseille (MRS) | **[198.9 ms](/docs/network/latency/pairs/mrs-jnb-rtt)** | 191.78 ms | 215.05 ms | 5.46 ms |
| 7    | 🇷🇺 Moscow (MOW)    | **[201.1 ms](/docs/network/latency/pairs/mow-jnb-rtt)** | 196.79 ms | 210 ms    | 3.15 ms |
| 8    | 🇺🇸 New York (NYC)  | **[221.8 ms](/docs/network/latency/pairs/nyc-jnb-rtt)** | 212.01 ms | 253.24 ms | 8.25 ms |
| 9    | 🇺🇸 Ashburn (IAD)   | **[228.3 ms](/docs/network/latency/pairs/iad-jnb-rtt)** | 223.49 ms | 249.1 ms  | 4.95 ms |
| 10   | 🇺🇸 Miami (MIA)     | **[259.4 ms](/docs/network/latency/pairs/mia-jnb-rtt)** | 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](/docs/network/latency/pairs/ams-jnb-rtt)** | 88.05 ms    | 51.2%      | 1.6 ms  | 0.15% | Fair |
| 🇩🇪 Berlin (BER)      | **[172.1](/docs/network/latency/pairs/ber-jnb-rtt)** | 86.53 ms    | 50.3%      | 0.82 ms | 0.06% | Fair |
| 🇬🇧 London (LON)      | **[179.8](/docs/network/latency/pairs/lon-jnb-rtt)** | 88.52 ms    | 49.2%      | 2.06 ms | 0%    | Fair |
| 🇫🇷 Paris (PAR)       | **[180.9](/docs/network/latency/pairs/par-jnb-rtt)** | 85.17 ms    | 47.1%      | 0.93 ms | 0.07% | Fair |
| 🇩🇪 Frankfurt (FRA)   | **[188.9](/docs/network/latency/pairs/fra-jnb-rtt)** | 84.87 ms    | 44.9%      | 2.11 ms | 0%    | Fair |
| 🇫🇷 Marseille (MRS)   | **[198.9](/docs/network/latency/pairs/mrs-jnb-rtt)** | 78.71 ms    | 39.6%      | 1.65 ms | 0.16% | Fair |
| 🇷🇺 Moscow (MOW)      | **[201.1](/docs/network/latency/pairs/mow-jnb-rtt)** | 89.37 ms    | 44.4%      | 2.38 ms | 0%    | Fair |
| 🇺🇸 New York (NYC)    | **[221.8](/docs/network/latency/pairs/nyc-jnb-rtt)** | 125.67 ms   | 56.7%      | 2.56 ms | 0.01% | Fair |
| 🇺🇸 Ashburn (IAD)     | **[228.3](/docs/network/latency/pairs/iad-jnb-rtt)** | 128.11 ms   | 56.1%      | 2.29 ms | 0.08% | Fair |
| 🇺🇸 Miami (MIA)       | **[259.4](/docs/network/latency/pairs/mia-jnb-rtt)** | 126.78 ms   | 48.9%      | 1.78 ms | 0.07% | High |
| 🇺🇸 Seattle (SEA)     | **[282.7](/docs/network/latency/pairs/sea-jnb-rtt)** | 161.61 ms   | 57.2%      | 3.13 ms | 0.01% | High |
| 🇺🇸 Los Angeles (LAX) | **[284.3](/docs/network/latency/pairs/lax-jnb-rtt)** | 163.35 ms   | 57.5%      | 2.19 ms | 0%    | High |
| 🇸🇬 Singapore (SIN)   | **[310.5](/docs/network/latency/pairs/sin-jnb-rtt)** | 84.85 ms    | 27.3%      | 1.81 ms | 0%    | High |
| 🇭🇰 Hong Kong (HKG)   | **[316.9](/docs/network/latency/pairs/hkg-jnb-rtt)** | 104.93 ms   | 33.1%      | 2.55 ms | 0.05% | High |
| 🇹🇼 Taipei (TPE)      | **[330.9](/docs/network/latency/pairs/tpe-jnb-rtt)** | 112.87 ms   | 34.1%      | 2.55 ms | 0.13% | High |
| 🇧🇷 São Paulo (GRU)   | **[333.4](/docs/network/latency/pairs/gru-jnb-rtt)** | 72.88 ms    | 21.9%      | 2.36 ms | 0.1%  | High |
| 🇯🇵 Tokyo (TYO)       | **[360.5](/docs/network/latency/pairs/tyo-jnb-rtt)** | 132.57 ms   | 36.8%      | 3.64 ms | 0%    | High |
| 🇦🇺 Melbourne (MEL)   | **[405](/docs/network/latency/pairs/mel-jnb-rtt)**   | 101.33 ms   | 25%        | 3.65 ms | 0.19% | High |
| 🇦🇺 Sydney (SYD)      | **[411.3](/docs/network/latency/pairs/syd-jnb-rtt)** | 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)](/docs/network/latency/pairs/ams-jnb-rtt), 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)](/docs/network/latency/pairs/jnb-lon-rtt), 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)](/docs/network/latency/pairs/jnb-syd-rtt), averages **411.6 ms** RTT.

## Open Data

Measured latency data for Johannesburg (JNB) is published daily under [CC BY 4.0](https://creativecommons.org/licenses/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/`](/opendata/latency/latest/pairs/) — for example [jnb-lon.pings.csv](/opendata/latency/latest/pairs/jnb-lon.pings.csv), the 50-probe ICMP echo round for [Johannesburg (JNB) → London (LON)](/docs/network/latency/pairs/jnb-lon-rtt).
* **Dataset documentation** — [/opendata/latency/](/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](/docs/network/latency) for side-by-side comparison across all 20 PoPs.*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/jnb-johannesburg).
- **Original documentation:** © Hats Network Inc., licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
- **Public latency data:** © Hats Network Inc., licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
- **Full terms:** [Content and Data License](https://hatsnet.io/docs/legal/content-and-data-license) — includes attribution requirements, third-party material, trademarks, source code and other exclusions.