# Tokyo, Japan → Berlin, Germany RTT

🇯🇵 **Tokyo, Japan (TYO)** → 🇩🇪 **Berlin, Germany (BER)**

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

ICMP echo RTT between Tokyo and Berlin in the 2026-08-16T04:07:28Z round averaged 186.1 ms, with a minimum of 174.48 ms and a maximum of 227.17 ms. The measurement carried no packet loss across 50 probes, and the moderate latency rating reflects an average that is 2.13 times the approximate fiber-path lower bound for the 8,937.7 km between the two cities.

Within the 19-route outbound set, this pair ranks 12th. Its RTT variability equals about 4.9% of the average, noticeably above the 3.28% median variability for the outbound set, meaning this crossing is less stable in relative terms than its average latency alone suggests.

The 52.69 ms difference between fastest and slowest replies, plus jitter of 7.88 ms, shows the path's delay profile shifted significantly during the sample window even though no probes were lost. Berlin's position as a bridge on the east-west European corridor makes it an important arrival point, and the Tokyo-to-Berlin leg should be treated as more variable than its 186.1 ms average implies.

## Latency Summary

| Metric               | Value                                                      |
| -------------------- | ---------------------------------------------------------- |
| RTT                  | **186.1 ms**                                               |
| Jitter               | **7.88 ms**                                                |
| Packet Loss          | **0%**                                                     |
| Standard Fiber Floor | **87.53 ms**                                               |
| Fiber Efficiency     | **47%**                                                    |
| 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 [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **8,937.7 km** |
| Vacuum RTT floor                              | **59.63 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **87.53 ms**   |
| Low-latency fiber material floor              | **87.17 ms**   |
| Engineering floor (5% path allowance)         | **91.91 ms**   |
| Research 1.33× mapped-fiber reference         | **116.41 ms**  |
| Estimated unamplified path loss               | **1876.9 dB**  |
| Transparent optical spans / inline amplifiers | **118 / 117**  |
| Published RTT inflation over fiber floor      | **2.13×**      |

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        | **174.48 ms** |
| Average RTT        | **186.1 ms**  |
| Maximum RTT        | **227.17 ms** |
| Standard deviation | **9.12 ms**   |
| Stdev / average    | **4.9%**      |

## Route Context

* Departure PoP: [Tokyo (TYO)](/docs/network/latency/tyo-tokyo)
* Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin)
* 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**

* [Berlin to Tokyo latency and RTT](/docs/network/latency/pairs/ber-tyo-rtt) — 187.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 Berlin (BER)**

* [Frankfurt to Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms
* [Amsterdam to Berlin latency and RTT](/docs/network/latency/pairs/ams-ber-rtt) — 7.2 ms
* [Paris to Berlin latency and RTT](/docs/network/latency/pairs/par-ber-rtt) — 15.5 ms
* [London to Berlin latency and RTT](/docs/network/latency/pairs/lon-ber-rtt) — 16.2 ms
* [Marseille to Berlin latency and RTT](/docs/network/latency/pairs/mrs-ber-rtt) — 20.6 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-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Tokyo → Berlin 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-ber-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.