# Ashburn, USA → Berlin, Germany RTT

🇺🇸 &#x2A;*Ashburn, USA (IAD)** → 🇩🇪 &#x2A;*Berlin, Germany (BER)**

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

On 2026-08-16T04:07:28Z, ICMP echo probes from Ashburn, USA to Berlin, Germany returned an average RTT of 86.1 ms, with a minimum of 84.07 ms and a maximum of 94.45 ms over 50 samples. Packet loss was 0% and jitter was 1.6 ms, placing the route in the Good latency tier.

The physical reference for this 6,744.5 km path is a vacuum floor of 44.99 ms and a fiber floor of 66.05 ms. The observed average sits 1.30 times above the fiber floor, translating to 76.7% fiber efficiency — a solid outcome for the US-to-Germany distance and a clear step above the theoretical minimum.

Within the same set of 19 outbound routes, this path ranks 9th, putting it near the middle of the network's latency distribution. Its standard deviation of 2.05 ms is about 2.4% of the average, which is tighter than the network's median 3.28% variability, so the route's Good-tier timing is also consistent across the run.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **86.1 ms**                                                  |
| Jitter               | **1.6 ms**                                                   |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **66.05 ms**                                                 |
| Fiber Efficiency     | **76.7%**                                                    |
| Latency Tier         | Good                                                         |
| Source Region        | [North America](/docs/network/latency/regions/north-america) |
| 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 [Ashburn](https://www.geonames.org/4744870) (39.04372, -77.48749) 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                      | **6,744.5 km** |
| Vacuum RTT floor                              | **44.99 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **66.05 ms**   |
| Low-latency fiber material floor              | **65.78 ms**   |
| Engineering floor (5% path allowance)         | **69.36 ms**   |
| Research 1.33× mapped-fiber reference         | **87.84 ms**   |
| Estimated unamplified path loss               | **1416.4 dB**  |
| Transparent optical spans / inline amplifiers | **89 / 88**    |
| Published RTT inflation over fiber floor      | **1.3×**       |

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        | **84.07 ms** |
| Average RTT        | **86.1 ms**  |
| Maximum RTT        | **94.45 ms** |
| Standard deviation | **2.05 ms**  |
| Stdev / average    | **2.4%**     |

## Route Context

* Departure PoP: [Ashburn (IAD)](/docs/network/latency/iad-ashburn)
* Destination PoP: [Berlin (BER)](/docs/network/latency/ber-berlin)
* Region overview: [North America](/docs/network/latency/regions/north-america) → [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 Ashburn latency and RTT](/docs/network/latency/pairs/ber-iad-rtt) — 85.7 ms

**Fastest routes departing Ashburn (IAD)**

* [Ashburn to New York latency and RTT](/docs/network/latency/pairs/iad-nyc-rtt) — 6 ms
* [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms
* [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms
* [Ashburn to Seattle latency and RTT](/docs/network/latency/pairs/iad-sea-rtt) — 62.3 ms
* [Ashburn to London latency and RTT](/docs/network/latency/pairs/iad-lon-rtt) — 70.3 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 (North America → Europe)**

* [New York to London latency and RTT](/docs/network/latency/pairs/nyc-lon-rtt) — 63.5 ms
* [New York to Amsterdam latency and RTT](/docs/network/latency/pairs/nyc-ams-rtt) — 68.7 ms
* [New York to Paris latency and RTT](/docs/network/latency/pairs/nyc-par-rtt) — 68.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/iad-ber.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Ashburn → 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/iad-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.
