# New York, USA → Frankfurt, Germany RTT

🇺🇸 **New York, USA (NYC)** → 🇩🇪 **Frankfurt, Germany (FRA)**

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

The 2026-08-16T04:07:28Z round from New York to Frankfurt returned a 73.9 ms average ICMP echo RTT, with 0.0% packet loss across 50 samples. The minimum of 71.94 ms and maximum of 81.47 ms produce a 1.98 ms standard deviation and 1.42 ms jitter, so the delay spread was narrow.

Relative to the 60.9 ms fiber-floor estimate for a 6,219 km crossing, the measured average is 21% higher, putting fiber efficiency at 82.4%. The route ranked 8th among 19 outbound routes from New York in this round, and its variability is comfortably below the 3.28% median relative variability for that outbound group.

The absence of loss combined with a sub-2 ms standard deviation points to a stable path at the time of measurement. The 73.9 ms figure is a useful ICMP latency baseline for this route, not a predictor of end-user application performance.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **73.9 ms**                                                  |
| Jitter               | **1.42 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **60.9 ms**                                                  |
| Fiber Efficiency     | **82.4%**                                                    |
| Latency Tier         | Excellent                                                    |
| 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 [New York City](https://www.geonames.org/5128581) (40.71427, -74.00597) 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                      | **6,219.3 km** |
| Vacuum RTT floor                              | **41.49 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **60.9 ms**    |
| Low-latency fiber material floor              | **60.66 ms**   |
| Engineering floor (5% path allowance)         | **63.96 ms**   |
| Research 1.33× mapped-fiber reference         | **81 ms**      |
| Estimated unamplified path loss               | **1306 dB**    |
| Transparent optical spans / inline amplifiers | **82 / 81**    |
| Published RTT inflation over fiber floor      | **1.21×**      |

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        | **71.94 ms** |
| Average RTT        | **73.9 ms**  |
| Maximum RTT        | **81.47 ms** |
| Standard deviation | **1.98 ms**  |
| Stdev / average    | **2.7%**     |

## Route Context

* Departure PoP: [New York (NYC)](/docs/network/latency/nyc-new-york)
* Destination PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* 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**

* [Frankfurt to New York latency and RTT](/docs/network/latency/pairs/fra-nyc-rtt) — 74.4 ms

**Fastest routes departing New York (NYC)**

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

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