ICMP echo RTT measurements from Berlin, Germany to Tokyo, Japan: average latency, jitter, packet loss, and fiber efficiency for the 2026-08-16 round.

🇩🇪 Berlin, Germany (BER) → 🇯🇵 Tokyo, Japan (TYO)

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

In the 2026-08-16T04:07:28Z round, ICMP echo probes from Berlin, Germany to Tokyo, Japan produced an average RTT of 187.5 ms across 50 samples at 100 ms intervals, with a minimum of 181.19 ms, a maximum of 200.11 ms, and zero packet loss.

The 8,937.7 km great-circle distance implies a fiber-floor RTT of 87.53 ms, so the measured average is 2.14 times that floor, translating to 46.7% fiber efficiency and a fair latency tier. Jitter of 3.12 ms and a standard deviation of 4.64 ms point to a stable path despite the long distance.

This route ranks 17th among the 19 outbound routes measured from Berlin, placing it near the slower end of the city's set, while its standard deviation is about 2.5% of the average, below the 3.28% median variability seen across the network's measured routes. The main operational takeaway is that absolute RTT is high but consistent, with no loss observed during the round.

Latency Summary

Metric	Value
RTT	187.5 ms
Jitter	3.12 ms
Packet Loss	0%
Standard Fiber Floor	87.53 ms
Fiber Efficiency	46.7%
Latency Tier	Fair
Source Region	Europe
Destination Region	Asia Pacific

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: BER → TYO

50 ICMP echo samples at 100 ms intervals · round 2026-08-16T04:07:28Z · avg 187.5 ± 0.66 ms (SE)

Sample distribution: box = interquartile range (184.5–188.5 ms), median 186.8 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 (87.5 ms) for this route.

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	184.96
2	100	184.35
3	200	182.68
4	300	182.10
5	400	188.43
6	500	187.70
7	600	192.14
8	700	185.47
9	800	186.90
10	900	198.21
11	1000	200.11
12	1100	188.32
13	1200	188.27
14	1300	187.74
15	1400	186.37
16	1500	182.73
17	1600	181.79
18	1700	181.19
19	1800	189.77
20	1900	185.39
21	2000	185.79
22	2100	186.76
23	2200	186.66
24	2300	182.86
25	2400	182.42
26	2500	182.62
27	2600	184.47
28	2700	182.42
29	2800	190.59
30	2900	189.41
31	3000	185.11
32	3100	194.85
33	3200	197.37
34	3300	200.10
35	3400	187.39
36	3500	186.28
37	3600	186.87
38	3700	188.21
39	3800	184.58
40	3900	187.66
41	4000	188.46
42	4100	187.70
43	4200	195.00
44	4300	194.22
45	4400	188.66
46	4500	185.27
47	4600	187.01
48	4700	184.55
49	4800	183.99
50	4900	183.10

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 Berlin (52.52437, 13.41053) and Tokyo (35.68950, 139.69171). It does not disclose either facility address.

Physical Reference	Value
WGS-84 geodesic distance	8,937.7 km
Vacuum RTT floor	59.63 ms
Standard fiber RTT floor ( $n_g=1.4679$ )	87.53 ms
Low-latency fiber material floor	87.17 ms
Engineering floor (5% path allowance)	91.91 ms
Research 1.33× mapped-fiber reference	116.41 ms
Estimated unamplified path loss	1876.9 dB
Transparent optical spans / inline amplifiers	118 / 117
Published RTT inflation over fiber floor	2.14×

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	181.19 ms
Average RTT	187.5 ms
Maximum RTT	200.11 ms
Standard deviation	4.64 ms
Stdev / average	2.5%

RTT trend

Estimated route stability across the selected time window.

Average: 187.6 ms
Minimum: 186.1 ms
Maximum: 189.1 ms
Average loss: 0.02%

Route Context

Departure PoP: Berlin (BER)
Destination PoP: Tokyo (TYO)
Region overview: Europe → Asia Pacific
Corridor overview: Europe to Asia Pacific
Full global matrix: Backbone Latency Matrix
Physical methodology: Theoretical Fiber Latency

Reverse direction

Tokyo to Berlin latency and RTT — 186.1 ms

Fastest routes departing Berlin (BER)

Berlin to Frankfurt latency and RTT — 6.1 ms
Berlin to Amsterdam latency and RTT — 7.2 ms
Berlin to London latency and RTT — 15.2 ms
Berlin to Paris latency and RTT — 15.6 ms
Berlin to Marseille latency and RTT — 20.2 ms

Fastest routes arriving at Tokyo (TYO)

Taipei to Tokyo latency and RTT — 31.9 ms
Hong Kong to Tokyo latency and RTT — 44.9 ms
Singapore to Tokyo latency and RTT — 68.9 ms
Seattle to Tokyo latency and RTT — 85 ms
Los Angeles to Tokyo latency and RTT — 101.2 ms

Same corridor (Europe → Asia Pacific)

Moscow to Hong Kong latency and RTT — 118.6 ms
Moscow to Taipei latency and RTT — 132.1 ms
Marseille to Singapore latency and RTT — 139.6 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/ber-tyo.pings.{csv,json,yaml}. When citing, include the route, the measurement round timestamp, and the dataset version — for example: "Hats Network latency dataset, Berlin → Tokyo 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.

Berlin, Germany → Tokyo, Japan RTT