# Frankfurt, Germany → Berlin, Germany RTT

🇩🇪 **Frankfurt, Germany (FRA)** → 🇩🇪 **Berlin, Germany (BER)**

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

ICMP echo RTT measurements from Frankfurt to Berlin in round 2026-08-16T04:07:28Z averaged 6.1 ms across 50 samples, with a minimum of 5.91 ms, a maximum of 6.79 ms, and 0% packet loss.

The 424.6 km geodesic path has a vacuum floor of 2.83 ms and a fiber floor of 4.16 ms; the measured RTT is 1.47 times that fiber floor, which translates to 68.2% fiber efficiency. This domestic route is already operating close to the optical limit for the straight-line distance, leaving only limited headroom.

Within a route set of 19 measured paths, this route ranked second, and the corresponding network median variability was 3.28% of average RTT. Frankfurt–Berlin recorded a standard deviation of 0.18 ms and jitter of 0.16 ms, or about 2.9% of the mean, so its stability is tighter than the network median.

## Latency Summary

| Metric               | Value                                          |
| -------------------- | ---------------------------------------------- |
| RTT                  | **6.1 ms**                                     |
| Jitter               | **0.16 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 [Frankfurt am Main](https://www.geonames.org/2925533) (50.11552, 8.68417) 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                      | **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.91 ms** |
| Average RTT        | **6.1 ms**  |
| Maximum RTT        | **6.79 ms** |
| Standard deviation | **0.18 ms** |
| Stdev / average    | **3.0%**    |

## Route Context

* Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin)
* 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**

* [Berlin to Frankfurt latency and RTT](/docs/network/latency/pairs/ber-fra-rtt) — 6.1 ms

**Fastest routes departing Frankfurt (FRA)**

* [Frankfurt to Amsterdam latency and RTT](/docs/network/latency/pairs/fra-ams-rtt) — 5.9 ms
* [Frankfurt to Paris latency and RTT](/docs/network/latency/pairs/fra-par-rtt) — 7.6 ms
* [Frankfurt to London latency and RTT](/docs/network/latency/pairs/fra-lon-rtt) — 12.9 ms
* [Frankfurt to Marseille latency and RTT](/docs/network/latency/pairs/fra-mrs-rtt) — 16.4 ms
* [Frankfurt to Moscow latency and RTT](/docs/network/latency/pairs/fra-mow-rtt) — 34.7 ms

**Fastest routes arriving at Berlin (BER)**

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