Miami, USA to Frankfurt, Germany ICMP RTT data: average latency, jitter, packet loss, and fiber efficiency for this transatlantic route.

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

Measurement round: 2026-08-15T04:03:13Z.

During the 2026-08-15T04:03:13Z round, Miami, USA to Frankfurt, Germany averaged 114.5 ms ICMP RTT, with a minimum of 109.56 ms, a maximum of 128.89 ms, and no packet loss. A 3.45 ms jitter and 4.25 ms standard deviation show normal transatlantic drift rather than a congested path.

Among the 19 Miami-origin routes in this round, Frankfurt ranks 9th by average round-trip time. Its mean-relative variation is about 3.7%, slightly above the 3.08% median variation across the set, so the route is competitive in central ordering though a bit more dispersed than the typical peer.

With a geodesic distance of 7,777.9 km, the route's fiber floor is 76.17 ms and its line-of-sight minimum is 51.89 ms. The measured average of 114.5 ms is 1.5 times the fiber floor, putting efficiency at 66.5%; connecting Miami's gateway position to Frankfurt's central switching point, the round returned zero loss and a stable result worth using as a reference for Frankfurt-bound connectivity.

Latency Summary

Metric	Value
RTT	114.5 ms
Jitter	3.45 ms
Packet Loss	0%
Standard Fiber Floor	76.17 ms
Fiber Efficiency	66.5%
Latency Tier	Good
Source Region	North America
Destination Region	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.

Ping series: MIA → FRA

50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 114.5 ± 0.60 ms (SE)

Sample distribution: box = interquartile range (111.2–115.6 ms), median 113.5 ms · whiskers = min–max · diamond = round average · each dot is one measured sample.

How to read this chart

The shaded band spans the measured minimum to maximum RTT of all samples collected up to that point, and the thin line traces the running average. The final position therefore matches the round statistics exactly — the band only widens when a new extreme sample arrives.

The dashed line is the round average, and the shaded band at the bottom is the theoretical fiber-optic floor (76.2 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	128.89
2	100	116.22
3	200	114.08
4	300	110.58
5	400	111.16
6	500	120.17
7	600	121.75
8	700	115.72
9	800	112.04
10	900	110.55
11	1000	111.44
12	1100	123.84
13	1200	119.26
14	1300	125.61
15	1400	119.41
16	1500	113.54
17	1600	112.48
18	1700	110.46
19	1800	110.82
20	1900	109.56
21	2000	109.59
22	2100	118.35
23	2200	115.38
24	2300	111.03
25	2400	110.59
26	2500	114.23
27	2600	110.83
28	2700	112.53
29	2800	110.93
30	2900	121.37
31	3000	114.50
32	3100	111.09
33	3200	113.45
34	3300	115.73
35	3400	112.08
36	3500	112.13
37	3600	115.02
38	3700	114.82
39	3800	114.37
40	3900	114.58
41	4000	111.38
42	4100	114.40
43	4200	112.87
44	4300	113.41
45	4400	119.08
46	4500	112.77
47	4600	113.56
48	4700	111.02
49	4800	111.22
50	4900	115.11

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 for citation guidance.

Download this dataset

Per-route ICMP ping series, released under CC BY 4.0. Uncompressed plain text — no decompression step needed.

CSV JSON YAML Full dataset

Theoretical Fiber Latency

The public physical reference uses the GeoNames city centres for Miami (25.77427, -80.19366) and Frankfurt am Main (50.11552, 8.68417). 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.5×

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.

Stability & Trend

The current measurement round (2026-08-15T04:03:13Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

Round Statistic	Value
Minimum RTT	109.56 ms
Average RTT	114.5 ms
Maximum RTT	128.89 ms
Standard deviation	4.25 ms
Stdev / average	3.7%

RTT trend

Estimated route stability across the selected time window.

Average: 114.4 ms
Minimum: 113.6 ms
Maximum: 115.6 ms
Average loss: 0.03%

Route Context

Departure PoP: Miami (MIA)
Destination PoP: Frankfurt (FRA)
Region overview: North America → Europe
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Frankfurt to Miami latency and RTT — 113.8 ms

Fastest routes departing Miami (MIA)

Miami to Ashburn latency and RTT — 27.3 ms
Miami to New York latency and RTT — 34 ms
Miami to Los Angeles latency and RTT — 56.8 ms
Miami to Seattle latency and RTT — 82 ms
Miami to London latency and RTT — 100.7 ms

Fastest routes arriving at Frankfurt (FRA)

Amsterdam to Frankfurt latency and RTT — 5.9 ms
Berlin to Frankfurt latency and RTT — 6.1 ms
Paris to Frankfurt latency and RTT — 7.6 ms
London to Frankfurt latency and RTT — 12.3 ms
Marseille to Frankfurt latency and RTT — 17.5 ms

Same corridor (North America → Europe)

New York to London latency and RTT — 64.3 ms
New York to Paris latency and RTT — 68.4 ms
New York to Amsterdam latency and RTT — 68.5 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. Per-pair files are available at /opendata/latency/latest/pairs/mia-fra.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Miami → Frankfurt round 2026-08-15T04:03:13Z, CC BY 4.0".

Data auto-generated on August 15, 2026. Explore the full interactive latency matrix or browse more city-pair routes.

Miami, USA → Frankfurt, Germany RTT