Berlin to Tokyo ping and RTT: 189.2 ms, 3.1 ms jitter, 87.53 ms fiber floor, and 46.3% efficiency across AS203314. Updated 2026-08-09.

🇩🇪 This page compares the published ping and round-trip time (RTT) from Berlin (BER) to 🇯🇵 Tokyo (TYO) with vacuum and optical-fiber physical limits.

As of August 9, 2026, the Berlin → Tokyo route on Hats Network averages 189.2 ms RTT across a 50-sample daily ICMP echo measurement round (source: RETN), 2.16× the theoretical fiber-floor limit of 87.53 ms.

Among the 19 measured routes departing Berlin, this route ranks 17th fastest by average RTT.

With a stdev-to-average ratio of 1.7%, this route is more stable than the network median of 3.4%. Across the round, per-probe RTT ranged from 184.73 ms to 200.38 ms with a standard deviation of 3.26 ms.

Latency Summary

Metric	Value
RTT	189.2 ms
Jitter	3.1 ms
Packet Loss	0%
Standard Fiber Floor	87.53 ms
Fiber Efficiency	46.3%
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-09 · avg 189.2 ± 0.46 ms (SE)

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

Full 50-sample dataset

Seq	Offset (ms)	RTT (ms)
1	0	185.91
2	100	187.16
3	200	187.08
4	300	186.55
5	400	188.84
6	500	190.11
7	600	186.23
8	700	197.68
9	800	189.71
10	900	191.50
11	1000	190.40
12	1100	186.39
13	1200	184.87
14	1300	184.73
15	1400	192.62
16	1500	187.29
17	1600	189.60
18	1700	188.64
19	1800	189.57
20	1900	189.73
21	2000	193.48
22	2100	190.35
23	2200	190.43
24	2300	186.49
25	2400	184.99
26	2500	190.24
27	2600	186.44
28	2700	189.17
29	2800	188.68
30	2900	192.34
31	3000	194.39
32	3100	189.17
33	3200	193.94
34	3300	191.65
35	3400	186.71
36	3500	189.23
37	3600	188.28
38	3700	191.43
39	3800	186.65
40	3900	188.94
41	4000	186.75
42	4100	188.12
43	4200	185.93
44	4300	186.26
45	4400	185.59
46	4500	194.87
47	4600	200.38
48	4700	190.99
49	4800	187.54
50	4900	185.96

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.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-09) collected 50 ICMP echo samples on this route. Distribution statistics from that round:

Round Statistic	Value
Minimum RTT	184.73 ms
Average RTT	189.2 ms
Maximum RTT	200.38 ms
Standard deviation	3.26 ms
Stdev / average	1.7%

RTT trend

Estimated route stability across the selected time window.

Average: 189.0 ms
Minimum: 187.7 ms
Maximum: 190.5 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 — 187.2 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 Paris latency and RTT — 14.7 ms
Berlin to London latency and RTT — 16.1 ms
Berlin to Marseille latency and RTT — 21.6 ms

Fastest routes arriving at Tokyo (TYO)

Taipei to Tokyo latency and RTT — 31.2 ms
Hong Kong to Tokyo latency and RTT — 44.9 ms
Singapore to Tokyo latency and RTT — 69.8 ms
Seattle to Tokyo latency and RTT — 84.6 ms
Los Angeles to Tokyo latency and RTT — 100.8 ms

Same corridor (Europe → Asia Pacific)

Moscow to Hong Kong latency and RTT — 122.1 ms
Moscow to Taipei latency and RTT — 133.1 ms
Marseille to Singapore latency and RTT — 137.3 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 date, and the dataset version — for example: "Hats Network latency dataset, Berlin → Tokyo round 2026-08-09, CC BY 4.0".

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

Berlin to Tokyo Latency, Ping & RTT | AS203314