New York, USA → London, UK RTT
ICMP RTT from New York, USA to London, UK: latency, packet loss, jitter, and route efficiency for the 2026-08-15 measurement round.
🇺🇸 New York, USA (NYC) → 🇬🇧 London, UK (LON)
Measurement round: 2026-08-15T04:03:13Z.
For the 2026-08-15T04:03:13Z round, the average ICMP echo RTT from New York, USA to London, UK was 64.3 ms, with a minimum of 63.21 ms, a maximum of 69.34 ms, and zero packet loss across 50 samples.
The route ran at 85.1% fiber efficiency, or 1.18 times the 54.69 ms direct fiber round-trip floor, over a 5,585 km great-circle path. It ranked 5th among 19 outbound routes, and its 1.22 ms standard deviation is about 1.9% of the average—well below the 3.08% median relative spread for the route set.
London's traditional role as the western anchor of the Northwest European corridor, combined with jitter of 0.95 ms and zero loss, points to a mature and stable transatlantic path. The near-floor RTT makes this pairing one of the more efficient routes in the set.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 64.3 ms |
| Jitter | 0.95 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 54.69 ms |
| Fiber Efficiency | 85.1% |
| Latency Tier | Excellent |
| 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: NYC → LON
50 ICMP echo samples at 100 ms intervals · round 2026-08-15T04:03:13Z · avg 64.3 ± 0.17 ms (SE)
Sample distribution: box = interquartile range (63.5–64.6 ms), median 63.9 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 (54.7 ms) for this route.
Full 50-sample dataset
| Seq | Offset (ms) | RTT (ms) |
|---|---|---|
| 1 | 0 | 63.23 |
| 2 | 100 | 63.72 |
| 3 | 200 | 63.42 |
| 4 | 300 | 64.59 |
| 5 | 400 | 64.43 |
| 6 | 500 | 64.74 |
| 7 | 600 | 64.50 |
| 8 | 700 | 64.65 |
| 9 | 800 | 63.71 |
| 10 | 900 | 63.53 |
| 11 | 1000 | 63.44 |
| 12 | 1100 | 63.39 |
| 13 | 1200 | 63.33 |
| 14 | 1300 | 63.77 |
| 15 | 1400 | 63.53 |
| 16 | 1500 | 63.95 |
| 17 | 1600 | 64.50 |
| 18 | 1700 | 63.49 |
| 19 | 1800 | 63.82 |
| 20 | 1900 | 65.06 |
| 21 | 2000 | 64.07 |
| 22 | 2100 | 65.52 |
| 23 | 2200 | 64.34 |
| 24 | 2300 | 63.53 |
| 25 | 2400 | 63.89 |
| 26 | 2500 | 63.56 |
| 27 | 2600 | 69.34 |
| 28 | 2700 | 66.19 |
| 29 | 2800 | 66.79 |
| 30 | 2900 | 64.70 |
| 31 | 3000 | 63.53 |
| 32 | 3100 | 64.69 |
| 33 | 3200 | 63.73 |
| 34 | 3300 | 63.39 |
| 35 | 3400 | 64.68 |
| 36 | 3500 | 64.53 |
| 37 | 3600 | 63.58 |
| 38 | 3700 | 64.01 |
| 39 | 3800 | 63.55 |
| 40 | 3900 | 63.34 |
| 41 | 4000 | 63.27 |
| 42 | 4100 | 63.37 |
| 43 | 4200 | 65.93 |
| 44 | 4300 | 64.01 |
| 45 | 4400 | 66.00 |
| 46 | 4500 | 64.01 |
| 47 | 4600 | 64.07 |
| 48 | 4700 | 63.38 |
| 49 | 4800 | 63.21 |
| 50 | 4900 | 67.99 |
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.
Theoretical Fiber Latency
The public physical reference uses the GeoNames city centres for New York City (40.71427, -74.00597) and London (51.50853, -0.12574). It does not disclose either facility address.
| Physical Reference | Value |
|---|---|
| WGS-84 geodesic distance | 5,585.2 km |
| Vacuum RTT floor | 37.26 ms |
| Standard fiber RTT floor () | 54.69 ms |
| Low-latency fiber material floor | 54.48 ms |
| Engineering floor (5% path allowance) | 57.44 ms |
| Research 1.33× mapped-fiber reference | 72.74 ms |
| Estimated unamplified path loss | 1172.9 dB |
| Transparent optical spans / inline amplifiers | 74 / 73 |
| Published RTT inflation over fiber floor | 1.18× |
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 | 63.21 ms |
| Average RTT | 64.3 ms |
| Maximum RTT | 69.34 ms |
| Standard deviation | 1.22 ms |
| Stdev / average | 1.9% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 64.4 ms
- Minimum
- 63.8 ms
- Maximum
- 64.9 ms
- Average loss
- 0.03%
Route Context
- Departure PoP: New York (NYC)
- Destination PoP: London (LON)
- Region overview: North America → Europe
- Full global matrix: Backbone Latency Matrix
- Physical methodology: Theoretical Fiber Latency
Related City-Pair Routes
Reverse direction
- London to New York latency and RTT — 63.5 ms
Fastest routes departing New York (NYC)
- New York to Ashburn latency and RTT — 6 ms
- New York to Miami latency and RTT — 34.3 ms
- New York to Los Angeles latency and RTT — 58 ms
- New York to Seattle latency and RTT — 59 ms
- New York to Paris latency and RTT — 68.4 ms
Fastest routes arriving at London (LON)
- Amsterdam to London latency and RTT — 5.1 ms
- Paris to London latency and RTT — 7.1 ms
- Frankfurt to London latency and RTT — 12.6 ms
- Berlin to London latency and RTT — 15.9 ms
- Marseille to London latency and RTT — 24.5 ms
Same corridor (North America → Europe)
- New York to Amsterdam latency and RTT — 68.5 ms
- Ashburn to London latency and RTT — 70.4 ms
- New York to Frankfurt latency and RTT — 74.2 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/nyc-lon.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 → London 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.