# 🇫🇷 Paris Ping & Network Latency (PAR) | AS203314

## 🇫🇷 Paris (PAR)

Paris is a major French interconnection market, providing direct access to France-IX Paris and NL-IX Paris alongside diverse national and European transit paths.

Measurement round: `2026-08-16T04:07:28Z`.

This page provides round-trip time (RTT) latency metrics between the &#x2A;*Paris (PAR)** PoP and every other node on the Hats Network (AS203314) global backbone.

### PoP Highlights

* **Location:** Paris, France (Europe)
* **Region:** Europe
* **Role:** Backbone interconnection point for Hats Network (AS203314)
* **Public city reference:** [GeoNames 2988507](https://www.geonames.org/2988507) — 48.85341, 2.34880
* **Coverage:** RTT measurements to 19 other PoPs across 5 continents

### Facility & Interconnection

* **Facility:** PAR1

> Interactive content is available on the canonical HTML page.

### Latency Summary

| Metric                | Value                                                                                                    |
| --------------------- | -------------------------------------------------------------------------------------------------------- |
| Fastest Route         | [🇫🇷 Paris (PAR) → 🇬🇧 London (LON)](/docs/network/latency/pairs/par-lon-rtt) (**6.4 ms**) — Ultra-Low |
| Slowest Route         | [🇫🇷 Paris (PAR) → 🇦🇺 Sydney (SYD)](/docs/network/latency/pairs/par-syd-rtt) (**249.7 ms**)           |
| Average RTT           | **112.9 ms**                                                                                             |
| Average Jitter        | **0.85 ms**                                                                                              |
| Average Packet Loss   | **0.05%**                                                                                                |
| Best Fiber Efficiency | **83.2%**                                                                                                |
| Intra-Region Peers    | 6 PoPs in Europe                                                                                         |
| 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

Paris sits on Hats Network's **Europe** backbone. Measured round-trip times to its 6 intra-region peers range from **6.4 ms** (London (LON)) to **44.7 ms** (Moscow (MOW)).

Paris is a major French interconnection market on the Northwest European corridor, with dense national and pan-European fiber paths.

## Outbound Latency from Paris (PAR)

Round-trip time in milliseconds **from Paris** to all other backbone PoPs, sorted fastest to slowest.

| Destination             | RTT (ms)                                             | Fiber Floor | Efficiency | Jitter  | Loss  | Tier      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇬🇧 London (LON)       | **[6.4](/docs/network/latency/pairs/par-lon-rtt)**   | 3.37 ms     | 52.7%      | 0.12 ms | 0%    | Ultra-Low |
| 🇳🇱 Amsterdam (AMS)    | **[7](/docs/network/latency/pairs/par-ams-rtt)**     | 4.22 ms     | 60.3%      | 0.12 ms | 0%    | Ultra-Low |
| 🇩🇪 Frankfurt (FRA)    | **[7.6](/docs/network/latency/pairs/par-fra-rtt)**   | 4.7 ms      | 61.8%      | 0.12 ms | 0.1%  | Ultra-Low |
| 🇫🇷 Marseille (MRS)    | **[8.9](/docs/network/latency/pairs/par-mrs-rtt)**   | 6.47 ms     | 72.7%      | 0.12 ms | 0%    | Ultra-Low |
| 🇩🇪 Berlin (BER)       | **[15.5](/docs/network/latency/pairs/par-ber-rtt)**  | 8.62 ms     | 55.6%      | 0.13 ms | 0%    | Ultra-Low |
| 🇷🇺 Moscow (MOW)       | **[44.7](/docs/network/latency/pairs/par-mow-rtt)**  | 24.42 ms    | 54.6%      | 0.23 ms | 0.2%  | Excellent |
| 🇺🇸 New York (NYC)     | **[68.9](/docs/network/latency/pairs/par-nyc-rtt)**  | 57.31 ms    | 83.2%      | 0.71 ms | 0.05% | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[75.5](/docs/network/latency/pairs/par-iad-rtt)**  | 60.73 ms    | 80.4%      | 0.86 ms | 0.02% | Excellent |
| 🇺🇸 Miami (MIA)        | **[106.8](/docs/network/latency/pairs/par-mia-rtt)** | 72.16 ms    | 67.6%      | 0.65 ms | 0.05% | Good      |
| 🇺🇸 Seattle (SEA)      | **[128](/docs/network/latency/pairs/par-sea-rtt)**   | 78.98 ms    | 61.7%      | 0.85 ms | 0.07% | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[136.5](/docs/network/latency/pairs/par-lax-rtt)** | 89.18 ms    | 65.3%      | 1.58 ms | 0.11% | Good      |
| 🇸🇬 Singapore (SIN)    | **[150.3](/docs/network/latency/pairs/par-sin-rtt)** | 105.19 ms   | 70%        | 1.32 ms | 0%    | Fair      |
| 🇭🇰 Hong Kong (HKG)    | **[160.1](/docs/network/latency/pairs/par-hkg-rtt)** | 94.48 ms    | 59%        | 1.29 ms | 0.05% | Fair      |
| 🇹🇼 Taipei (TPE)       | **[171.9](/docs/network/latency/pairs/par-tpe-rtt)** | 96.42 ms    | 56.1%      | 0.85 ms | 0%    | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[175.8](/docs/network/latency/pairs/par-gru-rtt)** | 91.83 ms    | 52.2%      | 1.26 ms | 0%    | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[180.9](/docs/network/latency/pairs/par-jnb-rtt)** | 85.17 ms    | 47.1%      | 0.94 ms | 0.17% | Fair      |
| 🇯🇵 Tokyo (TYO)        | **[204.7](/docs/network/latency/pairs/par-tyo-rtt)** | 95.34 ms    | 46.6%      | 2.17 ms | 0%    | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[246.4](/docs/network/latency/pairs/par-mel-rtt)** | 164.4 ms    | 66.7%      | 1.59 ms | 0.17% | Fair      |
| 🇦🇺 Sydney (SYD)       | **[249.7](/docs/network/latency/pairs/par-syd-rtt)** | 166.06 ms   | 66.5%      | 1.18 ms | 0%    | Fair      |

## Fastest Routes to Paris (PAR)

The 10 fastest measured routes **to Paris**, 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    | 🇬🇧 London (LON)    | **[6.4 ms](/docs/network/latency/pairs/lon-par-rtt)**   | 6.23 ms   | 6.9 ms    | 0.15 ms |
| 2    | 🇳🇱 Amsterdam (AMS) | **[7 ms](/docs/network/latency/pairs/ams-par-rtt)**     | 6.61 ms   | 8.02 ms   | 0.32 ms |
| 3    | 🇩🇪 Frankfurt (FRA) | **[7.6 ms](/docs/network/latency/pairs/fra-par-rtt)**   | 7.34 ms   | 8.24 ms   | 0.23 ms |
| 4    | 🇫🇷 Marseille (MRS) | **[8.9 ms](/docs/network/latency/pairs/mrs-par-rtt)**   | 8.72 ms   | 9.67 ms   | 0.16 ms |
| 5    | 🇩🇪 Berlin (BER)    | **[15.6 ms](/docs/network/latency/pairs/ber-par-rtt)**  | 14.9 ms   | 17.81 ms  | 0.63 ms |
| 6    | 🇷🇺 Moscow (MOW)    | **[44 ms](/docs/network/latency/pairs/mow-par-rtt)**    | 42.02 ms  | 49.11 ms  | 1.64 ms |
| 7    | 🇺🇸 New York (NYC)  | **[68.9 ms](/docs/network/latency/pairs/nyc-par-rtt)**  | 67.48 ms  | 73.26 ms  | 1.31 ms |
| 8    | 🇺🇸 Ashburn (IAD)   | **[76.1 ms](/docs/network/latency/pairs/iad-par-rtt)**  | 74.36 ms  | 85 ms     | 1.76 ms |
| 9    | 🇺🇸 Miami (MIA)     | **[106.2 ms](/docs/network/latency/pairs/mia-par-rtt)** | 104.35 ms | 111.43 ms | 1.69 ms |
| 10   | 🇺🇸 Seattle (SEA)   | **[129.2 ms](/docs/network/latency/pairs/sea-par-rtt)** | 126.7 ms  | 135.02 ms | 2.13 ms |

## Inbound Latency to Paris (PAR)

Round-trip time in milliseconds **from all other PoPs to Paris**. 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      |
| ----------------------- | ---------------------------------------------------- | ----------- | ---------- | ------- | ----- | --------- |
| 🇬🇧 London (LON)       | **[6.4](/docs/network/latency/pairs/lon-par-rtt)**   | 3.37 ms     | 52.7%      | 0.12 ms | 0%    | Ultra-Low |
| 🇳🇱 Amsterdam (AMS)    | **[7](/docs/network/latency/pairs/ams-par-rtt)**     | 4.22 ms     | 60.3%      | 0.12 ms | 0.03% | Ultra-Low |
| 🇩🇪 Frankfurt (FRA)    | **[7.6](/docs/network/latency/pairs/fra-par-rtt)**   | 4.7 ms      | 61.8%      | 0.12 ms | 0%    | Ultra-Low |
| 🇫🇷 Marseille (MRS)    | **[8.9](/docs/network/latency/pairs/mrs-par-rtt)**   | 6.47 ms     | 72.7%      | 0.12 ms | 0%    | Ultra-Low |
| 🇩🇪 Berlin (BER)       | **[15.6](/docs/network/latency/pairs/ber-par-rtt)**  | 8.62 ms     | 55.3%      | 0.16 ms | 0%    | Ultra-Low |
| 🇷🇺 Moscow (MOW)       | **[44](/docs/network/latency/pairs/mow-par-rtt)**    | 24.42 ms    | 55.5%      | 0.29 ms | 0%    | Excellent |
| 🇺🇸 New York (NYC)     | **[68.9](/docs/network/latency/pairs/nyc-par-rtt)**  | 57.31 ms    | 83.2%      | 0.43 ms | 0.15% | Excellent |
| 🇺🇸 Ashburn (IAD)      | **[76.1](/docs/network/latency/pairs/iad-par-rtt)**  | 60.73 ms    | 79.8%      | 0.7 ms  | 0.03% | Excellent |
| 🇺🇸 Miami (MIA)        | **[106.2](/docs/network/latency/pairs/mia-par-rtt)** | 72.16 ms    | 67.9%      | 1.07 ms | 0%    | Good      |
| 🇺🇸 Seattle (SEA)      | **[129.2](/docs/network/latency/pairs/sea-par-rtt)** | 78.98 ms    | 61.1%      | 1.22 ms | 0.02% | Good      |
| 🇺🇸 Los Angeles (LAX)  | **[135.9](/docs/network/latency/pairs/lax-par-rtt)** | 89.18 ms    | 65.6%      | 0.62 ms | 0%    | Good      |
| 🇸🇬 Singapore (SIN)    | **[151.4](/docs/network/latency/pairs/sin-par-rtt)** | 105.19 ms   | 69.5%      | 1.07 ms | 0.12% | Fair      |
| 🇭🇰 Hong Kong (HKG)    | **[159.4](/docs/network/latency/pairs/hkg-par-rtt)** | 94.48 ms    | 59.3%      | 1.21 ms | 0.07% | Fair      |
| 🇿🇦 Johannesburg (JNB) | **[164.4](/docs/network/latency/pairs/jnb-par-rtt)** | 85.17 ms    | 51.8%      | 1.05 ms | 0%    | Fair      |
| 🇹🇼 Taipei (TPE)       | **[173.8](/docs/network/latency/pairs/tpe-par-rtt)** | 96.42 ms    | 55.5%      | 1.13 ms | 0.13% | Fair      |
| 🇧🇷 São Paulo (GRU)    | **[180.2](/docs/network/latency/pairs/gru-par-rtt)** | 91.83 ms    | 51%        | 1.95 ms | 0.14% | Fair      |
| 🇯🇵 Tokyo (TYO)        | **[204.8](/docs/network/latency/pairs/tyo-par-rtt)** | 95.34 ms    | 46.6%      | 2.06 ms | 0.03% | Fair      |
| 🇦🇺 Melbourne (MEL)    | **[246.5](/docs/network/latency/pairs/mel-par-rtt)** | 164.4 ms    | 66.7%      | 1.53 ms | 0.13% | Fair      |
| 🇦🇺 Sydney (SYD)       | **[250.3](/docs/network/latency/pairs/syd-par-rtt)** | 166.06 ms   | 66.3%      | 2.41 ms | 0%    | High      |

## Europe Peers

Paris is one of 7 Hats Network PoPs in **Europe**. Intra-region routes offer the lowest latency and highest path diversity.

| PoP                                     | Code | Country     | RTT (ms) | Tier      |
| --------------------------------------- | ---- | ----------- | -------- | --------- |
| [🇳🇱 Amsterdam (AMS)](./ams-amsterdam) | AMS  | Netherlands | **7**    | Ultra-Low |
| [🇩🇪 Berlin (BER)](./ber-berlin)       | BER  | Germany     | **15.5** | Ultra-Low |
| [🇩🇪 Frankfurt (FRA)](./fra-frankfurt) | FRA  | Germany     | **7.6**  | Ultra-Low |
| [🇬🇧 London (LON)](./lon-london)       | LON  | UK          | **6.4**  | Ultra-Low |
| [🇫🇷 Marseille (MRS)](./mrs-marseille) | MRS  | France      | **8.9**  | Ultra-Low |
| [🇷🇺 Moscow (MOW)](./mow-moscow)       | MOW  | Russia      | **44.7** | Excellent |

## Frequently Asked Questions

**What is the fastest route to Paris?**

The fastest measured route to Paris (PAR) is [London (LON) → Paris (PAR)](/docs/network/latency/pairs/lon-par-rtt), averaging **6.4 ms** RTT (Ultra-Low).

**What is the fastest route from Paris?**

The fastest measured route from Paris (PAR) is [Paris (PAR) → London (LON)](/docs/network/latency/pairs/par-lon-rtt), averaging **6.4 ms** RTT (Ultra-Low).

**How well connected is Paris to the Hats Network backbone?**

Paris (PAR) maintains measured routes to all 19 other PoPs across 5 continents. The slowest route, [Paris (PAR) → Sydney (SYD)](/docs/network/latency/pairs/par-syd-rtt), averages **249.7 ms** RTT.

## Open Data

Measured latency data for Paris (PAR) 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 Paris is published as `par-<destination>.pings.{csv,json,yaml}` under [`/opendata/latency/latest/pairs/`](/opendata/latency/latest/pairs/) — for example [par-lon.pings.csv](/opendata/latency/latest/pairs/par-lon.pings.csv), the 50-probe ICMP echo round for [Paris (PAR) → London (LON)](/docs/network/latency/pairs/par-lon-rtt).
* **Dataset documentation** — [/opendata/latency/](/opendata/latency/) covers file formats, versioning, checksums, and the aggregated full-matrix releases.

***

*Data auto-generated on August 16, 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/par-paris).
- **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.
