# Frankfurt, Germany → Los Angeles, USA RTT

🇩🇪 **Frankfurt, Germany (FRA)** → 🇺🇸 **Los Angeles, USA (LAX)**

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

In the 2026-08-16T04:07:28Z measurement round, ICMP echo probes from Frankfurt, Germany to Los Angeles, USA averaged 141.8 ms across 50 samples sent every 100 ms, with a minimum of 135.2 ms, a maximum of 158.63 ms, and no packet loss. The 9,324.5 km great-circle path has a theoretical vacuum floor of 62.21 ms and a straight-fiber floor of 91.31 ms, so the measured average is 1.55 times the fiber floor and reaches 64.4% fiber efficiency.

The route's 5.99 ms standard deviation and 5.12 ms jitter place it in the good latency tier with only modest variation. In the 19-route Frankfurt set for this round, the route ranked 11th, and the median standard-deviation-to-average ratio for the set was 3.28%; this route's deviation of about 4.2% of its average sits slightly above that midpoint.

Because Los Angeles is the primary US West Coast landing point for trans-Pacific cables, this no-loss, moderately stable RTT offers a useful baseline for traffic that continues toward East Asia from the US West Coast.

## Latency Summary

| Metric               | Value                                                        |
| -------------------- | ------------------------------------------------------------ |
| RTT                  | **141.8 ms**                                                 |
| Jitter               | **5.12 ms**                                                  |
| Packet Loss          | **0%**                                                       |
| Standard Fiber Floor | **91.31 ms**                                                 |
| Fiber Efficiency     | **64.4%**                                                    |
| 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 [Los Angeles](https://www.geonames.org/5368361) (34.05223, -118.24368). It does not disclose either facility address.

| Physical Reference                            | Value          |
| --------------------------------------------- | -------------- |
| WGS-84 geodesic distance                      | **9,324.5 km** |
| Vacuum RTT floor                              | **62.21 ms**   |
| Standard fiber RTT floor ($n_g=1.4679$)       | **91.31 ms**   |
| Low-latency fiber material floor              | **90.95 ms**   |
| Engineering floor (5% path allowance)         | **95.89 ms**   |
| Research 1.33× mapped-fiber reference         | **121.45 ms**  |
| Estimated unamplified path loss               | **1958.1 dB**  |
| Transparent optical spans / inline amplifiers | **123 / 122**  |
| Published RTT inflation over fiber floor      | **1.55×**      |

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        | **135.2 ms**  |
| Average RTT        | **141.8 ms**  |
| Maximum RTT        | **158.63 ms** |
| Standard deviation | **5.99 ms**   |
| Stdev / average    | **4.2%**      |

## Route Context

* Departure PoP: [Frankfurt (FRA)](/docs/network/latency/fra-frankfurt)
* Destination PoP: [Los Angeles (LAX)](/docs/network/latency/lax-los-angeles)
* 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**

* [Los Angeles to Frankfurt latency and RTT](/docs/network/latency/pairs/lax-fra-rtt) — 142.3 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 Los Angeles (LAX)**

* [Seattle to Los Angeles latency and RTT](/docs/network/latency/pairs/sea-lax-rtt) — 25.9 ms
* [Miami to Los Angeles latency and RTT](/docs/network/latency/pairs/mia-lax-rtt) — 56.8 ms
* [New York to Los Angeles latency and RTT](/docs/network/latency/pairs/nyc-lax-rtt) — 58.9 ms
* [Ashburn to Los Angeles latency and RTT](/docs/network/latency/pairs/iad-lax-rtt) — 60.7 ms
* [Tokyo to Los Angeles latency and RTT](/docs/network/latency/pairs/tyo-lax-rtt) — 101.2 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-lax.pings.{csv,json,yaml}`. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Frankfurt → Los Angeles 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-lax-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.