New York, USA → London, UK RTT
ICMP RTT measurement between New York, USA and London, UK: average, jitter, packet loss, and route stability for the 2026-08-16 round.
🇺🇸 New York, USA (NYC) → 🇬🇧 London, UK (LON)
Measurement round: 2026-08-16T04:07:28Z.
During the 2026-08-16T04:07:28Z round, ICMP echo RTT from New York to London averaged 63.5 ms, with a minimum of 61.91 ms and a maximum of 68.19 ms over 50 samples. There was no packet loss, and the 1.32 ms standard deviation with 1.15 ms jitter points to a very consistent transatlantic path.
The average sits 16% above the 54.69 ms fiber-floor estimate for the 5,585 km route, giving a fiber efficiency of 86.1%. In this round the route ranked 5th among 19 outbound routes from New York, and its measured variability was well below the 3.28% median relative variability for that outbound group.
For a crossing of this length, the absence of loss and the low jitter figure make 63.5 ms a reliable ICMP latency baseline, though ICMP RTT alone should not be used to predict application performance.
Latency Summary
| Metric | Value |
|---|---|
| RTT | 63.5 ms |
| Jitter | 1.15 ms |
| Packet Loss | 0% |
| Standard Fiber Floor | 54.69 ms |
| Fiber Efficiency | 86.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-16T04:07:28Z · avg 63.5 ± 0.19 ms (SE)
Sample distribution: box = interquartile range (62.7–64.1 ms), median 63.2 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 | 62.08 |
| 2 | 100 | 63.95 |
| 3 | 200 | 62.40 |
| 4 | 300 | 62.94 |
| 5 | 400 | 63.62 |
| 6 | 500 | 62.94 |
| 7 | 600 | 62.08 |
| 8 | 700 | 62.79 |
| 9 | 800 | 63.63 |
| 10 | 900 | 63.16 |
| 11 | 1000 | 62.71 |
| 12 | 1100 | 68.19 |
| 13 | 1200 | 66.05 |
| 14 | 1300 | 64.51 |
| 15 | 1400 | 63.32 |
| 16 | 1500 | 62.23 |
| 17 | 1600 | 64.49 |
| 18 | 1700 | 64.23 |
| 19 | 1800 | 63.18 |
| 20 | 1900 | 62.55 |
| 21 | 2000 | 63.98 |
| 22 | 2100 | 63.01 |
| 23 | 2200 | 63.31 |
| 24 | 2300 | 62.96 |
| 25 | 2400 | 62.75 |
| 26 | 2500 | 62.01 |
| 27 | 2600 | 64.89 |
| 28 | 2700 | 62.73 |
| 29 | 2800 | 62.22 |
| 30 | 2900 | 62.69 |
| 31 | 3000 | 62.29 |
| 32 | 3100 | 62.60 |
| 33 | 3200 | 62.40 |
| 34 | 3300 | 61.91 |
| 35 | 3400 | 64.41 |
| 36 | 3500 | 62.56 |
| 37 | 3600 | 64.16 |
| 38 | 3700 | 63.53 |
| 39 | 3800 | 62.65 |
| 40 | 3900 | 63.41 |
| 41 | 4000 | 62.83 |
| 42 | 4100 | 66.25 |
| 43 | 4200 | 67.04 |
| 44 | 4300 | 64.24 |
| 45 | 4400 | 65.94 |
| 46 | 4500 | 64.38 |
| 47 | 4600 | 63.00 |
| 48 | 4700 | 63.29 |
| 49 | 4800 | 63.31 |
| 50 | 4900 | 63.20 |
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.16× |
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-16T04:07:28Z) collected 50 ICMP echo samples on this route. Distribution statistics from that round:
| Round Statistic | Value |
|---|---|
| Minimum RTT | 61.91 ms |
| Average RTT | 63.5 ms |
| Maximum RTT | 68.19 ms |
| Standard deviation | 1.32 ms |
| Stdev / average | 2.1% |
RTT trend
Estimated route stability across the selected time window.
- Average
- 63.5 ms
- Minimum
- 62.9 ms
- Maximum
- 64.2 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.8 ms
Fastest routes departing New York (NYC)
- New York to Ashburn latency and RTT — 6 ms
- New York to Miami latency and RTT — 32.9 ms
- New York to Seattle latency and RTT — 58.7 ms
- New York to Los Angeles latency and RTT — 58.9 ms
- New York to Amsterdam latency and RTT — 68.7 ms
Fastest routes arriving at London (LON)
- Amsterdam to London latency and RTT — 5.2 ms
- Paris to London latency and RTT — 6.4 ms
- Frankfurt to London latency and RTT — 12.9 ms
- Berlin to London latency and RTT — 15.2 ms
- Marseille to London latency and RTT — 18.9 ms
Same corridor (North America → Europe)
- New York to Paris latency and RTT — 68.9 ms
- Ashburn to London latency and RTT — 70.3 ms
- New York to Frankfurt latency and RTT — 73.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. 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-16T04:07:28Z, CC BY 4.0".
Data auto-generated on August 16, 2026. Explore the full interactive latency matrix or browse more city-pair routes.