# Berlin, Germany → Frankfurt, Germany RTT

🇩🇪 &#x2A;*Berlin, Germany (BER)** → 🇩🇪 &#x2A;*Frankfurt, Germany (FRA)**

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

The 2026-08-16T04:07:28Z measurement round captured 50 ICMP echo probes from Berlin, Germany to Frankfurt, Germany and returned an average round-trip time of 6.1 ms, with a minimum of 5.9 ms and a maximum of 6.73 ms. No packets were lost, and the 0.18 ms standard deviation with 0.15 ms jitter marked a highly consistent sample.

Relative to the 424.6 km geodesic distance, the measured average is 1.47 times the fiber floor of 4.16 ms, for a fiber efficiency of 68.2%. The 1.94 ms gap above the floor is more visible in proportional terms than the raw speed might imply, yet every reply stayed in the 5.9 ms to 6.73 ms range.

This route held the top rank in the 19-route measurement set for this network. Its spread-to-average ratio is about 3.0%, below the 3.28% median across the set, so the fastest measured route was also one of the steadier ones. The practical signal is that this corridor combined the best observed RTT with 0% loss and sub-0.2 ms jitter.

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **6.1 ms**                                     |
| Jitter               | **0.15 ms**                                    |
| Packet Loss          | **0%**                                         |
| Standard Fiber Floor | **4.16 ms**                                    |
| Fiber Efficiency     | **68.2%**                                      |
| Latency Tier         | Ultra-Low                                      |
| Source Region        | [Europe](/docs/network/latency/regions/europe) |
| 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 [Berlin](https://www.geonames.org/2950159) (52.52437, 13.41053) 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                      | **424.6 km** |
| Vacuum RTT floor                              | **2.83 ms**  |
| Standard fiber RTT floor ($n_g=1.4679$)       | **4.16 ms**  |
| Low-latency fiber material floor              | **4.14 ms**  |
| Engineering floor (5% path allowance)         | **4.37 ms**  |
| Research 1.33× mapped-fiber reference         | **5.53 ms**  |
| Estimated unamplified path loss               | **89.2 dB**  |
| Transparent optical spans / inline amplifiers | **6 / 5**    |
| Published RTT inflation over fiber floor      | **1.47×**    |

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        | **5.9 ms**  |
| Average RTT        | **6.1 ms**  |
| Maximum RTT        | **6.73 ms** |
| Standard deviation | **0.18 ms** |
| Stdev / average    | **3.0%**    |

## Route Context

* Departure PoP: [Berlin (BER)](/docs/network/latency/ber-berlin)
* Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [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 Berlin latency and RTT](/docs/network/latency/pairs/fra-ber-rtt) — 6.1 ms

**Fastest routes departing Berlin (BER)**

* [Berlin to Amsterdam latency and RTT](/docs/network/latency/pairs/ber-ams-rtt) — 7.2 ms
* [Berlin to London latency and RTT](/docs/network/latency/pairs/ber-lon-rtt) — 15.2 ms
* [Berlin to Paris latency and RTT](/docs/network/latency/pairs/ber-par-rtt) — 15.6 ms
* [Berlin to Marseille latency and RTT](/docs/network/latency/pairs/ber-mrs-rtt) — 20.2 ms
* [Berlin to Moscow latency and RTT](/docs/network/latency/pairs/ber-mow-rtt) — 28.6 ms

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

* [Amsterdam to Frankfurt latency and RTT](/docs/network/latency/pairs/ams-fra-rtt) — 5.9 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
* [Moscow to Frankfurt latency and RTT](/docs/network/latency/pairs/mow-fra-rtt) — 35.9 ms

**Same corridor (Europe → Europe)**

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