# Frankfurt, Germany → Miami, USA RTT

🇩🇪 **Frankfurt, Germany (FRA)** → 🇺🇸 **Miami, USA (MIA)**

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

In the 2026-08-16T04:07:28Z measurement round, ICMP echo probes from Frankfurt, Germany to Miami, USA averaged 112 ms over 50 samples at 100 ms intervals, with a narrow range of 110.01 ms to 117.35 ms and zero packet loss. The 7,777.9 km great-circle route has a vacuum floor of 51.89 ms and a straight-fiber floor of 76.17 ms, making the measured average 1.47 times the fiber floor with 68% fiber efficiency.

Variability is a standout feature: standard deviation is just 1.8 ms and jitter 1.53 ms, or about 1.6% of the average RTT. Among the 19 routes measured out of Frankfurt in this round, the median relative deviation was 3.28%, so this route is considerably steadier than the midpoint and earned its good latency tier.

As Miami hosts the NAP of the Americas and serves as the digital gateway between North and South America, a stable Frankfurt-to-Miami RTT is especially useful for baseline checks of traffic entering that hub. The zero packet loss and low jitter seen in this round make the route a dependable point of reference for the Latin American convergence corridor.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **112 ms**                                                   |
| Jitter               | **1.53 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **76.17 ms**                                                 |
| Fiber Efficiency     | **68%**                                                      |
| Latency Tier         | Good                                                         |
| Source Region        | [Europe](/docs/network/latency/regions/europe)               |
| Destination Region   | [North America](/docs/network/latency/regions/north-america) |

## 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 [Miami](https://www.geonames.org/4164138) (25.77427, -80.19366). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **7,777.9 km** |
| Vacuum RTT floor                              | **51.89 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **76.17 ms**   |
| Low-latency fiber material floor              | **75.86 ms**   |
| Engineering floor (5% path allowance)         | **79.99 ms**   |
| Research 1.33× mapped-fiber reference         | **101.3 ms**   |
| Estimated unamplified path loss               | **1633.4 dB**  |
| Transparent optical spans / inline amplifiers | **103 / 102**  |
| 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        | **110.01 ms** |
| Average RTT        | **112 ms**    |
| Maximum RTT        | **117.35 ms** |
| Standard deviation | **1.8 ms**    |
| Stdev / average    | **1.6%**      |

## Route Context

* Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* Destination PoP: [Miami (MIA)](/docs/network/latency/mia-miami)
* Region overview: [Europe](/docs/network/latency/regions/europe) → [North America](/docs/network/latency/regions/north-america)
* Corridor overview: [Europe to North America](/docs/network/latency/regions/europe-to-north-america)
* 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**

* [Miami to Frankfurt latency and RTT](/docs/network/latency/pairs/mia-fra-rtt) — 112.2 ms

**Fastest routes departing Frankfurt (FRA)**

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

**Fastest routes arriving at Miami (MIA)**

* [Ashburn to Miami latency and RTT](/docs/network/latency/pairs/iad-mia-rtt) — 27.4 ms
* [New York to Miami latency and RTT](/docs/network/latency/pairs/nyc-mia-rtt) — 32.9 ms
* [Los Angeles to Miami latency and RTT](/docs/network/latency/pairs/lax-mia-rtt) — 57.3 ms
* [São Paulo to Miami latency and RTT](/docs/network/latency/pairs/gru-mia-rtt) — 74 ms
* [Seattle to Miami latency and RTT](/docs/network/latency/pairs/sea-mia-rtt) — 81.7 ms

**Same corridor (Europe → North America)**

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