# Tokyo, Japan → Frankfurt, Germany RTT

🇯🇵 **Tokyo, Japan (TYO)** → 🇩🇪 **Frankfurt, Germany (FRA)**

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

In the 2026-08-16T04:07:28Z measurement round, Tokyo-to-Frankfurt ICMP echo RTT averaged 193.2 ms, with replies between 189.92 ms and 203.54 ms and no packet loss across all 50 probes. The moderate latency rating is consistent with an observed delay about 2.11 times the fiber-path lower bound for the 9,354.4 km route.

Within the 19-route outbound set, this connection is 13th by average latency. However, its RTT variability is only about 1.7% of the average, well below the 3.28% median variability seen across the outbound routes, so the route is notably steady for its latency tier.

The entire sample fit within a 13.62 ms range, and jitter was just 2.63 ms, indicating very consistent forwarding behavior during the window. For traffic landing in Frankfurt, a central switching point on the European fiber ring, this Tokyo route offers a reliable delay profile even though the absolute RTT remains in moderate territory.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **193.2 ms**                                               |
| Jitter               | **2.63 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **91.61 ms**                                               |
| Fiber Efficiency     | **47.4%**                                                  |
| Latency Tier         | Fair                                                       |
| Source Region        | [Asia Pacific](/docs/network/latency/regions/asia-pacific) |
| Destination Region   | [Europe](/docs/network/latency/regions/europe)             |

## Ping Measurement Series

The chart below renders the 50-sample ICMP echo measurement round for this route; an accessible table of every sample is included with the chart.

## Download This Route's Data

This route's measurement round is published as open data (CC BY 4.0) in CSV, JSON, and YAML. See [About This Measurement](#about-this-measurement) for citation guidance.

## Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for [Tokyo](https://www.geonames.org/1850147) (35.68950, 139.69171) and [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **9,354.4 km** |
| Vacuum RTT floor                              | **62.41 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **91.61 ms**   |
| Low-latency fiber material floor              | **91.24 ms**   |
| Engineering floor (5% path allowance)         | **96.2 ms**    |
| Research 1.33× mapped-fiber reference         | **121.84 ms**  |
| Estimated unamplified path loss               | **1964.4 dB**  |
| Transparent optical spans / inline amplifiers | **123 / 122**  |
| Published RTT inflation over fiber floor      | **2.11×**      |

Attenuation is used to estimate the number of 80 km optical spans; it does not directly slow light. See the full [theoretical fiber latency, GeoNames, attenuation, and amplifier methodology](/docs/network/latency/theoretical-fiber-latency).

## Stability & Trend

The current measurement round (2026-08-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

| Round Statistic    | Value         |
| ------------------ | ------------- |
| Minimum RTT        | **189.92 ms** |
| Average RTT        | **193.2 ms**  |
| Maximum RTT        | **203.54 ms** |
| Standard deviation | **3.37 ms**   |
| Stdev / average    | **1.7%**      |

## Route Context

* Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo)
* Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* Region overview: [Asia Pacific](/docs/network/latency/regions/asia-pacific) → [Europe](/docs/network/latency/regions/europe)
* Full global matrix: [Backbone Latency Matrix](/docs/network/latency)
* Physical methodology: [Theoretical Fiber Latency](/docs/network/latency/theoretical-fiber-latency)

## Related City-Pair Routes

**Reverse direction**

* [Frankfurt to Tokyo latency and RTT](/docs/network/latency/pairs/fra-tyo-rtt) — 194.5 ms

**Fastest routes departing Tokyo (TYO)**

* [Tokyo to Taipei latency and RTT](/docs/network/latency/pairs/tyo-tpe-rtt) — 32.3 ms
* [Tokyo to Hong Kong latency and RTT](/docs/network/latency/pairs/tyo-hkg-rtt) — 44.8 ms
* [Tokyo to Singapore latency and RTT](/docs/network/latency/pairs/tyo-sin-rtt) — 69.4 ms
* [Tokyo to Seattle latency and RTT](/docs/network/latency/pairs/tyo-sea-rtt) — 84.8 ms
* [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 ms

**Fastest routes arriving at Frankfurt (FRA)**

* [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 ms
* [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms
* [Paris to Frankfurt latency and RTT](/docs/network/latency/pairs/par-fra-rtt) — 7.6 ms
* [London to Frankfurt latency and RTT](/docs/network/latency/pairs/lon-fra-rtt) — 13.6 ms
* [Marseille to Frankfurt latency and RTT](/docs/network/latency/pairs/mrs-fra-rtt) — 16 ms

**Same corridor (Asia Pacific → Europe)**

* [Hong Kong to Moscow latency and RTT](/docs/network/latency/pairs/hkg-mow-rtt) — 118.2 ms
* [Taipei to Moscow latency and RTT](/docs/network/latency/pairs/tpe-mow-rtt) — 132.7 ms
* [Singapore to Marseille latency and RTT](/docs/network/latency/pairs/sin-mrs-rtt) — 140.6 ms

## About This Measurement

Published RTT reflects best-case backbone path behavior measured with ICMP echo probes between PoPs. End-user latency also depends on local access networks, congestion, routing policy, and traffic engineering. None of these values is an SLA.

The measurement round behind this page is published as open data under **CC BY 4.0** in the [Hats Network latency dataset](/opendata/latency/). Per-pair files are available at `/opendata/latency/latest/pairs/tyo-fra.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Frankfurt round 2026-08-16T04:07:28Z, CC BY 4.0".

***

*Data auto-generated on August 16, 2026. Explore the [full interactive latency matrix](/docs/network/latency) or browse more [city-pair routes](/docs/network/latency/pairs).*

---

## License and attribution

- **Canonical source:** [View the human-readable HTML page](https://hatsnet.io/docs/network/latency/pairs/tyo-fra-rtt).
- **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.